https://bz.apache.org/bugzilla/show_bug.cgi?id=64392
Bug ID: 64392
Summary: mod_status should offer JSON output
Product: Apache httpd-2
Version: 2.4-HEAD
Hardware: All
OS: All
Status: NEW
Severity: enhancement
Priority: P2
Component: mod_status
Assignee: bugs@httpd.apache.org
Reporter: rals...@pobox.com
Target Milestone: ---
The telemetry that the mod_status module provides comes in a human-readable
flavor:
curl --silent --max-time 30 'http://localhost/server-status'
And a more machine-readable flavor:
curl --silent --max-time 30 'http://localhost/server-status?auto'
Unfortunately, "key: value" pairs aren't particularly machine-readable without
help. For example, Splunk expects key=value pairs for textual data, so some
mangling of the output is required if the goal is to ship the telemetry off to
Splunk for graphing and other analysis:
curl --silent --max-time 30 'http://localhost/server-status' | sed
's/^\([[:alnum:]][[:alnum:]]*\): /\1=/g'
Hoops like this could be avoided if mod_status supported a more modern
machine-readable output format, such as JSON, as Splunk can grok JSON directly.
Thus, it would be tremendously useful for sites who are pulling the mod_status
telemetry into systems like Splunk and Grafana. (And I'd wager that's the
primary use of mod_status nowadays: cattle, not pets.)
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
