Security

REST API output - ID field doesn't have port information for standalone instance

rahulroy_splunk
Path Finder

I'm on Splunk 6.2.6. I have a SHC (3 nodes) and a deployment server (standalone box). So when I run a search with rest command, the id field format is different in my SHC nodes and deployment server nodes.

For example, if I run this

| rest /servicesNS/-/-/saved/searches splunk_server=local | head 1 | table id

The output on SHC nodes would be

id
http://<SHCNodeName>:<mgtmt_port>/servicesNS/nobody/search/saved/searches/somesname

Whereas, the same would return this on my standalone Deployment server.

id
http://127.0.0.1/servicesNS/nobody/search/saved/searches/somesname

I believe 127.0.0.1 is localhost but no port information , hence making the id field value unreachable (planning to some automation using this id/url).

Any idea why it doesn't show a valid url in the id field on standalone instance? I don't see any explicit config on SHC node where it works.

0 Karma

renjith_nair
Legend

Hi @rahulroy_splunk,

Check mgmtHostPort configuration of your standalone instance in web.conf. https://docs.splunk.com/Documentation/Splunk/7.1.1/Admin/Webconf

Happy Splunking!
0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Watch Now!   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to leverage ...

More Control Over Your Monitoring Costs with Archived Metrics GA in US-AWS!

What if there was a way you could keep all the metrics data you need while saving on storage costs?This is now ...

New in Observability Cloud - Explicit Bucket Histograms

Splunk introduces native support for histograms as a metric data type within Observability Cloud with Explicit ...