Splunk® IT Service Intelligence


This documentation does not apply to the most recent version of Splunk® IT Service Intelligence. For documentation on the most recent version, go to the latest release.

Troubleshoot the Web Server Module

See information below for troubleshooting information specific to the ITSI Web Server Module. For more information, see Troubleshooting modules.

Minicharts for Storage, Memory, and CPU in the drilldown are not displaying results

Minicharts that fail to display results in the drill down can occur due to one of the following issues:

  • You are running a version of ITSI that does not have the Operating System (OS) module installed. The saved searches that the minicharts use are stored within the context of the OS module. Upgrade to ITSI version 2.1 and above to fix this issue.
  • You do not have the Splunk Add-On for Windows or the Splunk Add-On for Unix and Linux installed. These are the applications that send data about OS metrics into the indexer. Install the Splunk Add-On for Windows or the Splunk Add-On for Unix and Linux to enable minichart display results.

Error tab doesn't have any information on the panels

The Error tab displays web server errors that occur within Apache, and not the site serving content.

Error log related searches are different from HTTP errors (4xx, 5xx).

To fix this issue, perform the following steps:

  1. Navigate to your data input configurations.
  2. Add the files/directories that correspond to your deployment's error logs.
  3. Assign the correct source types.
  4. Click Save.

Configure your Apache Web Server to display log events in a format Splunk platform can read

Configure your Apache Web Server deployment to format log events in a format that can be read by the Splunk Add-on for Apache Web Server.

  1. Navigate to the apache httpd.conf file in your Apache deployment (Example: /etc/apache/httpd.conf).
  2. Navigate to the statement <IfModule log_config_module> in your apache httpd.conf file, and replace the file contents with the below stanza:
     <IfModule log_config_module>
        # The following directives define some format nicknames for use with
        # a CustomLog directive (see below).
        LogFormat "%h %v %l %u %{local}p %t \"%r\" \"%q\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O %D" combined
        LogFormat "%h %l %u %t \"%r\" %>s %b" common
        <IfModule logio_module>
          # You need to enable mod_logio.c to use %I and %O
          LogFormat "%h  %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
        # The location and format of the access logfile (Common Logfile Format).
        # If you do not define any access logfiles within a <VirtualHost>
        # container, they will be logged here.  Contrariwise, if you *do*
        # define per-<VirtualHost> access logfiles, transactions will be
        # logged therein and *not* in this file.
        # CustomLog "logs/access_log" common
        # If you prefer a logfile with access, agent, and referer information
        # (Combined Logfile Format) you can use the following directive.
        CustomLog "logs/access_log" combined
  3. Restart your Apache server.
Last modified on 28 April, 2023
Web Server Module data model reference table   Troubleshooting modules

This documentation applies to the following versions of Splunk® IT Service Intelligence: 4.11.0, 4.11.1, 4.11.2, 4.11.3, 4.11.4, 4.11.5, 4.11.6, 4.12.0 Cloud only, 4.12.1 Cloud only, 4.12.2 Cloud only, 4.13.0, 4.13.1, 4.13.2, 4.13.3, 4.14.0 Cloud only, 4.14.1 Cloud only, 4.14.2 Cloud only, 4.15.0, 4.15.1, 4.15.2, 4.15.3, 4.16.0 Cloud only, 4.17.0, 4.17.1, 4.18.0, 4.18.1

Was this topic useful?

You must be logged into splunk.com in order to post comments. Log in now.

Please try to keep this discussion focused on the content covered in this documentation topic. If you have a more general question about Splunk functionality or are experiencing a difficulty with Splunk, consider posting a question to Splunkbase Answers.

0 out of 1000 Characters