diff --git a/blog-service/2021/12-31.md b/blog-service/2021/12-31.md
index 3b0f583401..ba6e64d47b 100644
--- a/blog-service/2021/12-31.md
+++ b/blog-service/2021/12-31.md
@@ -76,7 +76,7 @@ Update - The [Mimecast Source](/docs/send-data/hosted-collectors/cloud-to-cloud
---
## October 27, 2021 (Traces)
-New - Build custom Dashboards with [new panels](/docs/apm/traces/services-list-map) to view Service Maps filtered by service and application and Trace Lists filtered by a query to directly access trace views. Add panels to existing or new dashboards, setting filters and customized options.
+New - Build custom Dashboards with [new panels](/docs/apm/services-list-map) to view Service Maps filtered by service and application and Trace Lists filtered by a query to directly access trace views. Add panels to existing or new dashboards, setting filters and customized options.
---
## October 27, 2021 (Apps)
@@ -102,7 +102,7 @@ Update - We are delighted to release the additional Logs and Metrics dashboards
---
## October 14, 2021 (Traces)
-New - Operation level health metrics describe performance and availability on the level of a single SQL query or API call. They are automatically generated from tracing data real time for the most active operations, enabling you to understand application service health on one level below: what operations is this service executing towards its peers and what's the performance of each of them individually. See [Service Map and Dashboards](/docs/apm/traces/services-list-map).
+New - Operation level health metrics describe performance and availability on the level of a single SQL query or API call. They are automatically generated from tracing data real time for the most active operations, enabling you to understand application service health on one level below: what operations is this service executing towards its peers and what's the performance of each of them individually. See [Service Map and Dashboards](/docs/apm/services-list-map).
---
## October 6, 2021 (Collection)
@@ -230,7 +230,7 @@ Update - We are delighted to announce the availability of enhanced search functi
---
## August 12, 2021 (Traces)
-New - We are excited to introduce a new [Span Analytics](/docs/apm/traces/spans) experience to help you explore your trace data at the raw span level so you can understand the performance and behavior of your infrastructure.
+New - We are excited to introduce a new [Span Analytics](/docs/apm/spans) experience to help you explore your trace data at the raw span level so you can understand the performance and behavior of your infrastructure.
---
## August 12, 2021 (Collection)
@@ -596,7 +596,7 @@ Update - Explore now offers the ability to [filter your view](/docs/dashboards
---
## March 24, 2021 (Traces)
-New - We're excited to announce our [Service Map and Dashboards](/docs/apm/traces/services-list-map). A Service Map is a high-level out-of-the-box overview of your environment created from distributed tracing data. Service Maps provide you a real-time view of:
+New - We're excited to announce our [Service Map and Dashboards](/docs/apm/services-list-map). A Service Map is a high-level out-of-the-box overview of your environment created from distributed tracing data. Service Maps provide you a real-time view of:
- Your microservices and connections between them, to give you insight into their dependencies and relations.
- Health and load of each microservice reflected in size and color, so you can immediately ascertain potential problems and bottlenecks in your application infrastructure.
diff --git a/blog-service/2022/12-31.md b/blog-service/2022/12-31.md
index 0a1dac5b06..a0feefe93b 100644
--- a/blog-service/2022/12-31.md
+++ b/blog-service/2022/12-31.md
@@ -558,7 +558,7 @@ Update - The [Tenable Source](/docs/send-data/hosted-collectors/cloud-to-cloud-i
---
## April 26, 2022 (Traces)
-New - You can now add the results of Spans queries directly to Dashboards from the [Spans analytics](/docs/apm/traces/spans#add-to-dashboard) window. You'll use the same easy query builder to [modify your panels](/docs/dashboards/panels/modify-chart) later. You can still use [Log Search](/docs/apm/traces/search-query-language-support-for-traces) to add span results to Dashboards by running queries in the `_trace_spans` index. The same limitations of Log Search still apply, your query scan volume should not exceed 200x of your tracing ingest.
+New - You can now add the results of Spans queries directly to Dashboards from the [Spans analytics](/docs/apm/spans#add-to-dashboard) window. You'll use the same easy query builder to [modify your panels](/docs/dashboards/panels/modify-chart) later. You can still use [Log Search](/docs/apm/traces/search-query-language-support-for-traces) to add span results to Dashboards by running queries in the `_trace_spans` index. The same limitations of Log Search still apply, your query scan volume should not exceed 200x of your tracing ingest.
---
## April 17, 2022 (Apps)
@@ -678,7 +678,7 @@ Update - We’ve made an improvement to the [Sumo Logic Organizations](/docs/man
---
## February 10, 2022 (Traces)
-New - Number of [spans](/docs/apm/traces/spans) per Trace has been increased by 10 times to 10000 spans per trace to better support monitoring for long running and complex transactions. Please note that new spans can increase credits consumption.
+New - Number of [spans](/docs/apm/spans) per Trace has been increased by 10 times to 10000 spans per trace to better support monitoring for long running and complex transactions. Please note that new spans can increase credits consumption.
Update - Traces logs and data includes a new `duration` field that holds the difference between `endTimestamp` and `startTimestamp` in nanoseconds.
diff --git a/blog-service/2023/12-31.md b/blog-service/2023/12-31.md
index 87e5bdb379..7f150fec76 100644
--- a/blog-service/2023/12-31.md
+++ b/blog-service/2023/12-31.md
@@ -1012,7 +1012,7 @@ We're excited to introduce an improved approach to calculating and aggregating p
What's New?
* All APM metrics on dashboards now use the recently released [Metrics Histograms](/docs/metrics/introduction/metric-histograms/).
-* The Service List panel replaces the existing timeseries table in the Application Details panel and is now included in out-of-the-box dashboards for APM views. This change leverages the new and useful visualization for [Services List](/docs/apm/traces/services-list-map/#services-list-view) released earlier.
+* The Service List panel replaces the existing timeseries table in the Application Details panel and is now included in out-of-the-box dashboards for APM views. This change leverages the new and useful visualization for [Services List](/docs/apm/services-list-map/#services-list-view) released earlier.
* The top bar selector for latency type has been renamed to `latency_type`, which now automatically drives all latency percentile metrics in all panels that support pct metrics.
[Learn more](/docs/apm/traces/tracing-dashboards/).
@@ -1359,7 +1359,7 @@ Update - We have updated the **Reuse Password After** password policy. Previousl
#### Tracing Services List
-New - Our new tracing **Services List** view provides a high-level summary of your service health insights and important KPIs in one compact table, allowing you to spot potential issues in your application infrastructure. [Learn more](/docs/apm/traces/services-list-map).
+New - Our new tracing **Services List** view provides a high-level summary of your service health insights and important KPIs in one compact table, allowing you to spot potential issues in your application infrastructure. [Learn more](/docs/apm/services-list-map).
---
### January 17, 2023 (Metrics)
diff --git a/cid-redirects.json b/cid-redirects.json
index 6b55b72d0f..efbc991786 100644
--- a/cid-redirects.json
+++ b/cid-redirects.json
@@ -1494,7 +1494,7 @@
"/Traces/01Getting_Started_with_Transaction_Tracing/01Instrument_your_application_with_OpenTelemetry/Ruby_on_Rails_OpenTelemetry_auto-instrumentation": "/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby-on-rails",
"/Traces/01Getting_Started_with_Transaction_Tracing/01Instrument_your_application_with_OpenTelemetry/Ruby_OpenTelemetry_auto-instrumentation": "/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby",
"/Traces/02Working_with_Tracing_data": "/docs/apm/traces",
- "/Traces/02Working_with_Tracing_data/01Service_Map": "/docs/apm/traces/services-list-map",
+ "/Traces/02Working_with_Tracing_data/01Service_Map": "/docs/apm/services-list-map",
"/Traces/03Advanced_Configuration": "/docs/apm/traces/advanced-configuration",
"/Traces/03Advanced_Configuration/Correlate_Logs": "/docs/apm/traces/advanced-configuration/correlate-logs",
"/Traces/03Advanced_Configuration/Filter-Shape-Trace-Data": "/docs/apm/traces/advanced-configuration/filter-shape-tracing-data",
@@ -2566,11 +2566,11 @@
"/cid/7339": "/docs/alerts/webhook-connections/cloud-soar",
"/cid/741862": "/docs/manage/content-sharing/admin-mode",
"/cid/750": "/docs/apm/traces/tracing-dashboards",
- "/cid/751": "/docs/apm/traces/services-list-map",
+ "/cid/751": "/docs/apm/services-list-map",
"/cid/752": "/docs/apm/traces",
"/cid/754": "/docs/apm/real-user-monitoring",
"/cid/755": "/docs/apm/real-user-monitoring",
- "/cid/756": "/docs/apm/traces/spans",
+ "/cid/756": "/docs/apm/spans",
"/cid/757": "/docs/apm/traces/search-query-language-support-for-traces",
"/cid/758": "/docs/apm/traces/get-started-transaction-tracing/http-traces-source",
"/cid/759": "/docs/apm/traces/view-and-investigate-traces",
@@ -3525,10 +3525,10 @@
"/Traces/01Getting_Started_with_Transaction_Tracing": "/docs/apm/traces/get-started-transaction-tracing",
"/Traces/02Working_with_Tracing_data/02Tracing_Dashboards": "/docs/apm/traces/tracing-dashboards",
"/Traces/02Working_with_Tracing_data/03View_and_investigate_traces": "/docs/apm/traces/view-and-investigate-traces",
- "/Traces/02Working_with_Tracing_data/04Spans": "/docs/apm/traces/spans",
+ "/Traces/02Working_with_Tracing_data/04Spans": "/docs/apm/spans",
"/Traces/02Working_with_Tracing_data/05Search_Query_Language_support_for_Traces": "/docs/apm/traces/search-query-language-support-for-traces",
"/Traces/Real_User_Monitoring": "/docs/apm/real-user-monitoring",
- "/Traces/Service_Map_and_Dashboards": "/docs/apm/traces/services-list-map",
+ "/Traces/Service_Map_and_Dashboards": "/docs/apm/services-list-map",
"/Traces/View_and_investigate_traces": "/docs/apm/traces/view-and-investigate-traces",
"/Visualizations-and-Alerts": "/docs/alerts",
"/Visualizations-and-Alerts/Alerts": "/docs/alerts",
@@ -4038,7 +4038,7 @@
"/Start-Here/01About-Sumo-Logic/Sumo-Logic-Support-Terms-and-Conditions": "/docs/get-started/help",
"/Start-Here/01About-Sumo-Logic/System-Requirements/Supported-Browsers": "/docs/get-started/system-requirements",
"/Start-Here/01About-Sumo-Logic/System-Requirements/Installed-Collector-Requirements": "/docs/get-started/system-requirements",
- "/Traces/02Working_with_Tracing_data/Spans": "/docs/apm/traces/spans",
+ "/Traces/02Working_with_Tracing_data/Spans": "/docs/apm/spans",
"/Traces/02Working_with_Tracing_data/Search_Query_Language_support_for_Traces": "/docs/apm/traces/search-query-language-support-for-traces",
"/Traces/Getting_Started_with_Transaction_Tracing": "/docs/apm/traces/get-started-transaction-tracing",
"/Traces/Getting_Started_with_Transaction_Tracing/Set_up_traces_collection_for_other_environments": "/docs/apm/traces/get-started-transaction-tracing/set-up-traces-collection-for-other-environments",
@@ -4051,15 +4051,15 @@
"/Traces/01Getting_Started_with_Transaction_Tracing/Instrument_your_application_with_OpenTelemetry/JavaScript_OpenTelemetry_auto-instrumentation": "/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/javascript",
"/Traces/01Getting_Started_with_Transaction_Tracing/Instrument_your_application_with_OpenTelemetry": "/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation",
"/Traces/Search_Query_Language_support_for_Traces": "/docs/apm/traces/search-query-language-support-for-traces",
- "/Traces/Spans": "/docs/apm/traces/spans",
+ "/Traces/Spans": "/docs/apm/spans",
"/docs": "/",
"/docs/api/dashboard-new": "/docs/api/dashboard",
"/docs/apm/traces/host-list": "/docs/observability/host-list-beta",
"/docs/apm/traces/working-with-tracing-data": "/docs/apm/traces",
- "/docs/apm/traces/working-with-tracing-data/services-list-map": "/docs/apm/traces/services-list-map",
+ "/docs/apm/traces/working-with-tracing-data/services-list-map": "/docs/apm/services-list-map",
"/docs/apm/traces/working-with-tracing-data/tracing-dashboards": "/docs/apm/traces/tracing-dashboards",
"/docs/apm/traces/working-with-tracing-data/view-and-investigate-traces": "/docs/apm/traces/view-and-investigate-traces",
- "/docs/apm/traces/working-with-tracing-data/spans": "/docs/apm/traces/spans",
+ "/docs/apm/traces/working-with-tracing-data/spans": "/docs/apm/spans",
"/docs/apm/traces/working-with-tracing-data/search-query-language-support-for-traces": "/docs/apm/traces/search-query-language-support-for-traces",
"/Visualizations-and-Alerts/Alert-Grouping": "/docs/alerts/monitors/alert-grouping",
"/Visualizations-and-Alerts/Alerts/09-Scheduled-Search-FAQs/How-to-Prevent-your-Scheduled-Search-from-Timing-Out": "/docs/alerts/scheduled-searches/faq",
@@ -4158,6 +4158,10 @@
"/cid/-1": "/",
"/docs/api/beta": "/docs/api",
"/docs/api/dashboard-data": "/docs/api/dashboard",
+ "/docs/apm/traces/spans": "/docs/apm/spans",
+ "/docs/apm/traces/services-list-map": "/docs/apm/services-list-map",
+ "/docs/cloud-security-analytics": "/docs/security/cloud-infrastructure-security",
+ "/docs/cloud-security-analytics/introduction-to-cloud-security-analytics": "/docs/security/cloud-infrastructure-security/introduction",
"/docs/cloud-security-analytics": "/docs/security/additional-security-features/cloud-infrastructure-security",
"/docs/cloud-security-analytics/introduction-to-cloud-security-analytics": "/docs/security/additional-security-features/cloud-infrastructure-security/introduction",
"/docs/cloud-security-analytics/data-lake": "/docs/security/additional-security-features/data-lake",
diff --git a/docs/api/service-map.md b/docs/api/service-map.md
index 1a74d5f7e4..420c6eba8b 100644
--- a/docs/api/service-map.md
+++ b/docs/api/service-map.md
@@ -12,7 +12,7 @@ import ApiRoles from '../reuse/api-roles.md';
-The Service Map API allows you to fetch a graph representation of the Service Map, which is a high-level view of your application environment, automatically derived from tracing data. For more information, see [Service Map](/docs/apm/traces/services-list-map).
+The Service Map API allows you to fetch a graph representation of the Service Map, which is a high-level view of your application environment, automatically derived from tracing data. For more information, see [Service Map](/docs/apm/services-list-map).
:::tip Other Tracing APIs
See also: [Span Analytics APIs](/docs/api/span-analytics) and [Traces APIs](/docs/api/tracing).
diff --git a/docs/api/span-analytics.md b/docs/api/span-analytics.md
index 390bc783ad..4bb7359886 100644
--- a/docs/api/span-analytics.md
+++ b/docs/api/span-analytics.md
@@ -11,7 +11,7 @@ import ApiRoles from '../reuse/api-roles.md';
-The Span Analytics API allows you to browse spans collected in the system. You can execute queries to find individual spans matching provided search criteria as well as run aggregated span queries and retrieve their results. For more information, see [Spans](/docs/apm/traces/spans).
+The Span Analytics API allows you to browse spans collected in the system. You can execute queries to find individual spans matching provided search criteria as well as run aggregated span queries and retrieve their results. For more information, see [Spans](/docs/apm/spans).
:::tip Other Tracing APIs
See also: [Service Map APIs](/docs/api/service-map) and [Traces APIs](/docs/api/tracing).
@@ -60,4 +60,4 @@ While the span analytics query is running you need to request the query status b
## Errors
-
1. Enter **Advanced options for Browser RUM**.
- * **Application Name**. (Recommended) Add an **Application Name** tag of a text string to show for the app name in spans (for example, `bookings-app`). This groups services in the Application Service View. If left blank, services will belong to a "default" application. See [Application Service Dashboards](/docs/apm/traces/services-list-map.md) for more information. This setting is saved in the script for `name_of_your_web_application`.
+ * **Application Name**. (Recommended) Add an **Application Name** tag of a text string to show for the app name in spans (for example, `bookings-app`). This groups services in the Application Service View. If left blank, services will belong to a "default" application. See [Application Service Dashboards](/docs/apm/services-list-map.md) for more information. This setting is saved in the script for `name_of_your_web_application`.
* **Service Name**. (Required) Add a **Service Name** of a text string to show for the service name in spans (for example, `bookings-web-app`). This setting is saved in the script for `name_of_your_web_service`. To set up a service name dynamically (e.g., to have different service names for micro-frontend packages), leverage the `getOverriddenServiceName` function inside your page code to overwrite the default service name (requires RUM script v4.2.0 or higher). Service names should be of low cardinality and should describe parts of your website above page level. Here's an example code leveraging that function:
```javascript
window.sumoLogicOpenTelemetryRum.initialize({
diff --git a/docs/apm/traces/services-list-map.md b/docs/apm/services-list-map.md
similarity index 57%
rename from docs/apm/traces/services-list-map.md
rename to docs/apm/services-list-map.md
index 418730fd93..b7c2650e6d 100644
--- a/docs/apm/traces/services-list-map.md
+++ b/docs/apm/services-list-map.md
@@ -6,59 +6,17 @@ description: View your application topology and investigate microservice interac
import useBaseUrl from '@docusaurus/useBaseUrl';
-
+
-[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access Services, go to the **Home** screen and select **Services**.
+To access the services list and services map features:
+* [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to the **Home** screen and select **Traces** > **Services**.
+* [**New UI**](/docs/get-started/sumo-logic-ui/). In the main Sumo Logic menu, select **Observability**, and then under **Application Monitoring**, select **Services**. You can also click the **Go To...** menu at the top of the screen and select **Services**.
-[**New UI**](/docs/get-started/sumo-logic-ui/). To access Services, in the main Sumo Logic menu, select **Observability**, and then under **Application Monitoring**, select **Services**. You can also click the **Go To...** menu at the top of the screen and select **Services**.
-
-
-## Services List view
-
-The **Services List** view provides a compact, high-level overview of your application service health insights, alerts, and KPIs. You can filter and sort your KPI data using the filters and column headers.
-
-
-
-KPIs listed in the table reflect the previous 15 minutes of data. Clicking on any service will open the Entities panel allowing for further drill-down.
-
-### Alerts
-
-**Alerts** in the Service List are displayed based on the configured [Monitors](/docs/alerts/monitors/overview/) in the Sumo Logic platform for a given service.
-
-The **Alert status** column displays the most severe alert status along with the total number of alerts associated with a given service.
-
-To view alert details, click on a row and view it in the right-hand-side panel.
-
-In addition, you can narrow down the list of visible services by the type of active alerts for a given service. Service List can filter based on the following alert statuses:
-
-- Critical
-- Warning
-- Missing Data
-- Normal
-
-A service is displayed in the list if at least one of the alerts is in the selected state.
-
-### General Settings
-
-Configure anomaly detection in **General Settings** ([learn more](#anomaly-detection)).
-
-
-
-:::note
-Your Services List and Map settings are specific to you (not your team) and will be preserved in your browser's local storage.
-:::
-
-### Display Settings
-
-Display and hide columns using **Display Settings**.
-
-
-
-## Services Map view
+## Services map view
The **Services Map** view visually maps out your application environment, giving you a greater understanding of your application architecture, hierarchy, and dependencies between monitored microservices. Health and load of each microservice is reflected in size and color to help you spot potential problems and bottlenecks in your application infrastructure.
-Services Maps are built automatically from distributed tracing data in real time as it arrives in Sumo Logic. You can:
+Services maps are built automatically from distributed tracing data in real time as it arrives in Sumo Logic. You can:
* Zoom in on the map to see a more granular level of detail, or zoom out to get a higher-level overview
* Hover over a service to see its connections to other services and the last 15 minutes of activity in terms of latency, requests, and errors
@@ -67,17 +25,15 @@ Services Maps are built automatically from distributed tracing data in real time
* Filter by environment (up to 10 values), if your tracing data has the deployment environment tag (`deployment.environment=[environment]`)
* Search for a service by name
-
+
-### General Settings
+### Settings
-Configure anomaly detection in **General Settings** ([learn more](#anomaly-detection)).
-
-
+Use the **General Settings** to configure [anomaly detection](#anomaly-detection).
### Map legend
-
+
* **Color** of services:
* Red represents anomalies.
@@ -92,7 +48,37 @@ Configure anomaly detection in **General Settings** ([learn more](#anomaly-detec
* Circle and arrows with dotted lines represent services or connections that have been inactive an hour or more.
* **Size** of services: Size is based on service activity, where large circles are more active compared to smaller circles that are less active.
-## Anomaly Detection
+## Services list view
+
+The **Services List** view provides a compact, high-level overview of your application service health insights, alerts, and KPIs. You can filter and sort your KPI data using the filters and column headers.
+
+
+
+KPIs listed in the table reflect the previous 15 minutes of data. Clicking on any service will open the Entities panel allowing for further drill-down.
+
+### Alerts
+
+Alerts in the Service List are displayed based on the configured [monitors](/docs/alerts/monitors/overview/) in the Sumo Logic platform for a given service.
+
+The **Alert Status** column displays the most severe alert status along with the total number of alerts associated with a given service.
+
+To view an alert's details, click on a row and view it in the right-hand-side panel.
+
+Additionally, you can narrow down the list of visible services by the type of active alerts for a given service. Service List can filter based on the following alert statuses:
+
+- Critical
+- Warning
+- Missing Data
+- Normal
+
+A service is displayed in the list if at least one of the alerts is in the selected state.
+
+### Settings
+
+* Use the general settings to configure [anomaly detection](#anomaly-detection).
+* Use the columns display settings to display and hide columns.
+
+## Anomaly detection
An anomaly is a spike in latency and errors or a dip in requests. Here's how to configure your own threshold settings for anomaly detection.
@@ -100,38 +86,39 @@ An anomaly is a spike in latency and errors or a dip in requests. Here's how to
**Automatic anomaly detection** is enabled by default, with the **Worst Case** option selected. This will render services to be displayed as a red circle if at least one of the KPIs (latency, errors, requests) has had an anomaly in the last 15 minutes AND the anomaly was not present 7 days ago at the same time. Optionally, you can explicitly choose one of the other KPIs - **Latency**, **Error**, or **Request**.
-
+
The standard [metric outlier operator](/docs/metrics/metrics-operators/outlier/) is used to detect this. You can adjust the sensitivity and **Learning window** of the outlier detection in the settings to make the logic more or less dependent on occasional spikes.
### Manual
+
Manual anomaly detection allows you to specify different detection settings for each KPI. Click the toggle switch to manually enable or disable each KPI highlight as desired.
-
+
### Alerts
If the **Alerts** option is enabled, the status of a service will be influenced by the presence of active alerts (or those, which have been resolved within the selected time range) associated with the service.
-
+
-## Services Dashboard Panels
+## Add services panel to dashboard
-The **Services Map** and **Services List** panels, available out of the box, enable you to explore your application environment and review all traces from your Dashboard. You can duplicate or add multiple panels with different filtering or queries to refine views and support your organization.
+The **Services Map** and **Services List** panels, available out of the box, enable you to explore your application environment and review all traces from a dashboard. You can duplicate or add multiple panels with different filtering or queries to refine views and support your organization.
-To add a Services panel to your Dashboard:
+To add a services panel to a dashboard:
-1. Open an existing Dashboard or create a new Dashboard.
[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to the **Home** screen and select **Dashboard**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Dashboards > New Dashboard**. You can also click the **Go To...** menu at the top of the screen and select **New Dashboard**.
-1. On an existing Dashboard, click **Add Panel** > **Services**, or, on a new Dashboard, click **Services**.
-1. When the panel configuration page opens, go to the **Visual Settings** > **Chart Type**, dropdown and select **Table** (Services List) or **Graph** (Services Map).
-1. (Optional) Select from the dropdown menus to filter by the following:
+1. Open an existing dashboard or [create a new one](/docs/dashboards/create-dashboard-new).
+1. On an existing dashboard, click **Add Panel** > **Services**, or, if you're creating a new dashboard, click **Services**.
+1. When the panel configuration page opens, go to the **Visual Settings** > **Chart Type**, dropdown and select **Table** (Services List) or **Graph** (Services Map).
+1. (Optional) Select from the dropdown menus to filter by the following:
* **Application**. Your application name. You can use this if your tracing data has the tag called `application=[app-name]` To pass the variables from dashboard filters, set `application={{application}}`
* **Environment**. Your production, staging, or development environment name. You can use this if your tracing data has the tag called `deployment.environment=[environment-name]`. To pass the variables from dashboard filters, set `deployment.environment={{deployment.environment}}`
* **Service(s)**. Your application name, which should be always there. To pass the variables from dashboard filters, set `service={{service}}`.
1. Go to the **General** tab to configure your panel details (name, **Title Font Size**, and **Description**).
1. For **Table** chart type only: Go to **Display Settings** and set the column data and services you'd like to see displayed.
-1. Click **Add to Dashboard**. The panel loads in your Dashboard to review your applications and services according to filtering.
+1. Click **Add to Dashboard**. The panel loads in your dashboard to review your applications and services according to filtering.
:::tip
-See the [Dashboard guide](/docs/dashboards) for additional information and options to create panels, configure filters, create and filter with template variables from dashboard headers, and more.
+See [Dashboards](/docs/dashboards) for additional information on creating panels, configuring filters, filtering with template variables from dashboard headers, and more.
:::
diff --git a/docs/apm/traces/spans.md b/docs/apm/spans.md
similarity index 50%
rename from docs/apm/traces/spans.md
rename to docs/apm/spans.md
index 2c15ab7907..d972b5a0ea 100644
--- a/docs/apm/traces/spans.md
+++ b/docs/apm/spans.md
@@ -4,22 +4,27 @@ title: Span Analytics and Queries
description: Learn how to use the Spans page to explore your span data.
---
-The **Spans** page allows you to filter and aggregate your trace data at the raw span level so you can understand the performance and behavior of your application services.
+import useBaseUrl from '@docusaurus/useBaseUrl';
-## Spans page
+Sumo Logic Span Analytics enables you to filter and aggregate trace data at the raw span level, providing insights into the performance and behavior of your application services.
-[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access Spans, go to the **Home** screen and select **Spans**.
+With its intuitive interface, Span Analytics allows you to:
+* Filter and inspect tracing data in detail.
+* Explore span metadata through a structured facets list.
+* Aggregate by any custom dimension or tag to generate charts and tables.
-[**New UI**](/docs/get-started/sumo-logic-ui/). To access Spans, in the main Sumo Logic menu, select **Observability**, and then under **Application Monitoring**, select **Span Analytics**. You can also click the **Go To...** menu at the top of the screen and select **Span Analytics**.
-
+To access span analytics:
-A new Spans page opens. Data is displayed once you run a query.
+* [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to the **Home** screen and click **Traces**. In the new page, click the **Traces** dropdown menu and select **Span Analytics**.
+* [**New UI**](/docs/get-started/sumo-logic-ui/). In the main Sumo Logic menu, select **Observability**, and then under **Application Monitoring**, select **Span Analytics**. You can also click the **Go To...** menu at the top of the screen and select **Span Analytics**.
-
+A new **Spans** page opens. Data is displayed once you run a query.
+
+
From here, you can filter and aggregate by any standard or custom span attribute (tag) and create charts to visualize results. If you find something interesting, you can quickly explore your raw span records in the **Messages** tab.
-For more advanced use cases, you can further enhance your query by clicking the [Open in Search](#open-in-search) button, which opens a new Log Search of your spans based on your query. Here, you can use [Search Query Language](search-query-language-support-for-traces.md) to investigate further.
+For more advanced use cases, you can further enhance your query by clicking the [Open in Search](#open-in-search) button, which opens a new Log Search of your spans based on your query. Here, you can use [Search Query Language](/docs/apm/traces/search-query-language-support-for-traces) to investigate further.
:::note
Tracing must be enabled in your account to use this functionality. Contact your account team if the only thing you see is an infographic.
@@ -29,7 +34,7 @@ import Iframe from 'react-iframe';
:::sumo Micro Lesson
-This micro lesson provides an overview of Span Analytics, and describes the term Span in the distributed tracing and the benefits of Span Analytics. It also explains how to perform Span Analytics in Sumo Logic UI.
+This micro lesson provides an overview of Span Analytics, and describes the term *span* in the distributed tracing and the benefits of Span Analytics. It also explains how to perform Span Analytics in Sumo Logic UI.
### Run query
Once you have defined your spans query, with filters and aggregation if desired, click the search button to run the search. It looks like the following:
-
+
You can pause or stop your search by clicking the appropriate icons below the search button.
-
+
-## Search Results
+## Search results
**Messages** (including **Facets**) are always provided to show you the raw output of your query. You will have **Aggregates** if your query has set the **Visualize** option.
@@ -127,10 +134,10 @@ You can pause or stop your search by clicking the appropriate icons below the se
The **Messages** table shows your raw span data. You can click on any row to open a right-side Details pane (similar to the one in [Trace View](/docs/apm/traces/view-and-investigate-traces)) showing span details and options to navigate to other parts of the system from there.
-
+
* To move a column left or right, hold click and drag it to a different location in the table.
-* To adjust column width, click and drag the vertical line in between the columns.

+* To adjust column width, click and drag the vertical line in between the columns.

* To reset column width to the default size, double-click the vertical line to the right of a column name.
#### Facets
@@ -139,37 +146,36 @@ The **Facets** panel provides a list of all the metadata fields returned from yo
The content of the Facets panel is affected by your current active filters and time range, but shows any found metadata tag (span attribute) with its top 10 values, including any custom tags you may [add to your data](/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/java/custom-tags-configuration). By default, the fields used in the query are shown in the Messages table.
-
+
* You can adjust which fields are displayed in the raw span messages table by checking or unchecking the box next to the field in the Facets panel.
* Use the search field to easily find the metadata from your data. This applies the filter to both tag names and their values.
* The number of values found for each is displayed for your reference.
* Add and remove fields from your query by hovering over a field and clicking.
-
+
### Aggregates tab
-The Aggregates tab shows your data charted. See Panels from Dashboard for details on the settings. However, note that not all settings will be available on the Spans page. The interface will only show you available settings.
+The **Aggregates** tab shows your data charted. See Panels from Dashboard for details on the settings. However, note that not all settings will be available on the Spans page. The interface will only show you available settings.
-
+
-## Add to Dashboard
+#### Add to Dashboard
-You can add to Dashboard as long as your total dashboard-originated `_trace_spans `read volume does not exceed 200x of your tracing ingest. Contact your Sumo Logic representative for paid subscription service options for volume requirements exceeding 200x of your tracing ingest.
+You can add to a dashboard as long as your total dashboard-originated `_trace_spans` read volume does not exceed 200x of your tracing ingest. Contact your Sumo Logic representative for paid subscription service options for volume requirements exceeding 200x of your tracing ingest.
-To add your aggregated span data to a Dashboard:
+To add your aggregated span data to a dashboard:
-1. Click the three vertical-dots icon on the top right of the Spans page and select **Add to Dashboard**.

-1. In the **Add Panel to Dashboard** window provide a **Panel Title** and a name for the **Dashboard**. Once the name is entered you'll have an option to select **Create New Dashboard** with your name.

-1. Click **Add** when you're done assigning which Dashboard to add the Panel to.
+1. Click the three-dot kebab menu icon and select **Add to Dashboard**.

+1. In the **Add Panel to Dashboard** window, provide a **Panel Title** and enter an existing **Dashboard** name or add to a newly created a new one, as seen in this screenshot.

+1. When you're done assigning the panel to a dashboard, click **Add**.
-## Open in Search
+#### Open in Search
-To further enhance your query, you can use the [Search Query Language](search-query-language-support-for-traces.md) for more advanced use cases by opening a Search of your spans. Click the
-three vertical-dots icon on the top right of the Spans page and select **Open in Search**.
+To further enhance your query, you can use the [Search Query Language](/docs/apm/traces/search-query-language-support-for-traces) for more advanced use cases by opening a Search of your spans. Click the three-dot kebab menu icon and select **Open in Search**.
-
+
### Examples
@@ -177,9 +183,9 @@ three vertical-dots icon on the top right of the Spans page and select **Open
To compare the performance of different release versions defined by a custom tag `assemblyVersion`, you can graph the 95th percentile of latency of a microservice in the function of time by version.
-Use the **filters** or **facets** features to find the appropriate service in the dropdown and select it. Then, select to visualize duration’s 95th percentile and pick a group by time, for example, 1-minute granularity and the `assemblyVersion` custom tag that carries version information. That’s it!
+Use the **filters** or **facets** features to find the appropriate service in the dropdown and select it. Next, select to visualize duration’s 95th percentile and pick a group by time. For example, 1-minute granularity and the `assemblyVersion` custom tag that carries version information. That’s it!
-
+
You can customize your chart by picking different visualization types and colors.
@@ -189,15 +195,15 @@ Next, let’s see how to find the distribution of different HTTP errors among ou
Here is the simple query we used to visualize that data:
-
+
It’s now easier than ever to drill down into the information you care about. Note that our query only includes spans with codes from 4xx and 5xx ranges and visualizes the count of such spans, broken down by two dimensions, service and status code. Easy!
The number of cases you can realize with this is unlimited. In addition to the above examples, you can aggregate and visualize the content of custom metrics in your spans, and filter and break them down by any field, including custom tags. These can all be presented in any of the available chart visualizations.
-If any further query customization is required, you can click the [**Open in Search**](#open-in-search) button to edit your query, making it a great place to start queries in a way that still allows further technical refinement. Especially if you try to solve a use case that requires more than the current functionality of the Spans page, such as the following:
+To further customize your query, click [Open in Search](#open-in-search) to edit. Spans makes it a great place to start queries in a way that still allows further technical refinement. Especially if you try to solve a use case that requires more than the current functionality of the Spans page, such as the following:
1. A stacked time-series chart with more than two non-time dimensions. You can only set **Group By** to **Time** and a single dimension.
1. Visualize multiple series with more than one count operation.
-1. Use OR operations in filters. Filters are concatenated using AND logic.
+1. Use `OR` operations in filters. Filters are concatenated using `AND` logic.
1. Use mathematical operations between metrics.
diff --git a/docs/apm/traces/advanced-configuration/working-with-span-attributes.md b/docs/apm/traces/advanced-configuration/working-with-span-attributes.md
index 20339d023d..5b46024531 100644
--- a/docs/apm/traces/advanced-configuration/working-with-span-attributes.md
+++ b/docs/apm/traces/advanced-configuration/working-with-span-attributes.md
@@ -19,7 +19,7 @@ You can collect logs with traces attached to them by [inserting `spanid` and `t
and they are displayed in the **Span logs** tab in [Details Pane](/docs/apm/traces/view-and-investigate-traces) after clicking on the span.
-
+
## Working with attributes on OpenTelemetry collector
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/java.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/java.md
index 5c10b3963d..89eb72f919 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/java.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/java.md
@@ -42,7 +42,7 @@ You can instrument your AWS Java Lambda function using the [Sumo Logic Distribut
* `/opt/otel-proxy-handler`. If implementing RequestHandler but proxied through API Gateway.
* `/opt/otel-stream-handler`. If implementing RequestStreamHandler.
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME`. Ensure you define it as a string value that represents the function name and its business logic such as "Check SQS Lambda". This will appear as the tracing service name in Sumo Logic.
- * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME`. The string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID`. Set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data. All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair) such as: `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
* `SUMO_OTLP_HTTP_ENDPOINT_URL` has to be set to send all gathered telemetry data to Sumo Logic. The URL comes from an [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp). You can use an existing Source or create a new one, if needed.
@@ -168,7 +168,7 @@ Instrumentation of container-based AWS Lambda function requires some changes in
* `/opt/otel-stream-handler`. If implementing `RequestStreamHandler`
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME`. Ensure you define it as a string value that represents the function name and its business logic such as "Check SQS Lambda". This will appear as the tracing service name in Sumo Logic.
* `OTEL_TRACES_SAMPLER = always_on`. Enables traces sampling.
- * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME`. The string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID`. Set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data. All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair) such as: `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
* `SUMO_OTLP_HTTP_ENDPOINT_URL` has to be set to send all gathered telemetry data to Sumo Logic. The URL comes from an [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp). You can use an existing Source or create a new one, if needed.
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/nodejs.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/nodejs.md
index 8e594851ea..d51de9a21e 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/nodejs.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/nodejs.md
@@ -40,7 +40,7 @@ It is very simple to instrument your AWS NodeJS Lambda function using the Sumo L
* `AWS_LAMBDA_EXEC_WRAPPER = /opt/otel-handler`. Enables auto-instrumentation.
* `OTEL_TRACES_SAMPLER = always_on`. Enables traces sampling.
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME`. Ensure you define it as a string value that represents the function name and its business logic such as "Check SQS Lambda". This will appear as the tracing service name in Sumo Logic.
- * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME`. the string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID`. set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data. All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair) such as: `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
* `SUMO_OTLP_HTTP_ENDPOINT_URL` has to be set to send all gathered telemetry data to Sumo Logic. The URL comes from an [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp). You can use an existing Source or create a new one, if needed.
@@ -146,7 +146,7 @@ Instrumentation of container-based AWS Lambda function requires some changes in
* `AWS_LAMBDA_EXEC_WRAPPER = /opt/otel-handler`. Enables auto-instrumentation.
* `OTEL_TRACES_SAMPLER = always_on`. Enables traces sampling.
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME`. Sets the tracing service name in Sumo Logic. Make sure to define it as a string value that represents the function name and its business logic, such as "Check SQS Lambda".
- * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES`. Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME`. The string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID`. Set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data. All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair) such as: `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
* `SUMO_OTLP_HTTP_ENDPOINT_URL` has to be set to send all gathered telemetry data to Sumo Logic. The URL comes from an [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp). You can use an existing Source or create a new one, if needed.
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/python.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/python.md
index 4c50e4a92e..0b4b317eaa 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/python.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/aws-lambda/python.md
@@ -40,7 +40,7 @@ It is very simple to instrument your AWS Python Lambda function using the Sumo L
* `AWS_LAMBDA_EXEC_WRAPPER= /opt/otel-instrument` - Enables auto-instrumentation.
* `OTEL_TRACES_SAMPLER = always_on` - Enables traces sampling.
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME` - Sets the tracing service name in Sumo Logic. Make sure to define it as a string value that represents the function name and its business logic such as "Check SQS Lambda".
- * `OTEL_RESOURCE_ATTRIBUTES` - Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES` - Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME` - The string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID` - Set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data.
All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair) such as: `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
@@ -152,7 +152,7 @@ Instrumentation of container based AWS Lambda function requires some changes in
* `AWS_LAMBDA_EXEC_WRAPPER = /opt/otel-instrument` - Enables auto-instrumentation.
* `OTEL_TRACES_SAMPLER = always_on` - enables traces sampling.
* `OTEL_SERVICE_NAME = YOUR_SERVICE_NAME` - Ensure you define it as a string value that represents the function name and its business logic such as "Check SQS Lambda". This will appear as the tracing service name in Sumo Logic.
- * `OTEL_RESOURCE_ATTRIBUTES` - Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
+ * `OTEL_RESOURCE_ATTRIBUTES` - Sets OpenTelemetry resources. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. (For more information, see [Add Services Panel to Dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)). Tracing `application` and `cloud.account.id` are set with the `OTEL_RESOURCE_ATTRIBUTES` environment variable:
* `application=YOUR_APPLICATION_NAME` - the string value, if the function is a part of complex system/application then set it for all other functions/applications.
* `cloud.account.id=YOUR_CLOUD_ACCOUNT_ID` - set an additional tag that will contain your [AWS Lambda Account ID](https://docs.aws.amazon.com/general/latest/gr/acct-identifiers.html). This will help to provide more relevant data.
All of the attributes above are comma separated key/value pairs (this is also a way to add additional information to the spans, just after comma add additional key=value pair), such as `OTEL_RESOURCE_ATTRIBUTES=application=YOUR_APPLICATION_NAME,cloud.account.id=123456789012`.
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/go/index.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/go/index.md
index 015bde0281..7878fda6f3 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/go/index.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/go/index.md
@@ -103,7 +103,7 @@ func main() {
The last step is to configure few other things like:
* `SERVICE_NAME`. Insert the application service name. Ensure the string value represents its business logic, such as "SumoWebCall". This will appear as a tracing service name in Sumo Logic.
-* `APPLICATION_NAME`. Insert the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma separated key=value pairs. For example, add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels (for more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels)).
+* `APPLICATION_NAME`. Insert the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma separated key=value pairs. For example, add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels (for more information, see [Add services panel to dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard)).
* `ENDPOINT_ADDRESS`. OTLP HTTP (default port 4318) endpoint address must be provided with the location of the OpenTelemetry Collector/Agent (recommended for production) or [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp). Refer to the following setup instructions if you haven't yet installed a collector:
* [Set up traces collection for Kubernetes environments](/docs/apm/traces/get-started-transaction-tracing/set-up-traces-collection-for-kubernetes-environments.md)
* [Set up traces collection for other environments usage](/docs/apm/traces/get-started-transaction-tracing/set-up-traces-collection-for-other-environments.md)
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/java/custom-tags-configuration.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/java/custom-tags-configuration.md
index e62ad95280..b40fe86355 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/java/custom-tags-configuration.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/java/custom-tags-configuration.md
@@ -13,7 +13,7 @@ OTEL_RESOURCE_ATTRIBUTES="service.name=Accounts"
OTEL_RESOURCE_ATTRIBUTES="application=OnlineBanking,exampleKey=exampleValue"
```
-Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels).
+Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Add services panel to dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard).
## Custom tags configuration through your code
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/javascript/index.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/javascript/index.md
index 49d4e5c6af..0630b7282f 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/javascript/index.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/javascript/index.md
@@ -84,7 +84,7 @@ Remember to provide configuration using environment variables:
* [Set up traces collection for Kubernetes environments](/docs/apm/traces/get-started-transaction-tracing/set-up-traces-collection-for-kubernetes-environments.md)
* [Set up traces collection for other environments usage](/docs/apm/traces/get-started-transaction-tracing/set-up-traces-collection-for-other-environments.md)
* `OTEL_SERVICE_NAME`. A logical service name that represents its business logic.
-* `OTEL_RESOURCE_ATTRIBUTES`. Set "application" name attribute which should represent its business logic and extra attributes attached to all spans. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels).
+* `OTEL_RESOURCE_ATTRIBUTES`. Set "application" name attribute which should represent its business logic and extra attributes attached to all spans. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Add services panel to dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard).
**Example:**
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/net/index.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/net/index.md
index 8ec19fc073..23e1c11036 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/net/index.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/net/index.md
@@ -49,7 +49,7 @@ The final step is to configure the exporter endpoint, service and application na
* `OTEL_EXPORTER_OTLP_PROTOCOL=http/protobuf` - configures OTLP exporter to use OTLP HTTP protocol
* `OTEL_EXPORTER_OTLP_ENDPOINT=http://OTLP_HTTP_ENDPOINT:4318` - environment variable configures the endpoint where telemetry data will be sent. The value of the variable points to OpenTelemetry Collector/Agent (recommended for production) or [OTLP/HTTP source](/docs/send-data/hosted-collectors/http-source/otlp).
* `OTEL_SERVICE_NAME=SERVICE_NAME` - configure the service name. Ensure the string value represents its business logic, such as "FinanceServiceCall". This will appear as a tracing service name in Sumo Logic.
-* `OTEL_RESOURCE_ATTRIBUTES=application=APPLICATION_NAME` - configure the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma-separated key=value pairs. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels).
+* `OTEL_RESOURCE_ATTRIBUTES=application=APPLICATION_NAME` - configure the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma-separated key=value pairs. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Add services panel to dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard).
More extensive description of all available options can be found [here](https://github.com/open-telemetry/opentelemetry-dotnet-instrumentation/blob/main/docs/config.md)
diff --git a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby-on-rails.md b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby-on-rails.md
index e32e0809cb..b8244518a3 100644
--- a/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby-on-rails.md
+++ b/docs/apm/traces/get-started-transaction-tracing/opentelemetry-instrumentation/ruby-on-rails.md
@@ -96,7 +96,7 @@ The final step is to configure the exporter host, service and application name.
* `OTEL_SERVICE_NAME=SERVICE_NAME` - configure the service name. Ensure the string value represents its business logic, such as "FinanceServiceCall". This will appear as a tracing service name in Sumo Logic.
-* `OTEL_RESOURCE_ATTRIBUTES=application=APPLICATION_NAME` - configure the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma-separated key=value pairs. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Services Dashboard Panels](/docs/apm/traces/services-list-map#services-dashboard-panels).
+* `OTEL_RESOURCE_ATTRIBUTES=application=APPLICATION_NAME` - configure the application name. This will appear as a tracing application name in Sumo Logic. Additional attributes can be added here as comma-separated key=value pairs. Add the `deployment.environment=[environment-name]` tag as needed to allow for filtering by environment on dashboard panels. For more information, see [Add services panel to dashboard](/docs/apm/services-list-map/#add-services-panel-to-dashboard).
## TraceID, SpanID and operation data injection into logs
diff --git a/docs/apm/traces/index.md b/docs/apm/traces/index.md
index b98e4f1d04..97bbe24440 100644
--- a/docs/apm/traces/index.md
+++ b/docs/apm/traces/index.md
@@ -32,7 +32,7 @@ This guide provides information to work with your tracing data.
View your application topology and investigate microservice interactions.
Learn how to use the Spans page to explore your span data.
+Application Monitoring provides three Service and Application dashboard views. This allows you to review tracing data by application (all or grouped), environment, and services by top level and breaking down their health by application. This helps you review the most active operations performed on specified applications and services. See [Service Map Traces](/docs/apm/services-list-map) and [Sumo Logic Apps](/docs/integrations) for more info.
### Real User Monitoring
diff --git a/docs/dashboards/panels/index.md b/docs/dashboards/panels/index.md
index 3b43bffcb6..90aafc7a31 100644
--- a/docs/dashboards/panels/index.md
+++ b/docs/dashboards/panels/index.md
@@ -167,7 +167,7 @@ The link is displayed is in the panel.
+1. With the Dashboard open, click the **Add Panel** button.
1. A panel configuration page opens.
1. Configure a [Trace query](/docs/apm/traces/view-and-investigate-traces) to search for desired set of traces.
1. Select a time range or [create a custom range](/docs/dashboards/set-custom-time-ranges) for the panel. You can set this when creating or at any time when viewing the Dashboard panel.
diff --git a/docs/manage/security/audit-indexes/search-audit-index.md b/docs/manage/security/audit-indexes/search-audit-index.md
index 2323121c46..fbd5c2f95d 100644
--- a/docs/manage/security/audit-indexes/search-audit-index.md
+++ b/docs/manage/security/audit-indexes/search-audit-index.md
@@ -1,12 +1,12 @@
---
id: search-audit-index
title: Search Audit Index
-description: The Search Audit Index provides event logs on search usage and activities for your account.
+description: The Search Audit Index provides event logs on search usage and activities for your account.
---
import useBaseUrl from '@docusaurus/useBaseUrl';
-The Search Audit Index provides event logs on search usage and activities for your account. The index allows you to monitor and audit the search queries being run within your account, the types of queries, the users running them, and more.
+The Search Audit Index provides event logs on search usage and activities for your account. The index allows you to monitor and audit the search queries being run within your account, the types of queries, the users running them, and more.
To visualize your Search Audit Index data, download the [Enterprise Search Audit App](/docs/integrations/sumo-apps/enterprise-search-audit), which provides pre-built dashboards and reports to help you analyze your current search use and identify areas for improvement.
@@ -25,7 +25,7 @@ The Search Audit Index must be enabled by an administrator.
To enable the Search Audit Index:
-1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). In the main Sumo Logic menu, select **Administration > Security > Policies**.
:::note
@@ -91,4 +91,4 @@ The table below shows the possible values for the `query_type` field.
| Sumo Internal | The Internal searches Sumo Logic runs in the background that are critical in providing other services (for example, autocomplete, scheduled view optimization, etc.). |
| Auto Refresh Dashboard | Search queries used to power auto refresh dashboard panels. |
| Monitor | Queries associated with [monitors](/docs/alerts/monitors). |
-| Span Analytics | Queries run for filtering and aggregating trace data based on [span attributes](/docs/apm/traces/spans) to understand application services performance. Queries can be built using input fields, with filters and visualized results available. |
+| Span Analytics | Queries run for filtering and aggregating trace data based on [span attributes](/docs/apm/spans) to understand application services performance. Queries can be built using input fields, with filters and visualized results available. |
diff --git a/sidebars.ts b/sidebars.ts
index c67c30e977..721070c2c4 100644
--- a/sidebars.ts
+++ b/sidebars.ts
@@ -1789,8 +1789,6 @@ module.exports = {
],
},
'apm/traces/view-and-investigate-traces',
- 'apm/traces/spans',
- 'apm/traces/services-list-map',
'apm/traces/tracing-dashboards',
'apm/traces/search-query-language-support-for-traces',
'apm/traces/tracing-ingest',
@@ -1821,6 +1819,8 @@ module.exports = {
'apm/real-user-monitoring/dashboards',
],
},
+ 'apm/spans',
+ 'apm/services-list-map',
],
},
],
diff --git a/static/img/apm/traces/Service-Dashboards-from-traces.png b/static/img/apm/Service-Dashboards-from-traces.png
similarity index 100%
rename from static/img/apm/traces/Service-Dashboards-from-traces.png
rename to static/img/apm/Service-Dashboards-from-traces.png
diff --git a/static/img/apm/traces/create-servicemap.png b/static/img/apm/create-servicemap.png
similarity index 100%
rename from static/img/apm/traces/create-servicemap.png
rename to static/img/apm/create-servicemap.png
diff --git a/static/img/apm/traces/dropdown-for-spans-filter.png b/static/img/apm/dropdown-for-spans-filter.png
similarity index 100%
rename from static/img/apm/traces/dropdown-for-spans-filter.png
rename to static/img/apm/dropdown-for-spans-filter.png
diff --git a/static/img/apm/traces/enable-alerts.png b/static/img/apm/enable-alerts.png
similarity index 100%
rename from static/img/apm/traces/enable-alerts.png
rename to static/img/apm/enable-alerts.png
diff --git a/static/img/apm/traces/facets-add-to-query.png b/static/img/apm/facets-add-to-query.png
similarity index 100%
rename from static/img/apm/traces/facets-add-to-query.png
rename to static/img/apm/facets-add-to-query.png
diff --git a/static/img/apm/traces/Facets-expanded.png b/static/img/apm/facets-expanded.png
similarity index 100%
rename from static/img/apm/traces/Facets-expanded.png
rename to static/img/apm/facets-expanded.png
diff --git a/static/img/apm/traces/filter-servicemap.png b/static/img/apm/filter-servicemap.png
similarity index 100%
rename from static/img/apm/traces/filter-servicemap.png
rename to static/img/apm/filter-servicemap.png
diff --git a/static/img/apm/traces/pause-or-stop-spans-query.png b/static/img/apm/pause-or-stop-spans-query.png
similarity index 100%
rename from static/img/apm/traces/pause-or-stop-spans-query.png
rename to static/img/apm/pause-or-stop-spans-query.png
diff --git a/static/img/apm/traces/service-color-traces-span.png b/static/img/apm/service-color-traces-span.png
similarity index 100%
rename from static/img/apm/traces/service-color-traces-span.png
rename to static/img/apm/service-color-traces-span.png
diff --git a/static/img/apm/traces/service-latency.png b/static/img/apm/service-latency.png
similarity index 100%
rename from static/img/apm/traces/service-latency.png
rename to static/img/apm/service-latency.png
diff --git a/static/img/apm/traces/service-percentile-by-time.png b/static/img/apm/service-percentile-by-time.png
similarity index 100%
rename from static/img/apm/traces/service-percentile-by-time.png
rename to static/img/apm/service-percentile-by-time.png
diff --git a/static/img/apm/services-list-display.png b/static/img/apm/services-list-display.png
new file mode 100644
index 0000000000..8248dc3575
Binary files /dev/null and b/static/img/apm/services-list-display.png differ
diff --git a/static/img/apm/traces/services-list-filters.png b/static/img/apm/services-list-filters.png
similarity index 100%
rename from static/img/apm/traces/services-list-filters.png
rename to static/img/apm/services-list-filters.png
diff --git a/static/img/apm/traces/services-list-map-auto-detection-settings.png b/static/img/apm/services-list-map-auto-detection-settings.png
similarity index 100%
rename from static/img/apm/traces/services-list-map-auto-detection-settings.png
rename to static/img/apm/services-list-map-auto-detection-settings.png
diff --git a/static/img/apm/traces/services-list-map-example.png b/static/img/apm/services-list-map-example.png
similarity index 100%
rename from static/img/apm/traces/services-list-map-example.png
rename to static/img/apm/services-list-map-example.png
diff --git a/static/img/apm/traces/services-list-map-manual-detection-settings.png b/static/img/apm/services-list-map-manual-detection-settings.png
similarity index 100%
rename from static/img/apm/traces/services-list-map-manual-detection-settings.png
rename to static/img/apm/services-list-map-manual-detection-settings.png
diff --git a/static/img/apm/services-list-settings.png b/static/img/apm/services-list-settings.png
new file mode 100644
index 0000000000..3a9d97027e
Binary files /dev/null and b/static/img/apm/services-list-settings.png differ
diff --git a/static/img/apm/traces/services-list.png b/static/img/apm/services-list.png
similarity index 100%
rename from static/img/apm/traces/services-list.png
rename to static/img/apm/services-list.png
diff --git a/static/img/apm/traces/add-servicemap.png b/static/img/apm/services-map-dashboard.png
similarity index 100%
rename from static/img/apm/traces/add-servicemap.png
rename to static/img/apm/services-map-dashboard.png
diff --git a/static/img/apm/traces/servicemap.png b/static/img/apm/services-map-icon.png
similarity index 100%
rename from static/img/apm/traces/servicemap.png
rename to static/img/apm/services-map-icon.png
diff --git a/static/img/apm/traces/services-map-legend.png b/static/img/apm/services-map-legend.png
similarity index 100%
rename from static/img/apm/traces/services-map-legend.png
rename to static/img/apm/services-map-legend.png
diff --git a/static/img/apm/traces/services-map.png b/static/img/apm/services-map.png
similarity index 100%
rename from static/img/apm/traces/services-map.png
rename to static/img/apm/services-map.png
diff --git a/static/img/apm/traces/span-count-histogram.png b/static/img/apm/span-count-histogram.png
similarity index 100%
rename from static/img/apm/traces/span-count-histogram.png
rename to static/img/apm/span-count-histogram.png
diff --git a/static/img/apm/traces/span-count-timeseries.png b/static/img/apm/span-count-timeseries.png
similarity index 100%
rename from static/img/apm/traces/span-count-timeseries.png
rename to static/img/apm/span-count-timeseries.png
diff --git a/static/img/apm/span-dashboard.png b/static/img/apm/span-dashboard.png
new file mode 100644
index 0000000000..8f86d8d96c
Binary files /dev/null and b/static/img/apm/span-dashboard.png differ
diff --git a/static/img/apm/traces/span-event-marker.png b/static/img/apm/span-event-marker.png
similarity index 100%
rename from static/img/apm/traces/span-event-marker.png
rename to static/img/apm/span-event-marker.png
diff --git a/static/img/apm/traces/span-event-markers.gif b/static/img/apm/span-event-markers.gif
similarity index 100%
rename from static/img/apm/traces/span-event-markers.gif
rename to static/img/apm/span-event-markers.gif
diff --git a/static/img/apm/traces/span-event-more1.png b/static/img/apm/span-event-more1.png
similarity index 100%
rename from static/img/apm/traces/span-event-more1.png
rename to static/img/apm/span-event-more1.png
diff --git a/static/img/apm/traces/span-event-more2.png b/static/img/apm/span-event-more2.png
similarity index 100%
rename from static/img/apm/traces/span-event-more2.png
rename to static/img/apm/span-event-more2.png
diff --git a/static/img/apm/traces/span-event-select.png b/static/img/apm/span-event-select.png
similarity index 100%
rename from static/img/apm/traces/span-event-select.png
rename to static/img/apm/span-event-select.png
diff --git a/static/img/apm/traces/span-hover-view.png b/static/img/apm/span-hover-view.png
similarity index 100%
rename from static/img/apm/traces/span-hover-view.png
rename to static/img/apm/span-hover-view.png
diff --git a/static/img/apm/traces/span-logs-in-details-pane.png b/static/img/apm/span-logs-in-details-pane.png
similarity index 100%
rename from static/img/apm/traces/span-logs-in-details-pane.png
rename to static/img/apm/span-logs-in-details-pane.png
diff --git a/static/img/apm/traces/span-open-in-search.png b/static/img/apm/span-open-in-search.png
similarity index 100%
rename from static/img/apm/traces/span-open-in-search.png
rename to static/img/apm/span-open-in-search.png
diff --git a/static/img/apm/traces/add-to-dashboard-spans.png b/static/img/apm/spans-add-to-dashboard.png
similarity index 100%
rename from static/img/apm/traces/add-to-dashboard-spans.png
rename to static/img/apm/spans-add-to-dashboard.png
diff --git a/static/img/apm/traces/sumo-logic-spans-aggregates-visualize.png b/static/img/apm/spans-aggregates-visualize.png
similarity index 100%
rename from static/img/apm/traces/sumo-logic-spans-aggregates-visualize.png
rename to static/img/apm/spans-aggregates-visualize.png
diff --git a/static/img/apm/traces/spans-basic-example-with-where-operations.png b/static/img/apm/spans-basic-example-with-where-operations.png
similarity index 100%
rename from static/img/apm/traces/spans-basic-example-with-where-operations.png
rename to static/img/apm/spans-basic-example-with-where-operations.png
diff --git a/static/img/apm/spans-messages-results.png b/static/img/apm/spans-messages-results.png
new file mode 100644
index 0000000000..b4dc301784
Binary files /dev/null and b/static/img/apm/spans-messages-results.png differ
diff --git a/static/img/apm/spans-page.png b/static/img/apm/spans-page.png
new file mode 100644
index 0000000000..466a3ccde6
Binary files /dev/null and b/static/img/apm/spans-page.png differ
diff --git a/static/img/apm/traces/blank-spans-query.png b/static/img/apm/spans-query-blank.png
similarity index 100%
rename from static/img/apm/traces/blank-spans-query.png
rename to static/img/apm/spans-query-blank.png
diff --git a/static/img/apm/spans-query.png b/static/img/apm/spans-query.png
new file mode 100644
index 0000000000..44a1343923
Binary files /dev/null and b/static/img/apm/spans-query.png differ
diff --git a/static/img/apm/traces/spans-search-button.png b/static/img/apm/spans-search-button.png
similarity index 100%
rename from static/img/apm/traces/spans-search-button.png
rename to static/img/apm/spans-search-button.png
diff --git a/static/img/apm/traces/spans-search-with-fields-highlighted.png b/static/img/apm/spans-search-with-fields-highlighted.png
similarity index 100%
rename from static/img/apm/traces/spans-search-with-fields-highlighted.png
rename to static/img/apm/spans-search-with-fields-highlighted.png
diff --git a/static/img/apm/traces/status-codes-spans-example.png b/static/img/apm/spans-status-codes-example.png
similarity index 100%
rename from static/img/apm/traces/status-codes-spans-example.png
rename to static/img/apm/spans-status-codes-example.png
diff --git a/static/img/apm/spans-time-range.png b/static/img/apm/spans-time-range.png
new file mode 100644
index 0000000000..ca1136477e
Binary files /dev/null and b/static/img/apm/spans-time-range.png differ
diff --git a/static/img/apm/traces/spans-with-where-operation-example.png b/static/img/apm/spans-with-where-operation-example.png
similarity index 100%
rename from static/img/apm/traces/spans-with-where-operation-example.png
rename to static/img/apm/spans-with-where-operation-example.png
diff --git a/static/img/apm/traces/Spans-page.png b/static/img/apm/traces/Spans-page.png
deleted file mode 100644
index 1720291558..0000000000
Binary files a/static/img/apm/traces/Spans-page.png and /dev/null differ
diff --git a/static/img/apm/traces/messages-results.png b/static/img/apm/traces/messages-results.png
deleted file mode 100644
index cae7ab0bf9..0000000000
Binary files a/static/img/apm/traces/messages-results.png and /dev/null differ
diff --git a/static/img/apm/traces/open-service-map.png b/static/img/apm/traces/open-service-map.png
deleted file mode 100644
index f0d99fd86d..0000000000
Binary files a/static/img/apm/traces/open-service-map.png and /dev/null differ
diff --git a/static/img/apm/traces/open-spans-from-menu.png b/static/img/apm/traces/open-spans-from-menu.png
deleted file mode 100644
index bde2f2826f..0000000000
Binary files a/static/img/apm/traces/open-spans-from-menu.png and /dev/null differ
diff --git a/static/img/apm/traces/resize-column.png b/static/img/apm/traces/resize-column.png
deleted file mode 100644
index fc25bf49de..0000000000
Binary files a/static/img/apm/traces/resize-column.png and /dev/null differ
diff --git a/static/img/apm/traces/services-list-display.png b/static/img/apm/traces/services-list-display.png
deleted file mode 100644
index 4fc272a2fb..0000000000
Binary files a/static/img/apm/traces/services-list-display.png and /dev/null differ
diff --git a/static/img/apm/traces/services-list-settings.png b/static/img/apm/traces/services-list-settings.png
deleted file mode 100644
index 4f3067f5c3..0000000000
Binary files a/static/img/apm/traces/services-list-settings.png and /dev/null differ
diff --git a/static/img/apm/traces/span-dashboard.png b/static/img/apm/traces/span-dashboard.png
deleted file mode 100644
index 4803d6ed65..0000000000
Binary files a/static/img/apm/traces/span-dashboard.png and /dev/null differ
diff --git a/static/img/apm/traces/spans-query.png b/static/img/apm/traces/spans-query.png
deleted file mode 100644
index 1c01bc220b..0000000000
Binary files a/static/img/apm/traces/spans-query.png and /dev/null differ
diff --git a/static/img/apm/traces/spans-time-range.png b/static/img/apm/traces/spans-time-range.png
deleted file mode 100644
index 147259e97c..0000000000
Binary files a/static/img/apm/traces/spans-time-range.png and /dev/null differ