From ba9e018b83214afe709fb51dec2e1c7ed7910e18 Mon Sep 17 00:00:00 2001 From: John Pipkin Date: Fri, 21 Jun 2024 10:45:57 -0500 Subject: [PATCH 01/12] App Catalog updates --- docs/cloud-soar/overview.md | 1 - docs/cse/introduction-to-cloud-siem.md | 1 - docs/get-started/quickstart.md | 2 +- docs/integrations/index.md | 5 +---- 4 files changed, 2 insertions(+), 7 deletions(-) diff --git a/docs/cloud-soar/overview.md b/docs/cloud-soar/overview.md index 79257d6e82..280f74d904 100644 --- a/docs/cloud-soar/overview.md +++ b/docs/cloud-soar/overview.md @@ -85,7 +85,6 @@ Use the top menu to access: * Go To icon [**Go To...**](#go-to-menu) Launch Sumo Logic features, including for Cloud SOAR. * Help icon **Help**. Access links to documentation, support, community, release notes, and system status. -* App Catalog icon [**App Catalog**](/docs/integrations/). Open the App Catalog. * Configuration icon [**Configuration**](#configuration-menu). Configure Sumo Logic features, including for Cloud SOAR. * Administration icon [**Administration**](#administration-menu). Administer Sumo Logic features, including for Cloud SOAR. * Profile icon **Profile**. View your notification and [preference](/docs/get-started/account-settings-preferences/) settings. diff --git a/docs/cse/introduction-to-cloud-siem.md b/docs/cse/introduction-to-cloud-siem.md index c0810ba2db..3b2f356b51 100644 --- a/docs/cse/introduction-to-cloud-siem.md +++ b/docs/cse/introduction-to-cloud-siem.md @@ -142,7 +142,6 @@ This menu appears at the top of the screen:
Go To icon **Go To...** Launch Sumo Logic features, including for Cloud SIEM. * Help icon **Help**. Access links to documentation, support, community, release notes, and system status. -* App Catalog icon [**App Catalog**](/docs/integrations/). Open the App Catalog. * Configuration icon [**Configuration**](#configuration-menu-1). Configure Sumo Logic features, including for Cloud SIEM. * Administration icon **Administration**. Access Sumo Logic administration settings, such as for for [account](/docs/manage/), [users and roles](/docs/manage/users-roles/), and [account security](/docs/manage/security/). * Profile icon **Profile**. View your notification and [preference](/docs/get-started/account-settings-preferences/) settings. diff --git a/docs/get-started/quickstart.md b/docs/get-started/quickstart.md index 785be8ea42..a162bffcd8 100644 --- a/docs/get-started/quickstart.md +++ b/docs/get-started/quickstart.md @@ -38,7 +38,7 @@ OpenTelemetry is our preferred collector unless you're configuring security data #### OpenTelemetry Collector 1. Log in to Sumo Logic. -1. In the main Sumo Logic menu, select **App Catalog**. +1. In the main Sumo Logic menu, select **App Catalog**. 1. Click the app you'd like to install. 1. Click the **Add a New Collector** option during app installation. :::note diff --git a/docs/integrations/index.md b/docs/integrations/index.md index ff4781521d..db419edc6b 100644 --- a/docs/integrations/index.md +++ b/docs/integrations/index.md @@ -16,10 +16,7 @@ import Iframe from 'react-iframe'; In this section, you'll find documentation for our **App Catalog**, encompassing Sumo Logic apps, webhooks, and other integrations. - To access the App Catalog, in the main Sumo Logic menu select **App Catalog**. - +To access the App Catalog, in the main Sumo Logic menu select **App Catalog**. When you install our apps, they will be tailored to your source configurations and placed in your preferred folder. This setup allows you to start gaining insights from your data sources through [Dashboards](/docs/dashboards) and example searches designed for common use cases. From 61a47d404ea6d736aedbefca868212affa585a3a Mon Sep 17 00:00:00 2001 From: John Pipkin Date: Fri, 21 Jun 2024 12:30:36 -0500 Subject: [PATCH 02/12] Add the rest --- docs/alerts/monitors/alert-grouping.md | 4 ++-- docs/alerts/monitors/alert-response.md | 2 +- docs/alerts/monitors/create-monitor.md | 2 +- docs/alerts/monitors/muting-schedules.md | 6 +++--- docs/alerts/monitors/settings.md | 8 ++++---- docs/alerts/webhook-connections/servicenow/index.md | 6 +++++- docs/apm/real-user-monitoring/dashboards.md | 2 +- docs/apm/real-user-monitoring/index.md | 2 +- docs/apm/traces/quickstart.md | 2 +- docs/apm/traces/services-list-map.md | 2 +- docs/apm/traces/spans.md | 2 +- docs/apm/traces/tracing-dashboards.md | 2 +- docs/apm/traces/view-and-investigate-traces.md | 2 +- docs/dashboards/explore-view.md | 11 +++++------ docs/integrations/containers-orchestration/kafka.md | 2 +- .../containers-orchestration/rabbitmq.md | 2 +- docs/integrations/databases/cassandra.md | 2 +- docs/integrations/databases/elasticsearch.md | 2 +- docs/integrations/databases/oracle.md | 2 +- docs/integrations/web-servers/apache-tomcat.md | 2 +- docs/integrations/web-servers/apache.md | 2 +- docs/integrations/web-servers/haproxy.md | 2 +- docs/integrations/web-servers/iis-10.md | 2 +- docs/integrations/web-servers/squid-proxy.md | 2 +- docs/integrations/web-servers/varnish.md | 2 +- docs/manage/health-events.md | 2 +- docs/metrics/introduction/index.md | 2 +- docs/metrics/metrics-queries/metrics-explorer.md | 2 +- docs/observability/application-components.md | 2 +- .../deploy-use-aws-observability/view-dashboards.md | 2 +- .../add-new-aws-service.md | 2 +- docs/observability/kubernetes/monitoring.md | 2 +- .../kubernetes/troubleshoot-with-explore.md | 2 +- .../reliability-management-slo/create-slo.md | 13 +++++++++---- .../reliability-management-slo/dashboards.md | 2 +- .../reliability-management-slo/index.md | 2 +- i18n/ja/alerts/alerts/monitors/alert-response.md | 13 ++++--------- 37 files changed, 62 insertions(+), 59 deletions(-) diff --git a/docs/alerts/monitors/alert-grouping.md b/docs/alerts/monitors/alert-grouping.md index e141b60193..19b54f9627 100644 --- a/docs/alerts/monitors/alert-grouping.md +++ b/docs/alerts/monitors/alert-grouping.md @@ -20,7 +20,7 @@ Alert Grouping works for both Logs and Metrics Monitors. ### Metrics -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 2. Click **Add a New monitor**. 3. Select **Metrics** as the type of Monitor. 4. Enter your metrics query, then select your desired Alert Grouping option. @@ -32,7 +32,7 @@ Alert Grouping works for both Logs and Metrics Monitors. ### Logs -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 2. Click **Add a New monitor**. 3. Select **Logs** as the type of Monitor. 4. Enter your logs query, then select your desired Alert Grouping option: diff --git a/docs/alerts/monitors/alert-response.md b/docs/alerts/monitors/alert-response.md index f31f94987a..2f9e1a60e7 100644 --- a/docs/alerts/monitors/alert-response.md +++ b/docs/alerts/monitors/alert-response.md @@ -67,7 +67,7 @@ The Alerts list shows all of your Alerts from Monitors triggered within the pas To access the Alerts list, click the bell icon in the top menu.
alert-list-page-bell-border To filter or sort by category (e.g., **Name**, **Severity**, **Status**), you can use the search bar or click on a column header.
![search alert list.png](/img/monitors/search-alert-list.png) diff --git a/docs/alerts/monitors/create-monitor.md b/docs/alerts/monitors/create-monitor.md index 0979529771..44eb12f07e 100644 --- a/docs/alerts/monitors/create-monitor.md +++ b/docs/alerts/monitors/create-monitor.md @@ -21,7 +21,7 @@ This topic shows you how to create a monitor. #### From your Monitors page -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Click on the **Add** button > **New Monitor** to add a new Monitor. The **New Monitor** dialog box will appear. #### From your Dashboard diff --git a/docs/alerts/monitors/muting-schedules.md b/docs/alerts/monitors/muting-schedules.md index 062b0bb0fa..f6a4a52b0c 100644 --- a/docs/alerts/monitors/muting-schedules.md +++ b/docs/alerts/monitors/muting-schedules.md @@ -20,7 +20,7 @@ If fine-grained permissions are enabled for your account, you'll need the **Mana To set a muting schedule: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Muting Schedules**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Muting Schedules**. 1. Click **Add** > **New Schedule**. 1. Define your **Schedule Configuration** using the provided UI or [*RRule*](https://freetools.textmagic.com/rrule-generator), a syntax that allows you to specify schedule recurrence rules for calendar dates programmatically. 1. Define your **Scope**, where you associate one or more monitors with this schedule. @@ -29,7 +29,7 @@ To set a muting schedule: ### Validate Muting Schedule To confirm that your Muting Schedule has been applied successfully: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Find your monitor in the list and check the **Status** column, where you should see the muted indicator. mute schedule @@ -42,6 +42,6 @@ Optionally, you can apply a Muting Schedule to an entire alert group, rather tha Once you've set up an alert group and a Muting Schedule, here's how how to link them together: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Select the alert group variable you want to mute. In this example, we'll choose `region`.
mute-sched-alert-groups1.png 1. Under **(1) Trigger Conditions**, find the alert group you want to use. In this example, we've set up the condition so that if the `region` is `us-east-1`, alerts will be muted every third Saturday.
mute-sched-alert-groups2.png diff --git a/docs/alerts/monitors/settings.md b/docs/alerts/monitors/settings.md index 0664d154e4..a59a2d57cb 100644 --- a/docs/alerts/monitors/settings.md +++ b/docs/alerts/monitors/settings.md @@ -11,7 +11,7 @@ The Monitors page allows you to view, create, manage, and organize your Monitors To access the Monitors page, in the main Sumo Logic menu select **Manage Data > Monitoring > Monitors**. The page displays the following information: @@ -100,7 +100,7 @@ Adding a **Tag** to a Monitor can help you categorize, search, filter, and corre To add a tag to an existing monitor: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Double-click on any monitor in your list. 1. In the side panel, click **Edit**. 1. Under step 4 (**Monitor Details**), create a tag using the `key=value` format. @@ -108,7 +108,7 @@ To add a tag to an existing monitor: To add a tag while creating a new monitor: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Click **Add** > **New Monitor**. 1. Follow the steps to create a new monitor. When you get to step 4 (**Monitor Details**), you can: * Create a new tag using the `key=value` format. @@ -128,7 +128,7 @@ Access to folders that contain Monitors is controlled by permissions. If you hav * **Manage**. Ability to move folders and to grant other roles permissions to the folder. If you grant this permission, the permissions listed above will be granted as well. To set permissions for a Monitors folder: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 2. Right-click on the folder whose permissions you want to set, and click **Edit Permissions.** This option is present only if you have been granted **Manage** permission for the folder. 3. On the edit popup, note that the user who created the folder, and roles with the **Admin Monitors** capability, automatically have all permissions to the folder. diff --git a/docs/alerts/webhook-connections/servicenow/index.md b/docs/alerts/webhook-connections/servicenow/index.md index 3233de5122..e4e44f8825 100644 --- a/docs/alerts/webhook-connections/servicenow/index.md +++ b/docs/alerts/webhook-connections/servicenow/index.md @@ -8,7 +8,11 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; Your org can use collected data to investigate issues across your deployment and then upload it to ServiceNow through the use of scheduled searches. After saving a search, results are available in ServiceNow. Additionally, you can launch ad hoc ServiceNow investigations using search results in Sumo Logic. -To access [ServiceNow connections](/docs/alerts/webhook-connections/servicenow/), go to **Manage Data** > **Monitoring** > **Connections**. From here, you can search, edit, delete, and view of the details of Connections. + To access ServiceNow connections, in the main Sumo Logic menu select **Manage Data > Monitoring > Connections**. + + + +From here, you can search, edit, delete, and view of the details of [ServiceNow connections](/docs/alerts/webhook-connections/servicenow/). In this section, we'll introduce the following concepts: diff --git a/docs/apm/real-user-monitoring/dashboards.md b/docs/apm/real-user-monitoring/dashboards.md index 0fafc5efa2..84f43ca812 100644 --- a/docs/apm/real-user-monitoring/dashboards.md +++ b/docs/apm/real-user-monitoring/dashboards.md @@ -27,7 +27,7 @@ If your RUM app is removed accidentally, you'll need to install it manually: Once the RUM app has been installed, use the Real User Monitoring view to gain visibility into your web app's performance and end-user activity, such as geographic location, browser type, operating systems used. These dashboards visualize RUM metrics gathered from browser tracing instrumentation. -1. Click the **+ New** button at the top of the screen and select **Explore**. Then in the upper-left corner of the screen, select **Real User Monitoring** from the dropdown menu. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then in the upper-left corner of the screen, select **Real User Monitoring** from the dropdown menu. 1. Select your desired dashboard from **Dashboard** dropdown menu in the header:
![explore rum with red box.png](/img/rum/explore-rum-with-red-box.png)
There are three dashboard types on the **Application**, **Service**, and **Environment** levels, and a single one on the **Action type** and **Action** levels. 1. Set your desired filters. RUM data is organized on five levels: * **Application**: corresponds to the value of the application tag set in your [RUM script](/docs/apm/real-user-monitoring/configure-data-collection/#step-2-add-rum-script-to-your-page-header). This should correspond to your whole website defined by its business function, such as `the-coffee-bar-app`. diff --git a/docs/apm/real-user-monitoring/index.md b/docs/apm/real-user-monitoring/index.md index 7ae4a6d361..565498c2d2 100644 --- a/docs/apm/real-user-monitoring/index.md +++ b/docs/apm/real-user-monitoring/index.md @@ -49,7 +49,7 @@ Access Traces to confirm that your Sumo Logic service package has been upgraded To access Traces, click the **+ New** button at the top of the screen and select **Traces**. ## Guides diff --git a/docs/apm/traces/quickstart.md b/docs/apm/traces/quickstart.md index d6f382dcfd..19d0a0adbb 100644 --- a/docs/apm/traces/quickstart.md +++ b/docs/apm/traces/quickstart.md @@ -20,7 +20,7 @@ You can access Traces if your Sumo Logic service package has been upgraded to in To access Traces, click the **+ New** button at the top of the screen and select **Traces**. ## Micro Lesson diff --git a/docs/apm/traces/services-list-map.md b/docs/apm/traces/services-list-map.md index 4c55354158..6386c07968 100644 --- a/docs/apm/traces/services-list-map.md +++ b/docs/apm/traces/services-list-map.md @@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; To access Services, click the **+ New** button at the top of the screen and select **Services**. ## Services List view diff --git a/docs/apm/traces/spans.md b/docs/apm/traces/spans.md index 9bedfe148c..f89fc260a3 100644 --- a/docs/apm/traces/spans.md +++ b/docs/apm/traces/spans.md @@ -10,7 +10,7 @@ The **Spans** page allows you to filter and aggregate your trace data at the raw To access Spans, click the **+ New** button at the top of the screen and select **Spans**. A new Spans page opens. Data is displayed once you run a query. diff --git a/docs/apm/traces/tracing-dashboards.md b/docs/apm/traces/tracing-dashboards.md index 772c5feaf3..da032f9a4b 100644 --- a/docs/apm/traces/tracing-dashboards.md +++ b/docs/apm/traces/tracing-dashboards.md @@ -8,7 +8,7 @@ description: Explore and create Tracing dashboards, install apps, and more. import useBaseUrl from '@docusaurus/useBaseUrl'; To access APM hierarchies: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select an **APM:** hierarchy from the dropdown menu. An expandable list of your hierarchy appears in the panel. Out-of-the-box dashboards are available as three hierarchies. diff --git a/docs/apm/traces/view-and-investigate-traces.md b/docs/apm/traces/view-and-investigate-traces.md index 03b78d4217..37fa822f49 100644 --- a/docs/apm/traces/view-and-investigate-traces.md +++ b/docs/apm/traces/view-and-investigate-traces.md @@ -12,7 +12,7 @@ You can visualize your Traces data through filtered trace lists and icicle chart To access Traces, click the **+ New** button at the top of the screen and select **Traces**. Here, you can run a Trace query, view your **Trace Duration Breakdown Chart**, and explore your **Traces matching queries** table. diff --git a/docs/dashboards/explore-view.md b/docs/dashboards/explore-view.md index 31b6f85103..62fe5d8d73 100644 --- a/docs/dashboards/explore-view.md +++ b/docs/dashboards/explore-view.md @@ -11,18 +11,17 @@ Sumo Logic provides monitoring dashboards for an intuitive visual hierarchy of y To access the monitoring dashboards, click the **+ New** button at the top of the screen and select **Explore**. Then in the upper-left corner of the screen, select from the dropdown menu under **Explore By**. - ## Navigating To navigate, do the following: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 3. Drill down further until you find your desired component which you'd like to explore. Metrics will be displayed/visualized as dashboards. ### Stack linking diff --git a/docs/integrations/containers-orchestration/kafka.md b/docs/integrations/containers-orchestration/kafka.md index 6360255efb..564400e3b6 100644 --- a/docs/integrations/containers-orchestration/kafka.md +++ b/docs/integrations/containers-orchestration/kafka.md @@ -410,7 +410,7 @@ Sumo Logic has provided out-of-the-box alerts available through [Sumo Logic moni * For alerts applicable only to a specific cluster, your custom filter would be: `messaging_cluster=Kafka-prod.01` * For alerts applicable to all clusters that start with Kafka-prod, your custom filter would be: `messaging_cluster=Kafka-prod*` * For alerts applicable to a specific cluster within a production environment, your custom filter would be: `messaging_cluster=Kafka-1` and `environment=prod` (This assumes you have set the optional environment tag while configuring collection) - 2. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. + 2. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 3. Click **Add** 4. Click Import to import monitors from the JSON above. diff --git a/docs/integrations/containers-orchestration/rabbitmq.md b/docs/integrations/containers-orchestration/rabbitmq.md index a10417ed68..6c111472b4 100644 --- a/docs/integrations/containers-orchestration/rabbitmq.md +++ b/docs/integrations/containers-orchestration/rabbitmq.md @@ -381,7 +381,7 @@ There are limits to how many alerts can be enabled. For more information, see [M * For alerts applicable only to a specific cluster, your custom filter would be: `messaging_cluster=dev-rabbitmq01` * For alerts applicable to all clusters that start with RabbitMQ-prod, your custom filter would be: `messaging_cluster=RabbitMQ-prod*` * For alerts applicable to a specific cluster within a production environment, your custom filter would be: `messaging_cluster=dev-rabbitmq01 AND environment=prod` (This assumes you have set the optional environment tag while configuring collection) -3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 4. Click **Add**. 5. Click **Import**. 6. On the **Import Content popup**, enter **RabbitMQ** in the Name field, paste in the JSON into the the popup, and click **Import**. diff --git a/docs/integrations/databases/cassandra.md b/docs/integrations/databases/cassandra.md index 20776535b5..c87baa56db 100644 --- a/docs/integrations/databases/cassandra.md +++ b/docs/integrations/databases/cassandra.md @@ -543,7 +543,7 @@ There are limits to how many alerts can be enabled. For more information, see [M * For alerts applicable only to a specific cluster, your custom filter would be: `db_cluster=dev-cassandra-01`. * For alerts applicable to all clusters that start with `cassandra-prod`, your custom filter would be: `db_cluster=cassandra-prod*`. * For alerts applicable to specific clusters, within a production environment, your custom filter would be:`db_cluster=dev-cassandra-01` AND `environment=prod`. This assumes you have set the optional environment tag while configuring collection. -3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 4. Click **Add**. 5. Click **Import**. 6. On the **Import Content popup**, enter **Cassandra** in the Name field, paste the JSON into the popup, and click **Import**. diff --git a/docs/integrations/databases/elasticsearch.md b/docs/integrations/databases/elasticsearch.md index 537aaefd86..9d090a2bc2 100644 --- a/docs/integrations/databases/elasticsearch.md +++ b/docs/integrations/databases/elasticsearch.md @@ -381,7 +381,7 @@ To install these monitors, you must have the **Manage Monitors** role capability * For alerts applicable only to a specific cluster, your custom filter would be: `db_cluster=dev-elasticsearch-01` * For alerts applicable to all clusters that start with `elasticsearch-prod`, your custom filter would be: `db_cluster=elasticsearch-prod*` * For alerts applicable to a specific clusters, within a production environment, your custom filter would be: `db_cluster=dev-elasticsearch-01` AND `environment=prod`. This assumes you have set the optional environment tag while configuring collection. -3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 4. Click **Add**. 5. Click **Import**. 6. On the **Import Content popup**, enter **Elasticsearch** in the Name field, paste in the JSON into the popup, and click **Import**. diff --git a/docs/integrations/databases/oracle.md b/docs/integrations/databases/oracle.md index 830cc9b251..dd4d42458f 100644 --- a/docs/integrations/databases/oracle.md +++ b/docs/integrations/databases/oracle.md @@ -491,7 +491,7 @@ Custom filter examples: 1. For alerts applicable only to a specific cluster, your custom filter would be `db_cluster=oracle-prod.01`. 2. For alerts applicable to all clusters that start with Kafka-prod, your custom filter would be,`db_cluster=oracle-prod*`. 3. For alerts applicable to a specific cluster within a production environment, your custom filter would be: `db_cluster=oracle-1` and `environment=prod` (This assumes you have set the optional environment tag while configuring collection). -4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 5. Click **Add**. 6. Click Import and then copy-paste the above JSON to import monitors. diff --git a/docs/integrations/web-servers/apache-tomcat.md b/docs/integrations/web-servers/apache-tomcat.md index cff6103838..6d9c34539c 100644 --- a/docs/integrations/web-servers/apache-tomcat.md +++ b/docs/integrations/web-servers/apache-tomcat.md @@ -615,7 +615,7 @@ Custom filter examples: 2. For alerts applicable to all webserver farms that start with tomcat-prod, your custom filter would be: `webserver_farm=tomcat-prod*` 3. For alerts applicable to a specific webserver farm, within a production environment, your custom filter would be: `webserver_farm=dev-tomcat-01 AND environment=prod`. This assumes you have set the optional environment tag while configuring collection. -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 2. Click **Add**. 3. Click **Import**. 4. On the **Import Content popup**, enter **Apache Tomcat** in the Name field, paste in the JSON into the popup, and click **Import**. diff --git a/docs/integrations/web-servers/apache.md b/docs/integrations/web-servers/apache.md index e6b5fff260..a01ff48a26 100644 --- a/docs/integrations/web-servers/apache.md +++ b/docs/integrations/web-servers/apache.md @@ -456,7 +456,7 @@ You can install monitors by importing a JSON file or using a Terraform script. 1. Download the [JSON file](https://github.com/SumoLogic/terraform-sumologic-sumo-logic-monitor/blob/main/monitor_packages/apache/apache.json) that describes the monitors. 2. In the json file, replace `$$apache_data_source` with a custom source filter like `webserver_farm=dev-apache` for setting up alerts for a specific web server farm. If you want to configure this for all your web server farms you can find and replace `$$apache_data_source` with blank `“”`. -3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 4. Click **Add**. 5. Click **Import** and then copy paste the above JSON to import monitors. Name will be the folder name. diff --git a/docs/integrations/web-servers/haproxy.md b/docs/integrations/web-servers/haproxy.md index 53b9e7f271..0ab38113ad 100644 --- a/docs/integrations/web-servers/haproxy.md +++ b/docs/integrations/web-servers/haproxy.md @@ -447,7 +447,7 @@ However, if you would like to restrict these alerts to specific clusters or envi * For alerts applicable to all clusters that start with `haproxy-prod`: `proxy_cluster=haproxy-prod*` * For alerts applicable to a specific cluster within a production environment: `proxy_cluster=dev-haproxy01` AND `environment=prod`. This assumes you have set the optional environment tag while configuring collection. -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 2. Click **Add**. 3. Click **Import**. 4. On the **Import Content popup**, enter **HAProxy** in the Name field, paste in the JSON into the the popup, and click **Import**. diff --git a/docs/integrations/web-servers/iis-10.md b/docs/integrations/web-servers/iis-10.md index bda7e1166f..44894a223a 100644 --- a/docs/integrations/web-servers/iis-10.md +++ b/docs/integrations/web-servers/iis-10.md @@ -428,7 +428,7 @@ Alerts can be installed by either importing a JSON file or a Terraform script. T * For alerts applicable only to a specific farm, your custom filter would be: `webserver_farm=iis-standalone.01`. * For alerts applicable to all farms that start with `iis-standalone`, your custom filter would be: `webserver_system=iis-standalone*`. * For alerts applicable to a specific farm within a production environment, your custom filter would be: `webserver_farm=iis-1` AND `environment=standalone`. This assumes you have set the optional environment tag while configuring collection. -4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 5. Click **Add**.
Add Monitor 6. Click **Import** and then copy-paste the above JSON to import monitors. diff --git a/docs/integrations/web-servers/squid-proxy.md b/docs/integrations/web-servers/squid-proxy.md index 356c54062d..6cb94ce305 100644 --- a/docs/integrations/web-servers/squid-proxy.md +++ b/docs/integrations/web-servers/squid-proxy.md @@ -678,7 +678,7 @@ Custom filter examples: 1. For alerts applicable only to a specific farm, your custom filter would be ‘`proxy_cluster=squidproxy-standalone.01`‘. 2. For alerts applicable to all cluster that start with squidproxy-standalone, your custom filter would be '`proxy_cluster=squidproxy-standalone*`'. 3. For alerts applicable to a specific farm within a production environment, your custom filter would be `proxy_cluster=squidproxy-1` and `environment=standalone` (This assumes you have set the optional environment tag while configuring collection). -4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +4. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 5. Click **Add**. 6. Click Import and then copy-paste the above JSON to import monitors. diff --git a/docs/integrations/web-servers/varnish.md b/docs/integrations/web-servers/varnish.md index 890d5dd7d1..453aaa3430 100644 --- a/docs/integrations/web-servers/varnish.md +++ b/docs/integrations/web-servers/varnish.md @@ -344,7 +344,7 @@ You can install monitors by importing a JSON file or using a Terraform script. * For alerts applicable only to a specific cluster, your custom filter would be `cache_cluster=dev-varnish01` * For alerts applicable to all clusters that start with `varnish`-prod, your custom filter would be `cache_cluster=varnish-prod*` * For alerts applicable to a specific cluster within a production environment, your custom filter would be `cache_cluster=dev-varnish01` AND `environment=prod`. This assumes you have set the optional environment tag while configuring collection. -3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +3. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 4. Click **Add**. 5. Click **Import.** 6. On the **Import Content** popup, enter **Varnish** in the **Name** field, paste the JSON into the popup, and click **Import**. diff --git a/docs/manage/health-events.md b/docs/manage/health-events.md index 553286f259..6ee97e78be 100644 --- a/docs/manage/health-events.md +++ b/docs/manage/health-events.md @@ -40,7 +40,7 @@ On the health events table, you can search, filter, and sort incidents by ke To access the health events table, in the main Sumo Logic menu select **Manage Data > Monitoring > Health Events**. ![health events table.png](/img/health-events/health-events-table.png) diff --git a/docs/metrics/introduction/index.md b/docs/metrics/introduction/index.md index 31bd8a54c5..3937ea5eb7 100644 --- a/docs/metrics/introduction/index.md +++ b/docs/metrics/introduction/index.md @@ -89,7 +89,7 @@ For more information, see [About Metrics Rules](/docs/metrics/metric-rules-edito To access Metrics Explorer, click the **+ New** button at the top of the screen and select **Metrics**. In the screenshot below, the Metrics Explorer shows the results of two queries. diff --git a/docs/metrics/metrics-queries/metrics-explorer.md b/docs/metrics/metrics-queries/metrics-explorer.md index edcbab12b4..e994307624 100644 --- a/docs/metrics/metrics-queries/metrics-explorer.md +++ b/docs/metrics/metrics-queries/metrics-explorer.md @@ -46,7 +46,7 @@ If the query editor mode cannot be adjusted, it is changed to advanced mode so t ## Create a metric query -1. Click the **+ New** button at the top of the screen and select **Metrics**. +1. Click the **+ New** button at the top of the screen and select **Metrics**. 1. The Metrics Explorer opens. Click the **Metric** field. A list of metrics appears. You can scroll through the list, or begin typing to dynamically narrow the list. Click the desired metric. ![click-in-metric-area.png](/img/metrics/click-in-metrici-area.png) diff --git a/docs/observability/application-components.md b/docs/observability/application-components.md index ae8d26cbe9..a6fe5480e4 100644 --- a/docs/observability/application-components.md +++ b/docs/observability/application-components.md @@ -261,7 +261,7 @@ This section shows how to use the [monitoring dashboards](/docs/dashboards/explo ### Navigate Application Components View To open the Application Components View: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select **Application Components View** from the dropdown menu. An expandable list of your AWS environment hierarchy appears in the panel. 1. Select an environment to view a list of its components. **Application Components - Environments Overview** appears on the right. This dashboard provides insights into the CRUD activities and monitor errors of each of the components in that environment. diff --git a/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md b/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md index 483b1e4c43..e207a98dc3 100644 --- a/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md +++ b/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md @@ -28,7 +28,7 @@ The AWS Observability Solution comprises an intuitive dashboard framework that m To to [AWS Observibility tab](/docs/observability/aws) in the home page or do the following: -1. Click the **+ New** button at the top of the screen and select **Explore**. Then click the **Explore By** arrow and select **AWS Observability** from the dropdown menu. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then click the **Explore By** arrow and select **AWS Observability** from the dropdown menu. 1. In the navigation panel, make a selection for the hierarchy to view. The contents of your selection appear below. ## Navigate the AWS Observability Hierarchy diff --git a/docs/observability/aws/other-configurations-tools/add-new-aws-service.md b/docs/observability/aws/other-configurations-tools/add-new-aws-service.md index 708ad72a9f..b46c268719 100644 --- a/docs/observability/aws/other-configurations-tools/add-new-aws-service.md +++ b/docs/observability/aws/other-configurations-tools/add-new-aws-service.md @@ -182,7 +182,7 @@ Replace these variables with your own in the code samples in this section: Once you are done with the above steps, the AWS service will be added to the AWS Observability view hierarchy. To validate this: -1. Click the **+ New** button at the top of the screen and select **Explore**. Then select **AWS Observability** from the dropdown menu in the upper left. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then select **AWS Observability** from the dropdown menu in the upper left. 1. You should be able to see the new service in the hierarchy represented by namespace/entity. Validate hierarchy diff --git a/docs/observability/kubernetes/monitoring.md b/docs/observability/kubernetes/monitoring.md index a263619697..f67d8d3c61 100644 --- a/docs/observability/kubernetes/monitoring.md +++ b/docs/observability/kubernetes/monitoring.md @@ -32,7 +32,7 @@ Kubernetes views provide a visual representation of your Kubernetes stack. To navigate and analyze your Kubernetes environment, do the following: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select the Kubernetes view you want from the dropdown menu. 1. Click the arrow to the left of a content name to expand and view its contents.
![Explore_cluster_contents.png](/img/kubernetes/Explore_cluster_contents.png) 1. Dead entities are shown faded:
![faded entityexplore.png](/img/kubernetes/faded-entity-explore.png) diff --git a/docs/observability/kubernetes/troubleshoot-with-explore.md b/docs/observability/kubernetes/troubleshoot-with-explore.md index 8d248d7984..f8088c9fd5 100644 --- a/docs/observability/kubernetes/troubleshoot-with-explore.md +++ b/docs/observability/kubernetes/troubleshoot-with-explore.md @@ -46,7 +46,7 @@ In this troubleshooting scenario, we detect a problem with a cluster while nav To troubleshoot a problem with our cluster, we performed the following steps: -1. We clicked the **+ New** button at the top of the screen and selected **Explore**. +1. We clicked the **+ New** button at the top of the screen and selected **Explore**. 1. In the upper-left corner of the screen, we selected **Kubernetes Service View**, then chose the cluster we wanted to explore, and selected the Dashboards **Kubernetes - Cluster Overview** option on the upper right menu bar.
![TSS_Cluster_Overview_dialog.png](/img/kubernetes/TSS_Cluster_Overview_dialog.png)
The Dashboards view on the right displays panels that show the statuses of the clusters. 1. In our scenario, we selected the **prod-loggen** namespace in the **Pods Running** panel and discovered 2 pods that were not functioning (shown in Red).
![TSS_Cluster_Pods-Running_panel.png](/img/kubernetes/TSS_Cluster_Pods-Running_panel.png) diff --git a/docs/observability/reliability-management-slo/create-slo.md b/docs/observability/reliability-management-slo/create-slo.md index 8cf34f0998..a11fdffda1 100644 --- a/docs/observability/reliability-management-slo/create-slo.md +++ b/docs/observability/reliability-management-slo/create-slo.md @@ -30,8 +30,7 @@ The following table lists the available options for an SLO: ## Create an SLO (General) -1. In the main Sumo Logic menu select **Manage Data > Monitoring > SLOs**. +1. In the main Sumo Logic menu select **Manage Data > Monitoring > SLOs**. 2. Click **Add** > **New SLO**. Optionally, you can also: * Create folders to manage your SLOs. * Import an SLO.
To transfer data immediately and create an SLO using an import, you should first export JSON content to use that formatting. The Sumo Logic JSON format may change without notice. See [Export and Import Content in the Library](/docs/get-started/library#import-content) for complete details. @@ -137,7 +136,7 @@ As an example, say you have an existing Monitor that fires a **Critical** alert Your Monitor must be in an **active** state. ::: -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > Monitors**. 1. Click on any active Monitor to open its panel. 1. Choose one of the methods below:
Click **More Actions** > **Create SLO**.
Monitor-based SLO
Or, click Monitor-based SLO > Add Monitor-based SLO.
Monitor-based SLO
This will open the **New SLO** window. @@ -173,7 +172,13 @@ You can use the [Monitor Terraform provider (`sumologic_monitor`)](https://regis ## Managing your SLOs -Below are some best practices for managing your SLOs. To get to your SLOs list, click **Manage Data** > **Monitoring** > **SLOs** tab. +Below are some best practices for managing your SLOs. + + To access SLOs, in the main Sumo Logic menu select **Manage Data > Monitoring > SLOs**. + + ### Tags and Filters diff --git a/docs/observability/reliability-management-slo/dashboards.md b/docs/observability/reliability-management-slo/dashboards.md index 4cb5b0874e..3f761be284 100644 --- a/docs/observability/reliability-management-slo/dashboards.md +++ b/docs/observability/reliability-management-slo/dashboards.md @@ -64,7 +64,7 @@ You can also filter by compliance period to view your past activity and plan ahe #### Open in Log Search You can launch a Log Search session directly from an SLO dashboard panel, giving you the ability to drill down into further granular details. -1. In the main Sumo Logic menu, select **Manage Data > Monitoring > SLOs**. +1. In the main Sumo Logic menu, select **Manage Data > Monitoring > SLOs**. 1. Double-click on any SLO line item. 1. Hover over the panel > Click the kebab icon > **Open in Log Search**.
open-in-logsearch diff --git a/docs/observability/reliability-management-slo/index.md b/docs/observability/reliability-management-slo/index.md index 61e17f6725..28b1e9ec6f 100644 --- a/docs/observability/reliability-management-slo/index.md +++ b/docs/observability/reliability-management-slo/index.md @@ -130,7 +130,7 @@ SLO data is retained for 800 days. It is retained separately, regardless of unde To access SLOs, in the main Sumo Logic menu select **Manage Data > Monitoring > SLOs**. In the SLO screen, you can view, search, and add SLOs. Use folders to collect, package, and manage SLOs with ease, moving SLOs as needed. diff --git a/i18n/ja/alerts/alerts/monitors/alert-response.md b/i18n/ja/alerts/alerts/monitors/alert-response.md index 0f464b2e69..aa617cfd96 100644 --- a/i18n/ja/alerts/alerts/monitors/alert-response.md +++ b/i18n/ja/alerts/alerts/monitors/alert-response.md @@ -49,15 +49,10 @@ variable: Alert List shows all the Alerts from triggered Monitors within the past seven days. By default, the list is sorted by status (active on top), and then chronologically by creation time. -To open the Alert List, click the bell icon in the top menu. - -![alert list page with bell and border.png](/img/monitors/alert-list-page-bell-border.png) - - + To access the Alerts list, click the bell icon in the top menu.
alert-list-page-bell-border + * Use the search bar to filter by name, severity, or status. From 499ecf2361a551457be149eb3a05808f7c9f8f41 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:15:26 -0500 Subject: [PATCH 03/12] Update docs/apm/real-user-monitoring/dashboards.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/real-user-monitoring/dashboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/real-user-monitoring/dashboards.md b/docs/apm/real-user-monitoring/dashboards.md index 84f43ca812..e64007ec13 100644 --- a/docs/apm/real-user-monitoring/dashboards.md +++ b/docs/apm/real-user-monitoring/dashboards.md @@ -27,7 +27,7 @@ If your RUM app is removed accidentally, you'll need to install it manually: Once the RUM app has been installed, use the Real User Monitoring view to gain visibility into your web app's performance and end-user activity, such as geographic location, browser type, operating systems used. These dashboards visualize RUM metrics gathered from browser tracing instrumentation. -1. Click the **+ New** button at the top of the screen and select **Explore**. Then in the upper-left corner of the screen, select **Real User Monitoring** from the dropdown menu. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then in the upper-left corner of the screen, select **Real User Monitoring** from the dropdown menu. 1. Select your desired dashboard from **Dashboard** dropdown menu in the header:
![explore rum with red box.png](/img/rum/explore-rum-with-red-box.png)
There are three dashboard types on the **Application**, **Service**, and **Environment** levels, and a single one on the **Action type** and **Action** levels. 1. Set your desired filters. RUM data is organized on five levels: * **Application**: corresponds to the value of the application tag set in your [RUM script](/docs/apm/real-user-monitoring/configure-data-collection/#step-2-add-rum-script-to-your-page-header). This should correspond to your whole website defined by its business function, such as `the-coffee-bar-app`. From 8a12396384fce99a79507262d50d96a6f28f9dec Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:15:33 -0500 Subject: [PATCH 04/12] Update docs/apm/traces/quickstart.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/traces/quickstart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/traces/quickstart.md b/docs/apm/traces/quickstart.md index 19d0a0adbb..8144c6075c 100644 --- a/docs/apm/traces/quickstart.md +++ b/docs/apm/traces/quickstart.md @@ -20,7 +20,7 @@ You can access Traces if your Sumo Logic service package has been upgraded to in To access Traces, click the **+ New** button at the top of the screen and select **Traces**. ## Micro Lesson From 7b79e3afa5fe2f6e0981b7387d668bc39cf277c4 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:15:45 -0500 Subject: [PATCH 05/12] Update docs/apm/traces/services-list-map.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/traces/services-list-map.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/traces/services-list-map.md b/docs/apm/traces/services-list-map.md index 6386c07968..a5b9184f7c 100644 --- a/docs/apm/traces/services-list-map.md +++ b/docs/apm/traces/services-list-map.md @@ -10,7 +10,7 @@ import useBaseUrl from '@docusaurus/useBaseUrl'; To access Services, click the **+ New** button at the top of the screen and select **Services**. ## Services List view From 901c2ee2a8c14c41c6f4e19504ef5098df067be7 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:15:53 -0500 Subject: [PATCH 06/12] Update docs/apm/traces/spans.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/traces/spans.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/traces/spans.md b/docs/apm/traces/spans.md index f89fc260a3..a913abbd7c 100644 --- a/docs/apm/traces/spans.md +++ b/docs/apm/traces/spans.md @@ -10,7 +10,7 @@ The **Spans** page allows you to filter and aggregate your trace data at the raw To access Spans, click the **+ New** button at the top of the screen and select **Spans**. A new Spans page opens. Data is displayed once you run a query. From e6dc60a23ee8991adab3407de20405efbe222bc3 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:13 -0500 Subject: [PATCH 07/12] Update docs/apm/traces/tracing-dashboards.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/traces/tracing-dashboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/traces/tracing-dashboards.md b/docs/apm/traces/tracing-dashboards.md index da032f9a4b..04139b35af 100644 --- a/docs/apm/traces/tracing-dashboards.md +++ b/docs/apm/traces/tracing-dashboards.md @@ -8,7 +8,7 @@ description: Explore and create Tracing dashboards, install apps, and more. import useBaseUrl from '@docusaurus/useBaseUrl'; To access APM hierarchies: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select an **APM:** hierarchy from the dropdown menu. An expandable list of your hierarchy appears in the panel. Out-of-the-box dashboards are available as three hierarchies. From a7b577b4deef4074a13540bf85f0baf7e795cb03 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:22 -0500 Subject: [PATCH 08/12] Update docs/apm/traces/view-and-investigate-traces.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/apm/traces/view-and-investigate-traces.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/apm/traces/view-and-investigate-traces.md b/docs/apm/traces/view-and-investigate-traces.md index 37fa822f49..84733cebfe 100644 --- a/docs/apm/traces/view-and-investigate-traces.md +++ b/docs/apm/traces/view-and-investigate-traces.md @@ -12,7 +12,7 @@ You can visualize your Traces data through filtered trace lists and icicle chart To access Traces, click the **+ New** button at the top of the screen and select **Traces**. Here, you can run a Trace query, view your **Trace Duration Breakdown Chart**, and explore your **Traces matching queries** table. From 576eb88bfe5f84bcc9c713e9b3ff8358fc6328ac Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:31 -0500 Subject: [PATCH 09/12] Update docs/observability/aws/deploy-use-aws-observability/view-dashboards.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- .../aws/deploy-use-aws-observability/view-dashboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md b/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md index e207a98dc3..c75584f613 100644 --- a/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md +++ b/docs/observability/aws/deploy-use-aws-observability/view-dashboards.md @@ -28,7 +28,7 @@ The AWS Observability Solution comprises an intuitive dashboard framework that m To to [AWS Observibility tab](/docs/observability/aws) in the home page or do the following: -1. Click the **+ New** button at the top of the screen and select **Explore**. Then click the **Explore By** arrow and select **AWS Observability** from the dropdown menu. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then click the **Explore By** arrow and select **AWS Observability** from the dropdown menu. 1. In the navigation panel, make a selection for the hierarchy to view. The contents of your selection appear below. ## Navigate the AWS Observability Hierarchy From e17940fa37368d356ed5c12cf0738d5695c21fc9 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:37 -0500 Subject: [PATCH 10/12] Update docs/observability/application-components.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/observability/application-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/observability/application-components.md b/docs/observability/application-components.md index a6fe5480e4..ac50425f7f 100644 --- a/docs/observability/application-components.md +++ b/docs/observability/application-components.md @@ -261,7 +261,7 @@ This section shows how to use the [monitoring dashboards](/docs/dashboards/explo ### Navigate Application Components View To open the Application Components View: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select **Application Components View** from the dropdown menu. An expandable list of your AWS environment hierarchy appears in the panel. 1. Select an environment to view a list of its components. **Application Components - Environments Overview** appears on the right. This dashboard provides insights into the CRUD activities and monitor errors of each of the components in that environment. From a8c18541de57c673b463004bebf4754ff78b92d5 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:44 -0500 Subject: [PATCH 11/12] Update docs/observability/aws/other-configurations-tools/add-new-aws-service.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- .../aws/other-configurations-tools/add-new-aws-service.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/observability/aws/other-configurations-tools/add-new-aws-service.md b/docs/observability/aws/other-configurations-tools/add-new-aws-service.md index b46c268719..185fe3eb59 100644 --- a/docs/observability/aws/other-configurations-tools/add-new-aws-service.md +++ b/docs/observability/aws/other-configurations-tools/add-new-aws-service.md @@ -182,7 +182,7 @@ Replace these variables with your own in the code samples in this section: Once you are done with the above steps, the AWS service will be added to the AWS Observability view hierarchy. To validate this: -1. Click the **+ New** button at the top of the screen and select **Explore**. Then select **AWS Observability** from the dropdown menu in the upper left. +1. Click the **+ New** button at the top of the screen and select **Explore**. Then select **AWS Observability** from the dropdown menu in the upper left. 1. You should be able to see the new service in the hierarchy represented by namespace/entity. Validate hierarchy From 5a75799fb7f3ca65d5450a747891b6a76bb3e8a5 Mon Sep 17 00:00:00 2001 From: "John Pipkin (Sumo Logic)" Date: Fri, 21 Jun 2024 16:16:52 -0500 Subject: [PATCH 12/12] Update docs/observability/kubernetes/monitoring.md Co-authored-by: Kim (Sumo Logic) <56411016+kimsauce@users.noreply.github.com> --- docs/observability/kubernetes/monitoring.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/observability/kubernetes/monitoring.md b/docs/observability/kubernetes/monitoring.md index f67d8d3c61..6008507e44 100644 --- a/docs/observability/kubernetes/monitoring.md +++ b/docs/observability/kubernetes/monitoring.md @@ -32,7 +32,7 @@ Kubernetes views provide a visual representation of your Kubernetes stack. To navigate and analyze your Kubernetes environment, do the following: -1. Click the **+ New** button at the top of the screen and select **Explore**. +1. Click the **+ New** button at the top of the screen and select **Explore**. 1. In the upper-left corner of the screen, select the Kubernetes view you want from the dropdown menu. 1. Click the arrow to the left of a content name to expand and view its contents.
![Explore_cluster_contents.png](/img/kubernetes/Explore_cluster_contents.png) 1. Dead entities are shown faded:
![faded entityexplore.png](/img/kubernetes/faded-entity-explore.png)