REST error in DMC Index Detail

[cboillot]

In the DMC, I am seeing errors like below when looking at Index Detail.

[<SplunkServerName>] REST Processor: Failed to fetch REST endpoint uri=https://127.0.0.1:8089/services/data/indexes/<IndexName>?count=0 from server https://127.0.0.1:8089. Check that the URI path provided exists in the REST API.

and

[subsearch]: [<SplunkServerName>] REST Processor: Failed to fetch REST endpoint uri=https://127.0.0.1:8089/services/data/indexes-extended/<IndexName>?count=0 from server https://127.0.0.1:8089. Check that the URI path provided exists in the REST API

I don't see any reference to the /services/data in the REST endpoints. I am not sure what could be wrong.

Is this telling me that, on that Spunk Server, it is not seeing that index?

[Paul1896]

@cboillotDid you solved the issue in your DMC?

[matthewpearce]

I received the same problem in the DMC after upgrading from 7.2.4 to Splunk 8.0.2.1. It appeared to be fixed after I adjusted the cluster master to forward logs to the indexers.

[Vijeta]

Use this, instead of services use servicesNS

|rest /servicesNS/-/-/data/indexes/<IndexName>

[cboillot]

Still getting the sames errors, now with NS added. With or without the /-/-/.

[Vijeta]

@cboillot are you able to fetch any other end-points. Probably your id does not have permissions for rest calls.

[cboillot]

Odd, i should have full Admin rights.

[jbrinkman]

Do the hosts the error is thrown on actually have the index created? I see the same error for HFs configured with the server role of indexer in the monitoring console. So they are getting pinged by the search through rest even though they don't have the index created or any knowledge of it (not keeping the indexes updated on the HF since we don't do any searching there).