Splunk Enterprise

Splunk REST API: Bypass response format check

RG2
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
Get Updates on the Splunk Community!

Data Management Digest – December 2025

Welcome to the December edition of Data Management Digest! As we continue our journey of data innovation, the ...

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...