Observability | Updated Team Landing Page

[rt]

We've updated the look and feel of the team landing page in Splunk Observability. 

The team landing page is where you can go to see any active alerts and dashboard groups that have been linked to a team in Splunk Observability. When you use the teams feature, each team can curate the custom dashboards and detectors that appear on their team landing page. For instance, as a team lead I could collect all the dashboards related to the services that my team is responsible for, and link my team's detectors so that any alerts on those services will appear here. This is a good way to help a new team member quickly find useful content. 

The old team landing page.

The refreshed team landing page contains all the same information it had before -- team name, description, linked alerts and dashboards -- but its look and feel has been updated to better align with other areas of Splunk Observability. Team dashboards are arranged in a searchable, sortable table. We can also directly see the list of alerts linked to our team, in addition to the count. 

The team landing page's new look.

To create and manage teams, click the Settings icon, then click Teams for a full list of teams in your organization. Click here to read more about teams in Splunk Observability. 

[savec]

Hello,

While I'm really happy with the new look, I'm missing capability to navigate to team's detectors. Having dozens of teams making it not very convenient to filter on the alert page, especially as sorting works by time and not name.
Thank you.

[mjonesatlassian]

Hi there!

Just saw the new team dashboard. Overall, looks great! Really like having the alerts shown as the first thing you see.

However, as a team that looks after a lot of different microservices, each with a dedicated Dashboard Group with several dashboards within them, the new layout makes it significantly more difficult to jump into the Dashboard Group for Service A as now I have to go through several levels of pagination to find the service I need to check up on.

Is it possible to return the Dashboard Group as a top-level item to make navigating to dashboards for particular services that much easier? Not necessarily in the same format as before, but laid out so we can easily see and jump into any of the Dashboard Groups owned by our team.

Now, to get where I need to go, I have to scan through a list of duplicate items in the second columns of the new Dashboards table across three pages of dashboards to find the one for the service I'm after, and then click into the particular dashboard I want within that group. That's much harder than before when I'd quickly scan the names of all the dashboard group items that were displayed right in front of me to find the one I want, click into it, and if I accidentally clicked on the wrong dashboard within that group then oh well the right one is only a tab away! This is especially important during incidents when checking up on the health of a particular microservice to identify what's making it sad is so time critical.

I hope you take this feedback into account and provide some sort of top-level Dashboard Groups navigation on the new teams page. But other than that, really like how modern the new layout looks compared to the old one! Nice work team!

[enrico_jonas]

Hi,

we are facing the same problem. Essentially there is no overview anymore about the Dashboard Groups my team is owning, so essentially no way to find the dashboards if you don't know the name of the boards / groups. Additionally on the Teams Landing page, the dashboards-list only shows dashboards but no mirrors it seems. We are using a lot of mirrors, those do not show up their either.

I think you should activate the dashboard groups frame on the teams landing page again. Our dashboard groups / mirrors are practically useless after this change.

Regards

Enrico

[mnegron1]

Same comment here on the navigation.

The new [list] view is much more cumbersome to traverse and the list does not have any tools to order or choose columns to include/exclude.

Also, the detector are nice to have, but if no detectors are linked or enabled, there is a lot of real-estate lost on the page view..  Perhaps just having the summary line with severity/counts and it be the hyperlink to the active alerts may reduce some of the space used.

The tiled Dashboard group and related dashboard (same as the [all dashboards] view) was a much cleaner/simpler view at the team level