Skip to content
This repository was archived by the owner on Sep 2, 2025. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
125 commits
Select commit Hold shift + click to select a range
f3402b7
Added deprecation note for non-histogram MMS
johannahp-splunk Jan 21, 2025
98d1f9e
Add description for new detector list view
trangl-splunk Feb 7, 2025
b3c313d
Change page description
trangl-splunk Feb 7, 2025
0f09ee3
Change wording
trangl-splunk Feb 7, 2025
bc6dc44
Update linked detectors section
trangl-splunk Feb 10, 2025
7e245b4
Add sections on RUM and Synthetics detectors
trangl-splunk Feb 10, 2025
99b050a
Add alt text for images
trangl-splunk Feb 10, 2025
957c968
Wording
trangl-splunk Feb 10, 2025
95f8486
Resize images
trangl-splunk Feb 10, 2025
2dfcb7d
Adjust wording
trangl-splunk Feb 11, 2025
c7091dd
Style fixes for detector permissions
trangl-splunk Feb 24, 2025
463e92d
Add edit tag section and some style changes
trangl-splunk Feb 24, 2025
041c09c
Remove mention of tag limits
trangl-splunk Feb 24, 2025
199ade2
Update tag limit for detectors
trangl-splunk Feb 26, 2025
2d1e9d3
Fix line
trangl-splunk Feb 26, 2025
2bd4398
Add teams section
trangl-splunk Feb 26, 2025
a9cc5c2
Add details on teams linking
trangl-splunk Feb 28, 2025
ba1a76a
Add screenshot
trangl-splunk Feb 28, 2025
a24f55b
Increase screenshot size
trangl-splunk Feb 28, 2025
4e5cdc3
Fix typo
trangl-splunk Mar 17, 2025
7bfaea5
Wording
trangl-splunk Mar 17, 2025
f749323
Update field text to match UI
trangl-splunk Mar 17, 2025
dc94f9f
Add Issues to view list
trangl-splunk Mar 18, 2025
f684898
Add info on active alerts
trangl-splunk Mar 18, 2025
34a5464
Update screenshot
trangl-splunk Mar 18, 2025
5b117f5
Wording
trangl-splunk Mar 18, 2025
47f9e9e
Add new variables and helper functions
trangl-splunk Mar 20, 2025
17b067e
Update table formatting
trangl-splunk Mar 20, 2025
65eaa28
Adjust table widths
trangl-splunk Mar 20, 2025
86e9093
Mention message payload for tags and teams
trangl-splunk Mar 24, 2025
d67ab26
Remove payload mentions
trangl-splunk Mar 24, 2025
95847e4
Update alerts-detectors-notifications/alerts-and-detectors/create-det…
trangl-splunk Mar 24, 2025
9d1d4f9
Update alerts-detectors-notifications/alerts-and-detectors/create-det…
trangl-splunk Mar 24, 2025
2eab3f4
Update alerts-detectors-notifications/alerts-and-detectors/create-det…
trangl-splunk Mar 24, 2025
1765775
Update alerts-detectors-notifications/alerts-and-detectors/create-det…
trangl-splunk Mar 24, 2025
d1f359a
Update alerts-detectors-notifications/alerts-and-detectors/view-detec…
trangl-splunk Mar 24, 2025
9afe372
Remove extra full stop
trangl-splunk Mar 24, 2025
e9fee3f
Formatting
trangl-splunk Mar 24, 2025
27fab4e
Formatting
trangl-splunk Mar 25, 2025
f946949
Adding the fix for the undefined labels. Merge branch 'main' of githu…
jcatera-splunk Mar 25, 2025
c82542e
[O11YDOCS-7004] Bulk pause, play, delete [Apr 22 release]
Apr 9, 2025
1f9f5a1
removed logs metricization section
Apr 9, 2025
d83ff77
Updated wording
Apr 10, 2025
1b3e73f
Merge pull request #2736 from splunk/tcarter-OD-7182
tcarter-splunk Apr 10, 2025
042226f
Updated the formatting
Apr 10, 2025
3340334
Changed 'inbound' to 'outbound' as the network traffic is going from …
jcatera-splunk Apr 10, 2025
2cad6e5
Add auto-clear for Syntthetic detectors
trangl-splunk Apr 10, 2025
b85bcc9
Merge pull request #2737 from splunk/jcatera-DOCGUILD-29074
jcatera-splunk Apr 10, 2025
692475d
[DOCGUILD-29103] Remove a use case
Apr 10, 2025
52cd649
Merge pull request #2742 from splunk/adasplunk-DOCGUILD-29103
adasplunk Apr 11, 2025
92aa044
Merge pull request #2739 from splunk/trangl-o11ydocs-6985-autoclear-s…
trangl-splunk Apr 11, 2025
15c0a41
Update correct limit and notes
trangl-splunk Apr 11, 2025
44acfc3
WIF steps
aurbiztondo-splunk Apr 11, 2025
889edf5
headers
aurbiztondo-splunk Apr 11, 2025
f51ed52
Update gdi/get-data-in/connect/gcp/gcp-connect.rst
aurbiztondo-splunk Apr 11, 2025
a30b8cf
Update gdi/get-data-in/connect/gcp/gcp-connect.rst
aurbiztondo-splunk Apr 11, 2025
fef75ca
Update gdi/get-data-in/connect/gcp/gcp-connect.rst
aurbiztondo-splunk Apr 11, 2025
93a2996
Fix
aurbiztondo-splunk Apr 11, 2025
7e4c201
Updated teams topics for April release
johannahp-splunk Apr 11, 2025
4bf9183
Add customer impact
trangl-splunk Apr 13, 2025
e05e646
Remove extra space
trangl-splunk Apr 13, 2025
b891f75
Wording
trangl-splunk Apr 13, 2025
e31a896
Updated the text
Apr 14, 2025
fb914bf
Rescaled the image
Apr 14, 2025
d27f341
Rescaled the image
Apr 14, 2025
f1ab200
Rescaled the image
Apr 14, 2025
6766506
Rescaled the image
Apr 14, 2025
007c232
Updated the wording
Apr 14, 2025
46fe5e5
Update admin/references/system-limits/sys-limits-infra-details.rst
jcatera-splunk Apr 14, 2025
c8bdafd
Updating before pulling main
johannahp-splunk Apr 14, 2025
01e792d
Merge pull request #2743 from splunk/trangl-docguild-28584-query-args…
jcatera-splunk Apr 14, 2025
45ce21b
Removed em dash
Apr 14, 2025
23f7544
addressed doc feedback
Apr 14, 2025
2b2974a
Merge pull request #2746 from splunk/tcarter-DOCGUILD-28039
tcarter-splunk Apr 14, 2025
2e113a0
Updated topics and added new topic about editing services in teams
johannahp-splunk Apr 15, 2025
b864998
note
mbechtold-splunk Apr 15, 2025
cae0088
Updated dashboards/detectors instructions
johannahp-splunk Apr 15, 2025
bcc1fcc
add april release notes topic
bhillmer Apr 16, 2025
1b2fbc4
Updated more topics
johannahp-splunk Apr 16, 2025
2340bdd
Security permissions updates
johannahp-splunk Apr 16, 2025
f758841
Added new topic to TOC
johannahp-splunk Apr 16, 2025
022b3da
Formatting updates
johannahp-splunk Apr 16, 2025
8ea9e6e
Formatting updates pt 2
johannahp-splunk Apr 16, 2025
61adc7d
Small update to fix page reference
johannahp-splunk Apr 16, 2025
b5be500
Updated section about editing landing page text
johannahp-splunk Apr 16, 2025
1ba1efa
Update configure-page.rst
jcatera-splunk Apr 16, 2025
4147b17
Updates from editor
jcatera-splunk Apr 16, 2025
5385d77
Updated enhanced security topic
johannahp-splunk Apr 17, 2025
fe4e925
initial commit
mbechtold-splunk Apr 17, 2025
1cd4d14
release date
mbechtold-splunk Apr 17, 2025
fcef2a0
Merge pull request #2750 from splunk/mbechtold-otel-add-on
mbechtold-splunk Apr 17, 2025
7c6ebab
Update admin/user-management/teams/configure-page.rst
jcatera-splunk Apr 17, 2025
d3b5cfb
add release notes
bhillmer Apr 21, 2025
ef587be
fix bad refs
bhillmer Apr 21, 2025
d8757d3
fix apm teams landing page feature
bhillmer Apr 21, 2025
d08eefd
Updated based on reviewer feedback
Apr 21, 2025
5aa3eb3
Updated based on reviewer feedback
Apr 21, 2025
bd52aef
Update admin/user-management/teams/configure-page.rst
johannahp-splunk Apr 21, 2025
2027d66
Update synthetics/test-config/synth-alerts.rst
johannahp-splunk Apr 21, 2025
291d03e
Update admin/user-management/teams/manage-membership.rst
johannahp-splunk Apr 21, 2025
f2f72e7
Update admin/user-management/teams/manage-membership.rst
johannahp-splunk Apr 21, 2025
4179737
Update admin/user-management/teams/manage-membership.rst
johannahp-splunk Apr 21, 2025
a6d8d48
Merge pull request #2734 from splunk/adasplunk-O11YDOCS-7004
adasplunk Apr 21, 2025
828d2ea
Feedback updates
johannahp-splunk Apr 21, 2025
568aa3e
Merge pull request #2745 from splunk/johannahp-O11YDOCS-6546-teams
johannahp-splunk Apr 21, 2025
97d3e3c
[O11YDOCS-7006] Mention the audit log feature, which is available thr…
Apr 21, 2025
188dd03
Update synthetics/set-up-synthetics/set-up-synthetics.rst
adasplunk Apr 21, 2025
a272b66
Merge pull request #2685 from splunk/trangl-o11ydocs-6987-detectors-p…
trangl-splunk Apr 22, 2025
b113a4d
Merge pull request #2597 from splunk/trangl-o11ydocs-6188-new-detecto…
trangl-splunk Apr 22, 2025
c40285e
Merge branch 'main' into bhillmer-april2025-release-notes
bhillmer Apr 22, 2025
ec99f0e
edits from writers
bhillmer Apr 22, 2025
81d781c
Merge pull request #2744 from splunk/urbiz-OD7195-gcp-wif-updates
aurbiztondo-splunk Apr 22, 2025
3fafaa7
Merge pull request #2747 from splunk/mbechtold-archived-metrics-realm…
mbechtold-splunk Apr 22, 2025
8462c18
Merge pull request #2752 from splunk/adasplunk-O11YDOCS-7006
adasplunk Apr 22, 2025
5473bfa
Merge branch 'main' into bhillmer-april2025-release-notes
bhillmer Apr 22, 2025
77466c6
fix refs
bhillmer Apr 22, 2025
c6c3f3c
remove page header updates
bhillmer Apr 22, 2025
8050a3a
Update release-notes/2025-4-rn.rst
bhillmer Apr 22, 2025
8e9e8da
add period
bhillmer Apr 22, 2025
b26b3eb
remove synthetics bulk actions
bhillmer Apr 22, 2025
8b7b072
Merge pull request #2748 from splunk/bhillmer-april2025-release-notes
bhillmer Apr 23, 2025
6cca2c2
Updates
aurbiztondo-splunk Apr 23, 2025
1f04e4f
Correction
aurbiztondo-splunk Apr 23, 2025
dcede44
Merge pull request #2753 from splunk/urbiz-aws-sagemaker
aurbiztondo-splunk Apr 23, 2025
fdfa898
Merge branch 'main' into repo-sync
aurbiztondo-splunk Apr 23, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified _images/images-detectors-alerts/detectors-related.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified _images/logs/CreateUser.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified _images/synthetics/syn-filter-test.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
14 changes: 12 additions & 2 deletions _includes/gdi/available-aws.rst
Original file line number Diff line number Diff line change
Expand Up @@ -373,12 +373,22 @@ You can also collect data from any custom service you've created in AWS, or from
* - AWS/SageMaker
- Amazon SageMaker
- :strong:`X`
-
- :strong:`X`

* - AWS/sagemaker/Endpoints
- Amazon SageMaker Endpoints
- :strong:`X`
-
- :strong:`X`

* - AWS/sagemaker/InferenceComponents
- Amazon SageMaker Inference Components
- :strong:`X`
- :strong:`X`

* - AWS/sagemaker/InferenceRecommendationsJobs
- Amazon SageMaker Inference Recommendations Jobs
- :strong:`X`
- :strong:`X`

* - AWS/sagemaker/TrainingJobs
- Amazon SageMaker Training Jobs
Expand Down
6 changes: 3 additions & 3 deletions admin/references/system-limits/sys-limits-infra-details.rst
Original file line number Diff line number Diff line change
Expand Up @@ -244,9 +244,9 @@ Maximum SignalFlow programs per minute
Maximum number of query arguments in a filter() function
================================================================================

* :strong:`Default limit value`: 256
* :strong:`Notes`: Limit to the number of query arguments in a SignalFlow filter
* :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.
* :strong:`Default limit value`: 1024
* :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.
* :strong:`Customer impact`: SignalFlow programs that are violating the limit can't start. You immediately get an error message.

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

Expand Down
61 changes: 61 additions & 0 deletions admin/user-management/teams/associate-services.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,61 @@
.. _admin-associate-service:

********************************************************************************
Link services to teams in Splunk Observability Cloud
********************************************************************************

.. meta::
:description: Learn how to associate services with a team in Splunk Observability Cloud.

You can link services to a team to make these resources accessible on the team's landing page.

To learn more about team landing pages, see :ref:`admin-configure-page`.


.. _service-link-teams:

Services linked to teams
============================================================================

When you link services to a team, you get the following features:

* The team landing page displays lists of services and alerts for that service.

* On the APM page, filter the services listed by teams to view only the services relevant to your team.


.. _create-link-service-teams:

Link a service to a team
--------------------------------------------------------------------------------

You can link a service to a team from the team’s landing page, or the :guilabel:`Team page setup`.

To link a service to a team from the landing page, follow these steps:

#. From the :guilabel:`Services` section, select the :guilabel:`Edit services` button from the landing page.

#. From the modal, select the services that you want to add to the team.

#. (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.

To link a service to a team from the :guilabel:`Team page setup`, follow these steps:

#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
#. On the :guilabel:`Team page setup` page, go to the :guilabel:`Services` section. Add services from your environment to your team.
#. (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.

.. _remove-link-service-team:

Remove a service from a team
--------------------------------------------------------------------------

To remove a link to a service from the team landing page, follow these steps:

#. From the :guilabel:`Services` section, select :guilabel:`Edit services`.
#. Select the :guilabel:`x` to remove a service or a service attribute filter from their respective lists, then select :guilabel:`Save`.

To remove a link to a service from the :guilabel:`Team page setup`, follow these steps:

#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
#. 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.
39 changes: 27 additions & 12 deletions admin/user-management/teams/associate-team.rst
Original file line number Diff line number Diff line change
Expand Up @@ -19,23 +19,31 @@ Detectors linked to teams

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

* The team landing page displays lists of active alerts.
* The team landing page displays a list of recent alerts.

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

.. 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.


.. _create-link-detector-teams:

Link a detector to a team
--------------------------------------------------------------------------------

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`.

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.
To link a detector to a team from the landing page, follow these steps:

#. From the :guilabel:`Active alerts` section, select the :guilabel:`Edit detectors` button.
#. Select the detector you want to add from the modal, and then select :guilabel:`Add`.

To link a dashboard group to a team from the :guilabel:`Team page setup`, follow these steps:

To link a detector to a team, follow these steps:
#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
#. 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.
#. Select :guilabel:`Add`.

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.

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

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

.. 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`.


.. _remove-link-detector-team:

Remove the link between a detector and a team
--------------------------------------------------------------------------

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`.

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.
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.

To remove the link between a detector and a team, follow these steps:
To remove the link between a detector and a team on the Detectors page, follow these steps:

#. From the :guilabel:`Actions` menu for the detector, select :guilabel:`Links to teams`.
#. Select the :guilabel:`x` to remove a team from the linked teams list, then select :guilabel:`Done`.
#. 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.

To remove a link to detector from the :guilabel:`Team page setup`, follow these steps:

#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
#. 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.

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

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


.. _create-link-dashboard-group-team:

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

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

#. Select :guilabel:`Add Dashboard Group`.
#. Select :guilabel:`Edit dashboard groups`.

#. Select the dashboard group you want to link.

#. Select :guilabel:`OK`.
#. Select :guilabel:`Add`.

To link a dashboard group to a team from the :guilabel:`Team page setup`, follow these steps:

#. From the team's landing page, select the :guilabel:`Team details` button, and then select :guilabel:`Edit page`.
#. 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.
#. Select :guilabel:`Add`.

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

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

#. Select :guilabel:`Done`.


.. _remove-link-dashboard-group-team:

Remove the link between a dashboard group and a team
Expand Down
56 changes: 40 additions & 16 deletions admin/user-management/teams/configure-page.rst
Original file line number Diff line number Diff line change
Expand Up @@ -7,17 +7,16 @@ Manage team landing pages in Splunk Observability Cloud
.. meta::
:description: Learn how to view and configure an associated landing page that contains information relevant to team members.

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:
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:

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

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

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

Anyone can view the landing page for any team.


.. _view-team-landing-page:

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

#. Log in to Splunk Observability Cloud.

#. In the left navigation menu, select :menuselection:`Settings` then :menuselection:`Teams`.
#. In the left navigation menu, select :guilabel:`Settings` then :guilabel:`Teams management`.

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

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

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

#. Log in to Splunk Observability Cloud.
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.

Set up team landing page content
============================================================================

To customize the content on your team’s landing page, follow these steps:

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

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

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

.. _use-team-landing-page:

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

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

To review alerts associated with a detector linked to the team, follow these steps:
To review services linked to the team, follow these steps:

#. To view more details about each service, select the service name.

#. 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`.

#. 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.

#. Select :guilabel:`View APM page` to view additional services in your environment.

To review dashboards linked to the team, follow these steps:

#. To view a specific dashboard, select the dashboard name.
#. To view only the dashboards you created, select :guilabel:`Created by me`.
#. Select :guilabel:`View Dashboards page` to view additional dashboards in your environment.

#. 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.
You can review alerts associated with a detector linked to the team in different ways:

#. 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.
#. 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.

#. 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.
#. To see a list of active alerts for each detector linked to the team, select :guilabel:`All severities`.

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

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

* :ref:`admin-associate-team`

* :ref:`admin-associate-service`

.. _edit-landing-page-text:

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

To edit landing page text, follow these steps:

#. Select :guilabel:`Edit Description`.
#. Select the :guilabel:`Edit` button next to the team name.

#. Enter your changes in the edit box.
#. Enter your changes in the modal.

#. Select :guilabel:`Save`.
5 changes: 3 additions & 2 deletions admin/user-management/teams/enhanced-team-security.rst
Original file line number Diff line number Diff line change
Expand Up @@ -121,10 +121,11 @@ To learn more about enabling enhanced team security, see :ref:`admin-team-contro
- No

* - :strong:`Leave team`
- * Yes, if on a team
- * Yes, if on a team
* Not applicable, if not on a team
- Yes
- Yes
- * Yes, when enhanced team security is turned off
* No, when enhanced team security is turned on
- Not applicable: A user must be on a team to leave a team

Permission to link a detector to a team is based on the detector's permissions. For example, if the user has write permission for a detector, they can link it to a team. To learn more, see :ref:`detector-manage-permissions`.
Expand Down
Loading