You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/use-cases/observability/clickstack/integration-examples/nginx-logs.md
+8-8Lines changed: 8 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ import search_view from '@site/static/images/clickstack/nginx-logs-search-view.p
18
18
19
19
# Monitoring Nginx Logs with ClickStack {#nginx-clickstack}
20
20
21
-
::::note[TL;DR]
21
+
:::note[TL;DR]
22
22
This guide shows you how to monitor nginx with ClickStack by configuring the OpenTelemetry collector to ingest nginx access logs. You'll learn how to:
23
23
24
24
- Configure nginx to output JSON-formatted logs
@@ -29,7 +29,7 @@ This guide shows you how to monitor nginx with ClickStack by configuring the Ope
29
29
A demo dataset with 10,000 sample logs is provided to test the integration before connecting your production nginx instances.
30
30
31
31
Time Required: 5-10 minutes.
32
-
::::
32
+
:::
33
33
34
34
## Prerequisites {#prerequisites}
35
35
- ClickStack instance running
@@ -118,12 +118,12 @@ This configuration:
118
118
- Adds source: nginx attribute for filtering in HyperDX
119
119
- Routes logs to the ClickHouse exporter via a dedicated pipeline
120
120
121
-
::::note
121
+
:::note
122
122
- You only define new receivers and pipelines in the custom config
123
123
- The processors (memory_limiter, transform, batch) and exporters (clickhouse) are already defined in the base ClickStack configuration - you just reference them by name
124
124
- The time_parser operator extracts timestamps from nginx's time_local field to preserve original log timing
125
125
- The pipelines route data from your receivers to the ClickHouse exporter via the existing processors
126
-
::::
126
+
:::
127
127
128
128
## Configure ClickStack to load custom configuration {#load-custom}
129
129
@@ -161,9 +161,9 @@ docker run --name clickstack \
Ensure the ClickStack collector has appropriate permissions to read the nginx log files. In production, use read-only mounts (:ro) and follow the principle of least privilege.
166
-
::::
166
+
:::
167
167
168
168
## Verifying Logs in ClickStack {#verifying-logs}
169
169
Once configured, log into HyperDX and verify logs are flowing:
@@ -255,9 +255,9 @@ Once ClickStack is running (you may have to create an account and login first):
255
255
256
256
1. Open [HyperDX](http://localhost:8080/search?from=1760976000000&to=1761062400000&isLive=false&source=690235c1a9b7fc5a7c0fffc7&select=Timestamp,ServiceName,SeverityText,Body&where=&whereLanguage=lucene&filters=[]&orderBy=)
257
257
258
-
::::note
258
+
:::note
259
259
It is important to use the link above to get the correct time range, if you don't use this link set your time range to Oct 20 11:00:00 - Oct 21 11:00:00 to see proper results.
0 commit comments