For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Open sourceSupportFAQsDocs Home
DocumentationAPI referenceRelease notes
DocumentationAPI referenceRelease notes
  • Platform On-Prem
    • Overview
    • Navigate
      • View web server access logs
      • Event deduplication
      • Prometheus metrics
      • SNMP MIB
      • Recommendations
    • Search resources
  • Apps
    • FlowAI
    • Itential Automation Gateway
  • Resources
    • Itential Academy
    • Version lifecycle
    • Itential MCP
    • Accessibility conformance
    • Get support
    • FAQs
LogoLogo
Open sourceSupportFAQsDocs Home
On this page
  • Common log format
  • Configuration
  • Log rotation
  • Install logrotate
  • Configure logrotate
  • Example configuration by size
  • Example configuration by time
  • Run logrotate
  • Query log files
  • Use grep or similar command line tools
  • Use third-party visualization tools
Platform On-PremMonitor and log

View web server access logs

Was this page helpful?
Previous

Configure event deduplication

Next
Built with

This guide explains how to use a web server access log to see the calls made to the web server within Itential Platform.

You will need to access the Profile application within Admin Essentials. Navigate to Itential Platform > Admin Essentials > Profile. For more information, see Profiles.

Common log format

The log format for the web server access log is a stringified JSON object with each key mapping to a part of the Common Log Format. Since this is a JSON format, the ordering of the keys is not guaranteed. The keys, in the order they appear in a traditional Common Log Format, are referenced below.

KeyDescription
remote_addrThe IP address where the request comes from
remote_userThe username within Itential Platform that made the request (if not authenticated, a value of anon is used)
dateThe date the request was made in the Common Log Format
methodThe HTTP method of the request (GET, PUT, POST, or DELETE)
urlThe URL path used by the request
http_versionThe HTTP version used to make the request
statusThe status code returned as a response
result_lengthThe size of the response data in bytes (if this cannot be parsed, a value of ”-” is used)

Configuration

The web server access log currently has two different configurable properties that can be edited within the Itential Platform profile by updating loggerProps in the Profile Properties. Both properties can be found in the webserver section of the Configure tab.

PropertyDescription
log_directoryThe file path to the directory where the access logfile is stored
log_filenameThe exact name for the web server access logfile that will be created and used to store all access logs (located within the log_directory specified)

Profile Properties

Log rotation

There is no automatic log rotation built into the web server access log, which makes configuring an external log rotator very important. One useful tool to accomplish this is logrotate, a Linux tool that can automatically rotate a log file based on configured parameters.

Install logrotate

Install logrotate using your package manager:

RHEL/CentOS:

$yum install logrotate

Configure logrotate

Verify that logrotate is installed, then check the configuration file at /etc/logrotate.conf. There may be other ways to handle configuration, such as inside the /etc/logrotate.d/ folder.

Example configuration by size

The following example shows a configuration where the webserver logfile is named webserver.log and is located at /var/log/pronghorn:

$/var/log/pronghorn/webserver.log {
>  rotate 10
>  size 10M
>  nocompress
>}

In this example:

  • Logs rotate a maximum of 10 times before old log files are deleted
  • Logs only rotate when their size exceeds 10 megabytes
  • Files are not compressed when rotated

Example configuration by time

Another possible configuration:

$/var/log/pronghorn/webserver.log {
>  weekly
>  rotate 20
>  postrotate
>      echo Hello World
>  endscript
>}

In this example:

  • Logs rotate weekly instead of by size
  • Logs rotate a maximum of 20 times
  • A postrotate script runs after each rotation (in this case, echoing “Hello World” to the console)

Run logrotate

Start the log rotation:

$logrotate /etc/logrotate.conf

To force a rotation immediately, even when conditions like file size have not been met:

$logrotate -f /etc/logrotate.conf

Query log files

The log files can be queried using basic command line tools such as grep to search the file for a given pattern.

Use grep or similar command line tools

To find any API requests made by a user named admin for the log file named webserver.log:

$grep '"remote_user":"admin"' webserver.log

To retrieve all times a user has made a request to a specific route, such as GET /health/system:

$grep -E '"url":"/health/system"' webserver.log | grep '"verb":"GET"'

There are many other ways grep and similar command line tools can be used to query information from the JSON logs. Since all data values are preceded by a key, such as url or remote_user, it is possible to do standard queries on any value.

Use third-party visualization tools

The log format used by the access log should work with various third-party tools which support a standard JSON log format. These can be used for more advanced queries or visualization of logging information.