# View apache extended status **URL:** \ **Category:** Beats\ **Tags:** metricbeat\ **Created:** [December 23, 2019, 8:11pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895 "2019-12-23T20:11:51Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![jamesbro](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesbro](https://discuss.elastic.co/u/jamesbro)\ **Post date:** [December 23, 2019, 8:11pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/1 "2019-12-23T20:11:51Z")
I am currently monitoring the Apache status page, however. the extended status is not viewable/searchable in Kibana. Is there a way to get the extended status info from the status page into elastic using the metricbeat apache module? Thanks. ---
**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\ **Post date:** [December 23, 2019, 10:22pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/2 "2019-12-23T22:22:57Z")
Reading through [https://documentation.help/httpd-2.0-es/mod\_status.html](https://documentation.help/httpd-2.0-es/mod_status.html) and [https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-apache-status.html](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-metricset-apache-status.html) it appears the Metricbeat `apache` module already knows how to ingest extended status fields. Could you post a sample document from your Elasticsearch cluster showing the lack of extended status fields in it? Shaunak ---
**Author:** ![jamesbro](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesbro](https://discuss.elastic.co/u/jamesbro)\ **Post date:** [December 30, 2019, 9:14pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/3 "2019-12-30T21:14:12Z")
``` `{ ``` "\_index": "code-metricbeat-7.5.0-2019.12.12-000001", "\_type": "\_doc", "\_id": "8gKmWG8BsX8Gf5MmiDzQ", "\_score": 1, "\_source": { "@timestamp": "2019-12-30T21:11:45.629Z", "ecs": { "version": "1.1.0" }, "host": { "name": "it-sdp-elbk", "hostname": "it-sdp-elbk", "architecture": "x86\_64", "os": { "family": "redhat", "name": "Red Hat Enterprise Linux", "kernel": "4.18.0-80.el8.x86\_64", "codename": "Ootpa", "platform": "rhel", "version": "8.0 (Ootpa)" }, "id": "c5e619c01395431bb0bd652bd26dae10", "containerized": false }, "agent": { "id": "df77a5d7-12c1-4def-974f-4bae9a85d477", "version": "7.5.0", "type": "metricbeat", "ephemeral\_id": "ce58b51c-a9c1-4ea1-a910-a2a817727177", "hostname": "it-sdp-elbk" }, "event": { "dataset": "apache.status", "module": "apache", "duration": 11132026 }, "metricset": { "name": "status", "period": 10000 }, "service": { "address": "xxxx.xxxxxx.xxx", "type": "apache" }, "apache": { "status": { "workers": { "idle": 179, "busy": 21 }, "connections": { "total": 161, "async": { "closing": 84, "writing": 0, "keep\_alive": 53 } }, "load": { "1": 0.93, "5": 1.09, "15": 1.06 }, "total\_accesses": 71217636, "cpu": { "children\_system": 62559.1, "load": 9.23653, "user": 2160.66, "system": 1078.53, "children\_user": 120387 }, "total\_kbytes": 9917617674, "requests\_per\_sec": 35.3306, "uptime": { "uptime": 2015749, "server\_uptime": 2015749 }, "scoreboard": { "keepalive": 0, "dns\_lookup": 0, "closing\_connection": 0, "logging": 0, "idle\_cleanup": 0, "open\_slot": 200, "gracefully\_finishing": 0, "total": 400, "starting\_up": 0, "reading\_request": 6, "sending\_reply": 15, "waiting\_for\_connection": 179 }, "bytes\_per\_sec": 5038150, "hostname": "xxxx.xxxxxx.xxx", "bytes\_per\_request": 142600 } } }, "fields": { "@timestamp": [ "2019-12-30T21:11:45.629Z" ] } }` ---
**Author:** ![jamesbro](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesbro](https://discuss.elastic.co/u/jamesbro)\ **Post date:** [December 30, 2019, 9:16pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/4 "2019-12-30T21:16:43Z")
I'm not sure if this is the extended status information or not. What I am looking for is the information displayed in the following fields: srv PID Acc M CPU SS Req Dur Conn Child Slot Client Protocol VHost Request ---
**Author:** ![jamesbro](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesbro](https://discuss.elastic.co/u/jamesbro)\ **Post date:** [December 31, 2019, 4:08am UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/6 "2019-12-31T04:08:43Z")
Sorry mate. Can you translate? ---
**Author:** ![jamesbro](https://avatars.discourse-cdn.com/v4/letter/j/a9a28c/32.png) [@jamesbro](https://discuss.elastic.co/u/jamesbro)\ **Post date:** [January 22, 2020, 8:30pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/7 "2020-01-22T20:30:33Z")
Hi, I have done some more research and read through the linked page and the following fields from the scoreboard are not consumed. Is there a way to include them through metricbeat apache module or any either way? (Srv,PID,Acc,M,CPU,SS,Req,Dur,Conn,Child,Slot,Client,Protocol,VHost,Request) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [February 19, 2020, 8:30pm UTC](https://discuss.elastic.co/t/view-apache-extended-status/212895/8 "2020-02-19T20:30:36Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.