Collaborate on observability within and across teams 🔗
You can scale your system’s observability through collaboration. Site Reliability Engineers (SREs), developers, operations, and other teams can efficiently collaborate in Splunk Observability Cloud by sharing dashboards, queries, and detectors, which you can configure to send notifications to the appropriate teams or users. By using Splunk Observability Cloud’s tools for collaborating, your teams can exponentially expand their reach and scale the reliability of your systems quickly.
For a better understanding of how you can use Splunk Observability Cloud with other Splunk platform products, see Splunk Observability Cloud and the Splunk platform scenarios for sample use cases.
Splunk Observability Cloud dashboards 🔗
The most common way of collaborating within and among teams in Splunk Observability Cloud is by sharing dashboards. See dashboards. Well-designed dashboards can provide useful and actionable insight into your system at a glance.
Allow a group of people in your organization to access a set of dashboards by creating a dashboard group. See Create and manage dashboard groups. You can see, grant, or revoke permissions to a dashboard group. To learn how, see Specify who can see and edit your dashboard groups and dashboards. You can also share individual dashboards. See Share, clone, and mirror dashboards in Splunk Observability Cloud for more information.
Splunk Observability Cloud teams and alerting 🔗
A primary means of organizing collaboration on observability and reliability across teams is by setting up Splunk Observability Cloud teams. Teams serve as a secure way to organize users by functional area. Teams also let you control access and permissions to all objects, dashboards, and queries in Splunk Observability Cloud. Splunk Observability Cloud offers enterprise-grade management with token and access control. See:ref:admin-tokens.
After you organize users into teams by functional area, you can connect users in a particular area to detectors and dashboard groups that they are most interested in. See Create and manage teams in Splunk Observability Cloud to learn more about how you can use Splunk Observability Cloud teams to facilitate collaboration within and across functional teams. Organize your Splunk Observability Cloud teams structure to reduce toil by configuring detectors to notify only the most relevant teams. For an example of increasing security while reducing toil, see Scenario: Wei maintains a secure organization with many teams and users using Splunk Observability Cloud.
Splunk APM 🔗
You can facilitate collaboration across product, strategy, and sales teams with Splunk APM. When you configure Business Workflow rules, APM tracks business key performance indicators (KPIs) as well as service level indicators (SLIs). See Configure Business Workflow rules for more information. See Scenario: Wei monitors Business Workflows to measure business KPIs for an example of how to use APM to track business KPIs and collaborate across departments.
To learn how to set up APM to correlate with business KPIs, see Correlate traces to track Business Workflows.
Splunk Log Observer Connect 🔗
You can save and share Log Observer Connect queries across observability teams when you create a valuable query that might be useful for other team members or other teams. To learn more, see Save and share Log Observer Connect queries. See Query logs in Log Observer Connect to learn the different ways you can query logs without a query language in Log Observer Connect.
Splunk Real User Monitoring (RUM) 🔗
When you set up detectors to monitor RUM browser data, iOS RUM data, or manually instrumented Android applications, you can alert directly on RUM data. See Alert on Splunk RUM data for more information. Use Splunk Observability Cloud teams to send notifications to relevant teams. See Manage team notifications in Splunk Observability Cloud to learn how to send and edit notifications.
To learn more about the kind of RUM data you can collect and alert on, see Introduction to Splunk RUM.