Re: [prometheus-users] Ready access log from Prometheus

27 views
Skip to first unread message

Ben Kochie

unread,
Mar 2, 2020, 6:42:41 AM3/2/20
to Julian Ade Putra, Prometheus Users
mtail is a good tool for this.


On Mon, Mar 2, 2020 at 12:00 PM Julian Ade Putra <jad...@gmail.com> wrote:
Hello Experts,

I have access log that contains API list and status code that keep updating base on the transaction. May i know what is the best method to read it as metric in Prometheus?
Below the format of access log :

2020-03-02      14:38:44        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a11   0:13    /oem/proxy_services/inbound_sync_process_http_prepaid   200     514
2020-03-02      14:38:49        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a13   0:17    /oem/proxy_services/inbound_sync_process_http_prepaid   200     7831
2020-03-02      14:38:51        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a15   0:13    /oem/proxy_services/inbound_sync_process_http_prepaid   200     306
2020-03-02      14:39:02        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a18   0:5     /Catalyst/ProxyServices/NotificationActivityProxyService        200     770
2020-03-02      14:39:03        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a19   0:11    /oem/proxy_services/inbound_sync_process_http_postpaid  200     777
2020-03-02      14:39:03        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1a   0:16    /oem/proxy_services/inbound_sync_process_http_postpaid  200     2793
2020-03-02      14:39:03        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1b   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     713
2020-03-02      14:39:03        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1d   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     713
2020-03-02      14:39:04        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1e   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     713
2020-03-02      14:39:04        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1f   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     714
2020-03-02      14:39:06        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a21   0:13    /oem/proxy_services/inbound_sync_process_http_prepaid   200     1923
2020-03-02      14:39:10        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a24   0:17    /oem/proxy_services/inbound_sync_process_http_prepaid   200     5013
2020-03-02      14:39:15        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a27   0:14    /oem/proxy_services/inbound_sync_process_http_postpaid  200     49994
2020-03-02      14:39:16        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a28   0:12    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     2577
2020-03-02      14:39:16        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a2a   0:15    /oem/proxy_services/inbound_sync_process_http_prepaid   200     4556
2020-03-02      14:39:17        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a2b   0:15    /oem/proxy_services/inbound_sync_process_http_prepaid   200     307
2020-03-02      14:39:21        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a2c   0:15    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     643
2020-03-02      14:39:22        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a20   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     713
2020-03-02      14:39:22        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a1c   0:13    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     716
2020-03-02      14:39:23        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a2e   0:15    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     643
2020-03-02      14:39:28        POST    89218a53-181b-4ef3-bd64-cc159832accc-00021a30   0:15    /oem/proxy_services/inbound_sync_process_eai_http_prepaid       200     899


Thanks,
Julian

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/a288edda-8b89-4290-9606-0661ddc3e725%40googlegroups.com.

Arthi Subburaman

unread,
May 13, 2020, 12:29:03 AM5/13/20
to Prometheus Users
Hi, did you find the solution for this ? Can you please share if you found a solution?

Julius Volz

unread,
May 13, 2020, 4:50:22 AM5/13/20
to Arthi Subburaman, Prometheus Users
Could you clarify your question? Do you mean to ask whether there is a way to make Prometheus log every query or access to its web API / UI? If so, Prometheus currently does not have a way of doing this - it records metrics about HTTP requests, but no full logs.

On Wed, May 13, 2020 at 6:29 AM Arthi Subburaman <arthisu...@gmail.com> wrote:
Hi, did you find the solution for this ? Can you please share if you found a solution?

--
You received this message because you are subscribed to the Google Groups "Prometheus Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to prometheus-use...@googlegroups.com.


--
Julius Volz
PromLabs - promlabs.com

Arthi Subburaman

unread,
May 13, 2020, 9:13:54 AM5/13/20
to Prometheus Users
Hi , I’m looking to read tomcat access log which has response code. Right now the jmx exporter provides only the error count. Is there anyway I can get tomcat response code ?
Reply all
Reply to author
Forward
0 new messages