Skip to content

Commit 38c8549

Browse files
Merge pull request splunk#1727 from splunk/repo-sync
Pulling refs/heads/main into main
2 parents f226324 + fdfa898 commit 38c8549

File tree

32 files changed

+511
-217
lines changed

32 files changed

+511
-217
lines changed
124 KB
Loading
242 KB
Loading
63.4 KB
Loading

_images/logs/CreateUser.png

14.8 KB
Loading
-404 Bytes
Loading

_includes/gdi/available-aws.rst

Lines changed: 12 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -373,12 +373,22 @@ You can also collect data from any custom service you've created in AWS, or from
373373
* - AWS/SageMaker
374374
- Amazon SageMaker
375375
- :strong:`X`
376-
-
376+
- :strong:`X`
377377

378378
* - AWS/sagemaker/Endpoints
379379
- Amazon SageMaker Endpoints
380380
- :strong:`X`
381-
-
381+
- :strong:`X`
382+
383+
* - AWS/sagemaker/InferenceComponents
384+
- Amazon SageMaker Inference Components
385+
- :strong:`X`
386+
- :strong:`X`
387+
388+
* - AWS/sagemaker/InferenceRecommendationsJobs
389+
- Amazon SageMaker Inference Recommendations Jobs
390+
- :strong:`X`
391+
- :strong:`X`
382392

383393
* - AWS/sagemaker/TrainingJobs
384394
- Amazon SageMaker Training Jobs

admin/references/system-limits/sys-limits-infra-details.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -244,9 +244,9 @@ Maximum SignalFlow programs per minute
244244
Maximum number of query arguments in a filter() function
245245
================================================================================
246246

247-
* :strong:`Default limit value`: 256
248-
* :strong:`Notes`: Limit to the number of query arguments in a SignalFlow filter
249-
* :strong:`Customer impact`: Maximum number of derived MTS per SignalFlow program, where derived MTS are temporary MTS that a SignalFlow function or method has to maintain in memory. For example, if there are 20,000 MTS for the metric ``jvm.load``, and each MTS comes from a unique host , then ``"data('jvm.load').sum(by=['host']).publish()"`` tracks 40,000 derived MTS. The ``data()`` function uses 20,000, and the ``sum()`` uses another 20,000. The number of input MTS is still 20,000.
247+
* :strong:`Default limit value`: 1024
248+
* :strong:`Notes`: Limit to the number of query arguments in a SignalFlow filter. This limit includes global filters in dashboards as well as any internal filters.
249+
* :strong:`Customer impact`: SignalFlow programs that are violating the limit can't start. You immediately get an error message.
250250

251251
.. _maximum-number-of-detectors-per-org:
252252

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,61 @@
1+
.. _admin-associate-service:
2+
3+
********************************************************************************
4+
Link services to teams in Splunk Observability Cloud
5+
********************************************************************************
6+
7+
.. meta::
8+
:description: Learn how to associate services with a team in Splunk Observability Cloud.
9+
10+
You can link services to a team to make these resources accessible on the team's landing page.
11+
12+
To learn more about team landing pages, see :ref:`admin-configure-page`.
13+
14+
15+
.. _service-link-teams:
16+
17+
Services linked to teams
18+
============================================================================
19+
20+
When you link services to a team, you get the following features:
21+
22+
* The team landing page displays lists of services and alerts for that service.
23+
24+
* On the APM page, filter the services listed by teams to view only the services relevant to your team.
25+
26+
27+
.. _create-link-service-teams:
28+
29+
Link a service to a team
30+
--------------------------------------------------------------------------------
31+
32+
You can link a service to a team from the team’s landing page, or the :guilabel:`Team page setup`.
33+
34+
To link a service to a team from the landing page, follow these steps:
35+
36+
#. From the :guilabel:`Services` section, select the :guilabel:`Edit services` button from the landing page.
37+
38+
#. From the modal, select the services that you want to add to the team.
39+
40+
#. (Optional) Add a service attribute filter in order to populate all services that contain the specified attribute on the team landing page. This filter groups services by a specific property or namespace. For example, adding the attribute ``service.namespace = apm`` will display all services with the APM namespace on your team landing page.
41+
42+
To link a service to a team from the :guilabel:`Team page setup`, follow these steps:
43+
44+
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
45+
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Services` section. Add services from your environment to your team.
46+
#. (Optional) Add a service attribute filter in order to populate all services that contain the specified attribute on the team landing page. This filter groups services by a specific property or namespace. For example, adding the attribute ``service.namespace = apm`` will display all services with the APM namespace on your team landing page.
47+
48+
.. _remove-link-service-team:
49+
50+
Remove a service from a team
51+
--------------------------------------------------------------------------
52+
53+
To remove a link to a service from the team landing page, follow these steps:
54+
55+
#. From the :guilabel:`Services` section, select :guilabel:`Edit services`.
56+
#. Select the :guilabel:`x` to remove a service or a service attribute filter from their respective lists, then select :guilabel:`Save`.
57+
58+
To remove a link to a service from the :guilabel:`Team page setup`, follow these steps:
59+
60+
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
61+
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Services` section. Select the :guilabel:`x` to remove a service or a service attribute filter from their respective lists. Your changes will be reflected on the team landing page.

admin/user-management/teams/associate-team.rst

Lines changed: 27 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -19,23 +19,31 @@ Detectors linked to teams
1919

2020
When you link detectors to a team, you get the following features:
2121

22-
* The team landing page displays lists of active alerts.
22+
* The team landing page displays a list of recent alerts.
2323

24-
* On the Alerts page, users can use filters to display only those detectors linked to a specific team.
24+
* On the :guilabel:`Detectors & SLOs` page, users can use filters to display only detectors linked to a specific team.
2525

2626
.. note:: You can manually add a team as a notification recipient for any detector. You don't have to link the detector to the team.
2727

28-
2928
.. _create-link-detector-teams:
3029

3130
Link a detector to a team
3231
--------------------------------------------------------------------------------
3332

3433
You can only link a detector to a team if you have write permission for the detector. To learn more, see :ref:`detector-manage-permissions`.
3534

36-
You can link a detector to a team when you are viewing the :guilabel:`Detectors` tab on the :guilabel:`Alerts` page or when you are viewing a specific detector.
35+
To link a detector to a team from the landing page, follow these steps:
36+
37+
#. From the :guilabel:`Active alerts` section, select the :guilabel:`Edit detectors` button.
38+
#. Select the detector you want to add from the modal, and then select :guilabel:`Add`.
39+
40+
To link a dashboard group to a team from the :guilabel:`Team page setup`, follow these steps:
3741

38-
To link a detector to a team, follow these steps:
42+
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
43+
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Detectors` section and select :guilabel:`Edit detectors`. Add detectors to your team from the modal.
44+
#. Select :guilabel:`Add`.
45+
46+
You can link a detector to a team when you are viewing the :guilabel:`Detectors` tab on the :guilabel:`Detectors & SLOs` page or when you are viewing a specific detector.
3947

4048
#. From the :guilabel:`Actions` menu for the detector, select :guilabel:`Links to teams`.
4149

@@ -45,22 +53,25 @@ To link a detector to a team, follow these steps:
4553

4654
.. note:: Sending alert notifications to a team doesn't necessarily mean that every team member is notified. The team's notification policy determines which team members receive notifications. To learn more about configuring team notification policies, see :ref:`admin-team-notifications`.
4755

48-
4956
.. _remove-link-detector-team:
5057

5158
Remove the link between a detector and a team
5259
--------------------------------------------------------------------------
5360

5461
To remove a link between a detector and a team, you need to have write permission for the detector. To learn more, see :ref:`detector-manage-permissions`.
5562

56-
You can remove the link between a detector and a team when you are viewing the :guilabel:`Detectors` tab on the :guilabel:`Alerts` page or when you are viewing a specific detector.
63+
You can remove the link between a detector and a team when you are viewing the :guilabel:`Detectors` tab on the :guilabel:`Detectors & SLOs` page or when you are viewing a specific detector.
5764

58-
To remove the link between a detector and a team, follow these steps:
65+
To remove the link between a detector and a team on the Detectors page, follow these steps:
5966

6067
#. From the :guilabel:`Actions` menu for the detector, select :guilabel:`Links to teams`.
6168
#. Select the :guilabel:`x` to remove a team from the linked teams list, then select :guilabel:`Done`.
6269
#. If the team is a notification recipient for the detector, Splunk Observability Cloud asks if you want to stop sending notifications to the team. Select :guilabel:`Yes` to remove the team as a recipient from each detector rule. Select :guilabel:`No` to leave all recipients as is.
6370

71+
To remove a link to detector from the :guilabel:`Team page setup`, follow these steps:
72+
73+
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
74+
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Detectors` section. Select the :guilabel:`x` to remove a detector. Your changes will automatically be reflected on the landing page.
6475

6576
.. _dashboard-groups-link-team-features:
6677

@@ -87,7 +98,6 @@ The following table provides details about which dashboard group types you can l
8798
* - User dashboard group
8899
- You can't link a user dashboard group to a team.
89100

90-
91101
.. _create-link-dashboard-group-team:
92102

93103
Link a dashboard group to a team
@@ -99,11 +109,17 @@ To link a dashboard group to a team from the team landing page, follow these ste
99109

100110
#. Access the team landing page. To learn how to access team landing pages, see :ref:`view-team-landing-page`.
101111

102-
#. Select :guilabel:`Add Dashboard Group`.
112+
#. Select :guilabel:`Edit dashboard groups`.
103113

104114
#. Select the dashboard group you want to link.
105115

106-
#. Select :guilabel:`OK`.
116+
#. Select :guilabel:`Add`.
117+
118+
To link a dashboard group to a team from the :guilabel:`Team page setup`, follow these steps:
119+
120+
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
121+
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Dashboards` section and select :guilabel:`Edit dashboard groups`. Add dashboard groups to your team from the modal.
122+
#. Select :guilabel:`Add`.
107123

108124
To link a dashboard group to a team from the dashboard group:
109125

@@ -117,7 +133,6 @@ To link a dashboard group to a team from the dashboard group:
117133

118134
#. Select :guilabel:`Done`.
119135

120-
121136
.. _remove-link-dashboard-group-team:
122137

123138
Remove the link between a dashboard group and a team

admin/user-management/teams/configure-page.rst

Lines changed: 40 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -7,17 +7,16 @@ Manage team landing pages in Splunk Observability Cloud
77
.. meta::
88
:description: Learn how to view and configure an associated landing page that contains information relevant to team members.
99

10-
Every team has an associated landing page that contains information relevant to team members. A landing page brings together dashboard groups and alerts triggered by detectors that are linked to the team. The landing page has the following sections:
10+
Every team has a landing page that contains information relevant to team members. A landing page brings together dashboard groups and alerts triggered by detectors that are linked to the team. The landing page has the following sections:
1111

12-
* A customizable text section to provide helpful information to team members. In this section, you can use Markdown-formatted text.
12+
* A list of services managed by your team.
1313

1414
* A count of active alerts from detectors linked to the team, grouped by severity.
1515

1616
* Links to one or more dashboard groups linked to the team.
1717

1818
Anyone can view the landing page for any team.
1919

20-
2120
.. _view-team-landing-page:
2221

2322
View a team landing page
@@ -29,20 +28,26 @@ To see the landing page for any team, follow these steps:
2928

3029
#. Log in to Splunk Observability Cloud.
3130

32-
#. In the left navigation menu, select :menuselection:`Settings` then :menuselection:`Teams`.
31+
#. In the left navigation menu, select :guilabel:`Settings` then :guilabel:`Teams management`.
3332

3433
#. A table of current teams appears in the main panel.
3534

36-
#. Select a team name to see its landing page.
35+
#. Select a team name to view its landing page, or select :guilabel:`Go to team page` from the :guilabel:`Actions` menu.
3736

38-
To see the landing page for your team, follow these steps:
37+
#. (Optional) Select :guilabel:`Join team` to add yourself as a member of the team.
3938

40-
#. Log in to Splunk Observability Cloud.
39+
Alternatively, you can view the landing page for teams you are already part of on the Splunk Observability Cloud home page. The teams you are part of display as a tab on the home page.
40+
41+
Set up team landing page content
42+
============================================================================
43+
44+
To customize the content on your team’s landing page, follow these steps:
4145

42-
#. In the left navigation menu, select :menuselection:`Dashboards`.
46+
#. From a team's landing page, select the :guilabel:`Team details` button. From the side panel that appears, select :guilabel:`Edit page`.
4347

44-
#. In the :guilabel:`My Teams` area, select a team name to see its team landing page.
48+
#. Add and remove specific objects from the team's landing page page, such as services and detectors, from the :guilabel:`Team page setup`.
4549

50+
#. Your changes will automatically populate on the team landing page.
4651

4752
.. _use-team-landing-page:
4853

@@ -51,17 +56,36 @@ Use a team landing page
5156

5257
Use a team landing page as your starting point for monitoring important data.
5358

54-
To review alerts associated with a detector linked to the team, follow these steps:
59+
To review services linked to the team, follow these steps:
60+
61+
#. To view more details about each service, select the service name.
62+
63+
#. To view additional properties for each service, such as the endpoints or traces associated with each service, select the three-dot :guilabel:`Actions` menu and choose one of the options listed. The corresponding page in Splunk APM opens. To learn more about using the service view in APM, see :ref:`apm-service-view`.
64+
65+
#. To see the details of an alert for one of the services associated with your team, select the alert name in the :guilabel:`Alerts` column.
66+
67+
#. Select :guilabel:`View APM page` to view additional services in your environment.
68+
69+
To review dashboards linked to the team, follow these steps:
70+
71+
#. To view a specific dashboard, select the dashboard name.
72+
#. To view only the dashboards you created, select :guilabel:`Created by me`.
73+
#. Select :guilabel:`View Dashboards page` to view additional dashboards in your environment.
5574

56-
#. To see all active alerts, select :guilabel:`Team Alerts`. The Alerts page for the team appears. You see all active alerts for detectors linked to the team.
75+
You can review alerts associated with a detector linked to the team in different ways:
5776

58-
#. To see all active alerts for a specific severity level, select the severity. The Alert page for the team appears. You see active alerts for detectors linked to the team, filtered by the severity level you selected.
77+
#. To see all active alerts for a specific severity level, select the severity. You see active alerts for detectors linked to the team, filtered by the severity level you selected.
5978

60-
#. To see a list of active alerts for each detector linked to the team, select :guilabel:`Team Detectors`. The Alert page for the team appears, listing the name of the detector that issued each alert.
79+
#. To see a list of active alerts for each detector linked to the team, select :guilabel:`All severities`.
6180

62-
To learn more about linking teams to detectors and dashboard groups, see :ref:`admin-associate-team`,
81+
#. Select :guilabel:`View Detectors & SLOs page` to view additional detectors in your environment.
6382

83+
To learn more about linking services and other objects to your team landing page, see:
6484

85+
* :ref:`admin-associate-team`
86+
87+
* :ref:`admin-associate-service`
88+
6589
.. _edit-landing-page-text:
6690

6791
Edit the landing page text
@@ -77,8 +101,8 @@ To learn about which roles can edit landing page text, see :ref:`about-team-role
77101

78102
To edit landing page text, follow these steps:
79103

80-
#. Select :guilabel:`Edit Description`.
104+
#. Select the :guilabel:`Edit` button next to the team name.
81105

82-
#. Enter your changes in the edit box.
106+
#. Enter your changes in the modal.
83107

84108
#. Select :guilabel:`Save`.

0 commit comments

Comments
 (0)