Hello,
NEW INFO BELOW
Looking a detailed doc/vid on Service Analyzer (SA).
Having issues with permitting users an pre-filtered SA and blocking their ability to switch to another filter, or turn off filtering completely.
My flawed(?) understanding is there is really only a single SA which contains every service within ITSI. Using Teams, we should be able to create other SAs permitting permitting different access. However, that is not working; or I am missing something in the process. While I can save a new SA with the filter on service or tag in place; the user can click the X on the service or tag filter and see all services and tags available, including CPs, which they do not have read/write permissions to.
===================================
Here are some more details.
- Created role tre_user, inherits from itoa_user.
- Assigned my end users to that role.
- Users can no longer edit and save our premade deep dives (DD). They can only modify and save as new DD; which is what we wanted them to be able to do.
- When the tre_user logs in to ITSI they are taken to the default service analyzer (SA). We want them to be directed to a different SA. Also, don't want them to be able to access only a preset group of filters and flags within this assigned SA.
- We are using the KPI base searches from the Monitoring Microsoft Windows Content Pack (CP). This worked without issue for our various services. However, we had to created an additional individual service for each entity.
- 11 services covering 42 entities
- 42 services, one for each entity
- On our Glass table (GT) we have a main tab that displays all 11 services. These include KPIs for C: and 😧 drives as well as CPU and the Service Health Score (HS).
- Clicking on the HS will open a new tab in the GT displaying the entities for that service with the individual KPIs for each entity. We had to create a separate service for each entity in order to use the threshold range colors from the KPIs. If we modify the KPI base searches by adding something like | where entity = "server_1", the search becomes an adhoc search and we lose the threshold ranges and colors. Therefore, we created use the base KPI search and in the entities tab we add only one entity. We have 42 entities; therefore, 42 additional services.
Here is the SA. We want the tre_user to see only the top section (11 services); while the the bottom section should not be visible in the SA, but accessible from the GT.
Checkout this forum question of WHY we need to an individual service for each entity.
Using Aliases in Deep Dives and with other ITSI components(?)
Is there an easier way to do the above?
As a side question. Working with GT or Dashboard Studio (DS) we have come across some editing issues we did not experience in Classic Dashboards. We used to be able to develop in separate CD and then copy the rows/panels from these separate CDs into the main CD. Development was efficient.
Now with GT/DS, we can't do this. Only one developer at a time can work on the GT/DS. And if another developer left their GT/DS open, even if it was not in Edit mode; if they clicked Edit without refreshing or exiting and returning first, the first developers code was gone.
Any best practice tips on how you and your teams have handled this? It is really time consuming.
Thanks in advance and God bless,
Genesius
