Bypass response format check in PersistentServerConnectionApplication

RG2 — Tue, 03 Oct 2023 08:28:38 GMT

I am trying to host Prometheus metrics on a Splunk app such that the metrics are available at `.../my_app/v1/metrics` endpoint.

I am able to create a handler of type PersistentServerConnectionApplication and have it return Prometheus metrics. The response status, however, code = `500` and content = `Unexpected character while looking for value: '#'`

Prometheus metrics do not confirm to any of the supported `output_modes`

(atom | csv | json | json_cols | json_rows | raw | xml)

so I get the same error irrespective of the output mode chosen.

Is there a way to bypass the output check? Is there any other alternative to host a non-confirming-format output via a Splunk REST API?

Re: Bypass response format check in PersistentServerConnectionApplication

_JP — Fri, 06 Oct 2023 20:06:24 GMT

I'm assuming you know about & are modeling things after the Splunk Rest Examples?

Can you share a bit of your Python on how you are returning your data? What I'm thinking is if your handle method isn't returning your data in the correct JSON format it needs to generate the response.

topic Bypass response format check in PersistentServerConnectionApplication in Getting Data In

Bypass response format check in PersistentServerConnectionApplication

Re: Bypass response format check in PersistentServerConnectionApplication