Nginx Ingress

The Nginx Ingress app is a unified logs and metrics app that helps you monitor the availability, performance, health, and resource utilization of your Nginx Ingress web servers. Preconfigured dashboards and searches provide insight into connections, requests, ingress controller metrics, visitor locations, visitor access types, traffic patterns, errors, web server operations, and access from known malicious sources.

This app is tested with the following Nginx Ingress versions:

• For Kubernetes environments: Nginx version 1.21.3

Log and metrics types

The Sumo Logic app for Nginx Ingress assumes the NCSA extended/combined log file format for Access logs and the default Nginx error log file format for error logs.

All Dashboards (except the Error logs Analysis dashboard) assume the Access log format. The Error Logs Analysis Dashboard assumes both Access and Error log formats, so as to correlate information between the two.

For more details on Nginx logs, see Module ngx_http_log_module.

The Sumo Logic app for Nginx Ingress assumes Prometheus format Metrics for Requests, Connections, and Ingress controller.

For more details on Nginx Ingress Metrics, see Prometheus.

Collecting logs and metrics for Nginx Ingress

This section provides instructions for configuring log and metric collection for the Sumo Logic app for Nginx Ingress.

In the Kubernetes environment, we use our Sumo Logic Kubernetes collection. You can learn more about this here.

Configuring log and metric collection for the Nginx Ingress app includes the following tasks:

Configure Nginx Ingress Logs and Metrics Collection

Sumo Logic supports the collection of logs and metrics data from Nginx Ingress in Kubernetes environments.

Prerequisites

It’s assumed that you are using the latest helm chart version if not please upgrade using the instructions here.

1. Before you can configure Sumo Logic to ingest metrics, you must enable the Prometheus metrics in the Nginx Ingress controller and annotate the Nginx Ingress pods, so Prometheus can find the Nginx Ingress metrics. For instructions on Nginx Open Source, refer to this documentation.
2. Ensure you have deployed the Sumologic-Kubernetes-Collection, to send the logs and metrics to Sumologic. For more information on deploying Sumologic-Kubernetes-Collection, visit here. Once deployed, logs will automatically be picked up and sent by default. Prometheus will scrape the Nginx Ingress pods, based on the annotations set in Step 1, for the metrics. Logs and Metrics will automatically be sent to the respective Sumo Logic Distribution for OpenTelemetry Collector instances, which consistently tag your logs and metrics, then forward them to your Sumo Logic org.
3. Apply the following labels to the Nginx Ingress pod.

environment="prod_CHANGEME"
component="webserver"
  webserver_system="nginx_ingress"
  webserver_farm="<farm_CHANGEME>"

Enter in values for the following parameters (marked in bold and CHANGE_ME above):

• environment. This is the deployment environment where the Nginx Ingress farm identified by the value of servers resides. For example:- dev, prod, or QA. While this value is optional we highly recommend setting it.
• webserver_farm - Enter a name to identify this Nginx Ingress farm. This farm name will be shown in the Sumo Logic dashboards. If you haven’t defined a farm in Nginx Ingress, then enter ‘default’ for webserver_farm.

Do not modify the following values set by this configuration as it will cause the Sumo Logic app to not function correctly.

• component: “webserver”. This value is used by Sumo Logic apps to identify application components.
• webserver_system: “nginx_ingress”. This value identifies the database system.

FER to normalize the fields in Kubernetes environments. Labels created in Kubernetes environments automatically are prefixed with pod_labels. To normalize these for our app to work, a Field Extraction Rule named AppObservabilityNginxIngressWebserverFER is automatically created for Nginx Application Components.

Installing the Nginx Ingress app

To install the app, do the following:

note

Next-Gen App: To install or update the app, you must be an account administrator or a user with Manage Apps, Manage Monitors, Manage Fields, Manage Metric Rules, and Manage Collectors capabilities depending upon the different content types part of the app.

1. Select App Catalog.
2. In the 🔎 Search Apps field, run a search for your desired app, then select it.
3. Click Install App.
   note

   Sometimes this button says Add Integration.

4. Click Next in the Setup Data section.
5. In the Configure section of your respective app, complete the following fields.
   1. Field Name. If you already have collectors and sources set up, select the configured metadata field name (eg _sourcecategory) or specify other custom metadata (eg: _collector) along with its metadata Field Value.
   2. Is K8S deployment involved. Specify if resources being monitored are partially or fully deployed on Kubernetes (K8s)
6. Click Next. You will be redirected to the Preview & Done section.

Post-installation

Once your app is installed, it will appear in your Installed Apps folder, and dashboard panels will start to fill automatically.

Each panel slowly fills with data matching the time range query received since the panel was created. Results will not immediately be available but will be updated with full graphs and charts over time.

Additionally, if you're using Nginx Ingress in the Kubernetes environment, the following fields will be created automatically during the app installation process:

• pod_labels_component
• pod_labels_environment
• pod_labels_webserver_system
• pod_labels_webserver_farm

Viewing Nginx Ingress dashboards

All dashboards have a set of filters that you can apply to the entire dashboard. Use these filters to drill down and examine the data to a granular level.

• You can change the time range for a dashboard or panel by selecting a predefined interval from a drop-down list, choosing a recently used time range, or specifying custom dates and times. Learn more.
• You can use template variables to drill down and examine the data on a granular level. For more information, see Filtering Dashboards with Template Variables.
• Most Next-Gen apps allow you to provide the scope at the installation time and are comprised of a key (_sourceCategory by default) and a default value for this key. Based on your input, the app dashboards will be parameterized with a dashboard variable, allowing you to change the dataset queried by all panels. This eliminates the need to create multiple copies of the same dashboard with different queries.

Overview

The Nginx Ingress - Overview dashboard provides an at-a-glance view of the NGINX server access locations, error logs, and connection metrics.

Use this dashboard to:

• Gain insights into originated traffic location by region. This can help you allocate computer resources to different regions according to their needs.
• Gain insights into your Nginx health using Critical Errors and Status of Nginx Server.
• Get insights into Active and dropped connections.

Error Logs

The Nginx Ingress - Error Logs Analysis Dashboard provides a high-level view of log level breakdowns, comparisons, and trends. The panels also show the geographic locations of clients and clients with critical messages, new connections, outliers, client requests, request trends, and request outliers.

Use this dashboard to:

• Track requests from clients. A request is a message asking for a resource, such as a page or an image.
• To track and view client geographic locations generating errors.
• Track critical alerts and emergency error alerts.

Trends

The Nginx Ingress - Logs Timeline Analysis dashboard provides a high-level view of the activity and health of Nginx servers on your network. Dashboard panels display visual graphs and detailed information on traffic volume and distribution, responses over time, as well as time comparisons for visitor locations and server hits.

Use this dashboard to:

• To understand the traffic distribution across servers, provide insights for resource planning by analyzing data volume and bytes served.
• Gain insights into originated traffic location by region. This can help you allocate compute resources to different regions according to their needs.

Outlier Analysis

The Nginx Ingress - Outlier Analysis dashboard provides a high-level view of Nginx server outlier metrics for bytes served, number of visitors, and server errors. You can select the time interval over which outliers are aggregated, then hover the cursor over the graph to display detailed information for that point in time.

Use this dashboard to:

• Detect outliers in your infrastructure with Sumo Logic’s machine-learning algorithm.
• To identify outliers in incoming traffic and the number of errors encountered by your servers.

You can use schedule searches to send alerts to yourself whenever there is an outlier detected by Sumo Logic.

Threat Intel

The Nginx Ingress - Threat Intel dashboard provides an at-a-glance view of threats to Nginx servers on your network. Dashboard panels display the threat count over a selected time period, geographic locations where threats occurred, source breakdown, actors responsible for threats, severity, and a correlation of IP addresses, method, and status code of threats.

Use this dashboard to:

• To gain insights and understand threats in incoming traffic and discover potential IOCs. Incoming traffic requests are analyzed using Sumo Logic threat intelligence.

Web Server Operations

The Nginx - Web Server Operations dashboard provides a high-level view combined with detailed information on the top ten bots, geographic locations, and data for clients with high error rates, server errors over time, and non 200 response code status codes. Dashboard panels also show information on server error logs, error log levels, error responses by a server, and the top URIs responsible for 404 responses.

Use this dashboard to:

• Gain insights into Client and Server Responses on the Nginx Server. This helps you identify errors in the Nginx Server.
• To identify geolocations of all Client errors. This helps you identify client locations causing errors and helps you to block client IPs.

Visitor Access Types

The Nginx Ingress - Visitor Access Types dashboard provides insights into visitor platform types, browsers, and operating systems, as well as the most popular mobile devices, PC and Mac versions used.

Use this dashboard to:

• Understand which platform and browsers are used to gain access to your infrastructure.
• These insights can be useful for planning in which browsers, platforms, and operating systems (OS) should be supported by different software services.

Visitor Locations

The Nginx Ingress - Visitor Locations dashboard provides a high-level view of Nginx visitor geographic locations both worldwide and in the United States. Dashboard panels also show graphic trends for visits by country over time and visits by US region over time.

Use this dashboard to:

• Gain insights into the geographic locations of your user base. This is useful for resource planning in different regions across the globe.

Visitor Traffic Insight

The Nginx Ingress - Visitor Traffic Insight dashboard provides detailed information on the top documents accessed, top referrers, top search terms from popular search engines, and the media types served.

Use this dashboard to:

• To understand the type of content that is frequently requested by users.
• It helps in allocating IT resources according to the content types.

Connections and Requests Metrics

The Nginx Ingress - Connections and Requests Metrics dashboard provides insight into active, dropped connections, reading, writing, and waiting requests.

Use this dashboard to:

• Gain information about active and dropped connections. This helps you identify the connection rejected by the Nginx Server.
• Gain information about the total requests handled by Nginx Server per second. This helps you understand read, and write requests on the Nginx Server.

Controller Metrics

The Nginx Ingress - Ingress Controller Metrics dashboard gives you insight into the status, reloads, and failure of the Kubernetes Nginx ingress controller.

Use this dashboard to:

• Gain information about Nginx ingress Controller status and reloads. This helps you understand the availability of Nginx Ingress controllers.
• Gain information about Nginx reload time and any reload errors.

Create monitors for Nginx Ingress app

From your App Catalog:

1. From the Sumo Logic navigation, select App Catalog.
2. In the Search Apps field, search for and then select your app.
3. Make sure the app is installed.
4. Navigate to What's Included tab and scroll down to the Monitors section.
5. Click Create next to the pre-configured monitors. In the create monitors window, adjust the trigger conditions and notifications settings based on your requirements.
6. Scroll down to Monitor Details.
7. Under Location click on New Folder.
   note

   By default, monitor will be saved in the root folder. So to make the maintenance easier, create a new folder in the location of your choice.

8. Enter Folder Name. Folder Description is optional.
   tip

   Using app version in the folder name will be helpful to determine the versioning for future updates.

9. Click Create. Once the folder is created, click on Save.

Nginx Ingress alerts

Here are the alerts available for Nginx Ingress (click to expand).

Alert Type (Metrics/Logs)	Alert Name	Alert Description	Trigger Type (Critical / Warning)	Alert Condition	Recover Condition
Logs	Nginx Ingress - Access from Highly Malicious Sources	This alert fires when an Nginx Ingress server is accessed from highly malicious IP addresses.	Critical	> 0	< = 0
Logs	Nginx Ingress - High Client (HTTP 4xx) Error Rate	This alert fires when there are too many HTTP requests (>5%) with a response status of 4xx.	Critical	> 0	0
Logs	Nginx Ingress - High Server (HTTP 5xx) Error Rate	This alert fires when there are too many HTTP requests (>5%) with a response status of 5xx.	Critical	> 0	0
Logs	Nginx Ingress - Critical Error Messages	This alert fires when we detect critical error messages for a given Nginx Ingress server.	Critical	> 0	0
Metrics	Nginx Ingress - Dropped Connections	This alert fires when we detect dropped connections for a given Nginx Ingress server.	Critical	> 0	0