Deployment Architecture

Error on Overview Pane - Failed to fetch REST endpoint

yarick
Path Finder

REST Processor: Failed to fetch REST endpoint uri=https://127.0.0.1:8089/services/alerts/correlationsearches?count=0 from server https://127.0.0.1:8089. Check that the URI path provided exists in the REST API.
Unexpected status for to fetch REST endpoint uri=https://127.0.0.1:8089/services/alerts/correlationsearches?count=0 from server=https://127.0.0.1:8089 - Not Found

zamkov
Explorer

You can edit savedsearch panel and change the REST Endpoint to the updated version
From:
/services/alerts/correlationsearches
To:
/services/saved/searches

REF. https://answers.splunk.comn/answers/239437/how-to-get-a-complete-list-with-descriptions-of-co.html
REF. https://docs.splunk.com/Documentation/ESHealthCheck/1.0.0/UserGuide/Releasenotes

2017-05-10 SOLNESS-12056, SOLNESS-12106 On instances running Splunk Enterprise Security 4.6.0 or later, the Get Enabled Correlation Searches panel does not show results.
Workaround:
Replace the search with the following syntax: | rest splunk_server=local count=0 /services/saved/searches | search action.correlationsearch.enabled = 1 | stats count as total, count(eval(disabled=0)) as enabled | eval op = enabled . "/" . total | fields op

yarick
Path Finder

Perfect, thanks!

0 Karma
Get Updates on the Splunk Community!

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

The Latest Cisco Integrations With Splunk Platform!

Join us for an exciting tech talk where we’ll explore the latest integrations in Cisco + Splunk! We’ve ...

AI Adoption Hub Launch | Curated Resources to Get Started with AI in Splunk

Hey Splunk Practitioners and AI Enthusiasts! It’s no secret (or surprise) that AI is at the forefront of ...