Getting Data In

Bypass response format check in PersistentServerConnectionApplication

Splunk Employee
Splunk Employee

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?

Labels (1)
0 Karma


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.

0 Karma
Get Updates on the Splunk Community!

Observability | How to Think About Instrumentation Overhead (White Paper)

Novice observability practitioners are often overly obsessed with performance. They might approach ...

Cloud Platform | Get Resiliency in the Cloud Event (Register Now!)

IDC Report: Enterprises Gain Higher Efficiency and Resiliency With Migration to Cloud  Today many enterprises ...

The Great Resilience Quest: 10th Leaderboard Update

The tenth leaderboard update (11.23-12.05) for The Great Resilience Quest is out >> As our brave ...