Splunk ITSI

I created a new role in ITSI and they cannot view service definitions/ thresholds/KPI's

amckinnie_splun
Splunk Employee
Splunk Employee

I want my users to only have read access to service definitions and thresholds. I created a new role with all of the read access capabilities in ITSI. Users with the new role should be able to see various items and not edit them. However, when a user tries to view service definitions and thresholds, the page does not load. 

0 Karma
1 Solution

amckinnie_splun
Splunk Employee
Splunk Employee

To create a custom role in ITSI you have to perform 4 steps. 

1. Assign the role proper capabilities

2. Grant the role access to ITSI indexes

3. Assign the role proper view-level access

4.Assign the role KV store collection level access

The step most people skip is to assign proper view level access. To do this, navigate to Settings >> all configurations OR Settings >> User interface>>Views. Here you need to grant view access for your newly created role. If you are not sure which view the user needs access to? Pay attention to the URL. Navigate to the area that the role cannot access and look at the URL, this will tell you which view you should update. 

Ex URL: splunkcloud.com/en-US/app/itsi/entity_detail.......

Navigate to Settings >> User Interface >> Views >> search for entity. You will see the item named entity_detail. Modify the permissions and allow the new role to have read rights. This will allow the new role to access this view. 

View solution in original post

0 Karma

amckinnie_splun
Splunk Employee
Splunk Employee

To create a custom role in ITSI you have to perform 4 steps. 

1. Assign the role proper capabilities

2. Grant the role access to ITSI indexes

3. Assign the role proper view-level access

4.Assign the role KV store collection level access

The step most people skip is to assign proper view level access. To do this, navigate to Settings >> all configurations OR Settings >> User interface>>Views. Here you need to grant view access for your newly created role. If you are not sure which view the user needs access to? Pay attention to the URL. Navigate to the area that the role cannot access and look at the URL, this will tell you which view you should update. 

Ex URL: splunkcloud.com/en-US/app/itsi/entity_detail.......

Navigate to Settings >> User Interface >> Views >> search for entity. You will see the item named entity_detail. Modify the permissions and allow the new role to have read rights. This will allow the new role to access this view. 

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Tech Talk Recap | Mastering Threat Hunting

Mastering Threat HuntingDive into the world of threat hunting, exploring the key differences between ...

Observability for AI Applications: Troubleshooting Latency

If you’re working with proprietary company data, you’re probably going to have a locally hosted LLM or many ...

Splunk AI Assistant for SPL vs. ChatGPT: Which One is Better?

In the age of AI, every tool promises to make our lives easier. From summarizing content to writing code, ...