Docs » Available host and application monitors » Configure application receivers for hosts and servers » NGINX

NGINX 🔗

The Splunk Distribution of OpenTelemetry Collector uses the Smart Agent receiver with the nginx monitor type to to retrieve metrics and logs from an NGINX instance.

This integration is available on Linux and Windows.

Benefits 🔗

After you configure the integration, you can access these features:

  • View metrics. You can create your own custom dashboards, and most monitors provide built-in dashboards as well. For information about dashboards, see View dashboards in Observability Cloud.

  • View a data-driven visualization of the physical servers, virtual machines, AWS instances, and other resources in your environment that are visible to Infrastructure Monitoring. For information about navigators, see Splunk Infrastructure Monitoring navigators.

  • Access the Metric Finder and search for metrics sent by the monitor. For information, see Use the Metric Finder.

Installation 🔗

Follow these steps to deploy this integration:

  1. Deploy the Splunk Distribution of OpenTelemetry Collector to your host or container platform:

  2. Configure the monitor, as described in the Configuration section.

  3. Restart the Splunk Distribution of OpenTelemetry Collector.

Configuration 🔗

To use this integration of a Smart Agent monitor with the Collector:

  1. Include the Smart Agent receiver in your configuration file.

  2. Add the monitor type to the Collector configuration, both in the receiver and pipelines sections.

Example 🔗

To activate this integration, add the following to your Collector configuration:

receivers:
  smartagent/nginx:
    type: collectd/nginx
    ...  # Additional config

Next, add the monitor to the service > pipelines > metrics > receivers section of your configuration file:

service:
  pipelines:
    metrics:
      receivers: [smartagent/nginx]
    logs:
      receivers: [smartagent/nginx]

Configuration settings 🔗

The following table shows the configuration options for this monitor:

Option

Required

Type

Description

host

Yes

string

Hostname or IP address of the NGINX instance. For example, 127.0.0.1.

port

Yes

integer

The port of the NGINX instance. For example, 8080.

name

no

string

Name of the NGINX instance.

url

no

string

URL of the status endpoint. The default value is http://{{.Host}}:{{.Port}}/nginx_status, which takes the values defined in host and port.

username

no

string

Username for HTTP basic authentication, if needed.

password

no

string

Password for HTTP basic authentication, if needed.

timeout

no

integer

Timeout in seconds for the request. The default value is 0.

Nginx configuration 🔗

You can configure NGINX to expose status information by editing the NGINX configuration. See ngx_http_stub_status_module on the NGINX documentation site.

After you’ve set up the Collector, follow these steps to configure the Nginx web server to expose status metrics:

  1. Add the following configuration to your Nginx server:

    server {
      location /nginx_status {
        stab_status on;
        access_log off;
        allow 127.0.0.1; # The source IP address of OpenTelemetry Collector.
        deny all;
      }
    }
    
  2. Restart the Nginx web server.

Metrics 🔗

The following metrics are available for this integration:

Notes 🔗

  • Learn more about the available metric types in Observability Cloud.

  • Default metrics are those metrics included in host-based subscriptions in Observability Cloud, such as host, container, or bundled metrics. Custom metrics are not provided by default and might be subject to charges. See more about metric categories.

  • To add additional metrics, see how to configure extraMetrics using the Collector.

Troubleshooting 🔗

If you are not able to see your data in Splunk Observability Cloud, try these tips:

To learn about even more support options, see Splunk Customer Success.