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: README.md
+43-15Lines changed: 43 additions & 15 deletions
Original file line number
Diff line number
Diff line change
@@ -1,10 +1,29 @@
1
1
# About
2
2
3
-
Monitor the incoming and outgoing traffic metrics in realtime for NGINX http subsystem.
3
+
Monitor the incoming and outgoing traffic metrics in realtime for `NGINX` http subsystem.
4
4
5
5
Realtime traffic and status code monitor solution for NGINX, need less memory and cpu than realtime log analyzing.
6
6
Useful for http traffic accounting based on NGINX config logic ( by-location or by-server or by-user-defined-variable ).
7
7
8
+
## Why?
9
+
10
+
Real-time log analysis solution,
11
+
which requires multiple machines for storage and analysis,
12
+
are too heavy for application monitoring.
13
+
14
+
An cost-effective solution is needed to monitor the traffic metrics/status of application requests.
15
+
That solution should be accurate, sensitive, robust, light weight enough, and not affected by traffic peaks.
16
+
17
+
## How it works?
18
+
19
+
The context of this module keeps a list of **metrics** identified by `accounting_id`.
20
+
21
+
When a new **request** hits the server, the module will try to find its `accounting_id`, calculate statistics, and **aggregate** them into the corresponding metrics.
22
+
23
+
For every period (defined by `interval`), a timer event is triggered, these metrics are rotated and exported to log files or remote log servers.
0 commit comments