Monitoring Splunk

Monitoring console not working for user prievileges.

saramamurthy_sp
Splunk Employee
Splunk Employee

What capabilities I need to give to particular user on Deployment Server in order to view monitoring console?

Right now I have given admin_all_objects capability.

But when I am checking health check it is showing instances not reachable.

And if I am logging in with admin credentials all instances are showing as reachable.

Currently I have given user and power role to user along with admin_all_objects capability.

Tags (1)
0 Karma

swmishra_splunk
Splunk Employee
Splunk Employee

You need to provide in total three capabilities to view the monitoring console for user privileges.

1).admin_all_objests.

2).dispatch_rest_to_indexers.

3).edit_dist_peer.

The dispatch_rest_to_indexers capability will show the resource usage of each instance and edit_dist_peer will fix the instance unreachable error.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...