diff --git a/docs/alerts/monitors/alert-response.md b/docs/alerts/monitors/alert-response.md index 9e4405a4fc..0083acb183 100644 --- a/docs/alerts/monitors/alert-response.md +++ b/docs/alerts/monitors/alert-response.md @@ -86,23 +86,23 @@ To resolve an alert, click a row to select it, then click **Resolve**. ## Translating thresholds -Threshold translating allows you to open the alert response page in the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer) that helps you to easily view the threshold associated with an alert. This also helps you to understand how your monitor's thresholds are translating into metrics and compare the threshold values set in a monitor with the data displayed in the Metrics Explorer chart. +Threshold translating allows you to open the alert response page in the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer) that helps you to easily view the threshold associated with an alert. This also helps you to understand how your monitor's thresholds are translating into metrics and compare the threshold values set in a monitor with the data displayed in the Metrics Search chart. -For example, when you open an alert response page in Metrics Explorer, you can see critical thresholds defined with some number. You can then see that this threshold is also applied and enabled in the Metrics Explorer view, with exactly the same number defined.
arp-metrics-explorer +For example, when you open an alert response page in Metrics Search, you can see critical thresholds defined with some number. You can then see that this threshold is also applied and enabled in the Metrics Search view, with exactly the same number defined.
arp-metrics-explorer -To view the alert response chart in Metrics Explorer, follow the steps below: +To view the alert response chart in Metrics Search, follow the steps below: 1. Navigate to your [Alert List](#alert-list) and select the alert for which you want to view the corresponding metrics and threshold values. -1. Click the **View in Metrics Explorer** button for that alert. You can click on either of the two buttons, and they both function the same way. -1. The Metrics Explorer view will open with the graph of the metric associated with the alert. -1. In the **Threshold** section of the Metrics Explorer, you can see the same threshold values for the monitor associated with the alert.
threshold-metrics-explorer +1. Click the **View in Metrics Search** button for that alert. You can click on either of the two buttons, and they both function the same way. +1. The Metrics Search view will open with the graph of the metric associated with the alert. +1. In the **Threshold** section of the Metrics Search, you can see the same threshold values for the monitor associated with the alert.
threshold-metrics-explorer 1. The thresholds will be enabled and only the ones that are defined in the monitor will be displayed. - * If the alert has both critical and warning thresholds defined in the corresponding monitor, both thresholds will be displayed in the Metrics Explorer view. - * If the alert has only a critical threshold defined in the corresponding monitor, only the warning threshold will be displayed in the Metrics Explorer view. -1. Use this feature to compare the threshold values set in a monitor with the data displayed in the Metrics Explorer graph and gain a better understanding of how your monitors are translating into metrics. + * If the alert has both critical and warning thresholds defined in the corresponding monitor, both thresholds will be displayed in the Metrics Search view. + * If the alert has only a critical threshold defined in the corresponding monitor, only the warning threshold will be displayed in the Metrics Search view. +1. Use this feature to compare the threshold values set in a monitor with the data displayed in the Metrics Search graph and gain a better understanding of how your monitors are translating into metrics. :::note -Note that the same threshold translating functionality supports to [Create Monitors from the Metrics Explorer](/docs/alerts/monitors/create-monitor/#from-metrics-explorer) and [Opening a Monitor in the Metrics Explorer](/docs/alerts/monitors/settings/#view-in-metrics-explorer). +Note that the same threshold translating functionality supports to [Create Monitors from the Metrics Search](/docs/alerts/monitors/create-monitor/#from-metrics-search) and [Opening a Monitor in the Metrics Search](/docs/alerts/monitors/settings/#view-in-metrics-search). ::: ## Alert details diff --git a/docs/alerts/monitors/create-monitor.md b/docs/alerts/monitors/create-monitor.md index bcd627d0db..b8d63a4c83 100644 --- a/docs/alerts/monitors/create-monitor.md +++ b/docs/alerts/monitors/create-monitor.md @@ -40,19 +40,19 @@ Click the kebab icon in the upper right corner, then **Create a Monitor**. --> -### From Metrics Explorer +### From Metrics Search Creating a monitor based on the threshold values defined in the Metrics page can save time and effort. By using the pre-filled monitor editor, you can quickly create a monitor with the same threshold values as defined in the Metrics page. This will ensure that the monitor is using the same criteria as the Metrics page, providing consistency in monitoring. -To create a monitor from the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer/), follow the steps below: +To create a monitor from the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer/), follow the steps below: -1. Open the **Metrics Explorer**: +1. Open the **Metrics Search**: * [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). From Sumo Logic home, click **Metrics**.
Screenshot of the Sumo Logic home page with rectangle around the Metrics icon * [**New UI**](/docs/get-started/sumo-logic-ui). Click the **Go To...** menu at the top of the screen and select **Metrics Search**. -1. On the **Metrics Explorer** page: +1. On the **Metrics Search** page: 1. Enter a metrics query.
Metrics explorer query - 1. In the **Thresholds** section, define the critical and warning thresholds for your metrics query.
Screenshot of the Metrics Explorer in Sumo Logic, displaying a line chart for node memory utilization over time. The chart shows the memory utilization metric from 17:42:12 to 17:57:12 on 21/02/2023. The right side of the screen includes a thresholds panel with critical and warning thresholds set to 500000000 and 80, respectively. The 'Fill remaining area as green' option is toggled off. -1. Click the three-dot kebab icon button at the end of the query field and select **Create a Monitor**.
Screenshot of the Metrics Explorer in Sumo Logic, showing the dropdown menu accessed via the three vertical dots icon. The menu includes options for Basic Mode, Duplicate Query, Create a Monitor, and Create an SLO. The option 'Create a Monitor' is highlighted. Below the menu, the thresholds panel shows critical and warning thresholds set to 500000000 and 80, respectively, with the 'Fill remaining area as green' option toggled off. + 1. In the **Thresholds** section, define the critical and warning thresholds for your metrics query.
Screenshot of the Metrics Search in Sumo Logic, displaying a line chart for node memory utilization over time. The chart shows the memory utilization metric from 17:42:12 to 17:57:12 on 21/02/2023. The right side of the screen includes a thresholds panel with critical and warning thresholds set to 500000000 and 80, respectively. The 'Fill remaining area as green' option is toggled off. +1. Click the three-dot kebab icon button at the end of the query field and select **Create a Monitor**.
Screenshot of the Metrics Search in Sumo Logic, showing the dropdown menu accessed via the three vertical dots icon. The menu includes options for Basic Mode, Duplicate Query, Create a Monitor, and Create an SLO. The option 'Create a Monitor' is highlighted. Below the menu, the thresholds panel shows critical and warning thresholds set to 500000000 and 80, respectively, with the 'Fill remaining area as green' option toggled off. 1. The **New Monitor** will open with prefilled data based on the threshold values you set in the previous steps.
Screenshot of the 'New Monitor' setup page in Sumo Logic, specifically focusing on the Trigger Conditions section. The Monitor Type is set to Metrics and Detection Method to Static. The query is set for node memory utilization for a specific collector. The Alert Grouping options include one alert per monitor or one alert per time series. The Trigger Type section shows critical alerts set to trigger when the result is greater than or equal to 500000000 within 15 minutes. The recovery settings are enabled to recover automatically when the result is less than 500000000 within a 15-minute window. Historical Trend is displayed below, with a dashed red line indicating the threshold. 1. In the **Trigger Type** section, enable the checkbox that corresponds to the threshold value that you want to use (Critical and/or Warning). * The threshold values will be the same as defined in the Metrics page for both Critical and Warning thresholds. @@ -62,10 +62,10 @@ To create a monitor from the [Metrics Explorer](/docs/metrics/metrics-queries/me 1. The same threshold will also be applied to the histogram chart. :::note -The same threshold translating functionality supports [opening the Alerts Response Page in the Metrics Explorer](/docs/alerts/monitors/alert-response/#translating-thresholds) and [opening a monitor in the Metrics Explorer](/docs/alerts/monitors/settings/#view-in-metrics-explorer). +The same threshold translating functionality supports [opening the Alerts Response Page in the Metrics Search](/docs/alerts/monitors/alert-response/#translating-thresholds) and [opening a monitor in the Metrics Search](/docs/alerts/monitors/settings/#view-in-metrics-search). ::: :::tip -When you create a monitor and open the metrics search query in the Metrics Explorer, the signal gets a new value for the [`quantize`](/docs/metrics/metrics-operators/quantize/) operator based on the time range of the query. The default value for the `quantize` operator is `1m`. Because opening the query in Metrics Explorer may not match because of quantization differences, you may need to adjust the query to return the results you expect, especially when creating a monitor that uses the [anomaly detection method](#detection-method).
Metrics query with quantize +When you create a monitor and open the metrics search query in the Metrics Search, the signal gets a new value for the [`quantize`](/docs/metrics/metrics-operators/quantize/) operator based on the time range of the query. The default value for the `quantize` operator is `1m`. Because opening the query in Metrics Search may not match because of quantization differences, you may need to adjust the query to return the results you expect, especially when creating a monitor that uses the [anomaly detection method](#detection-method).
Metrics query with quantize ::: ## Step 1. Set trigger conditions diff --git a/docs/alerts/monitors/settings.md b/docs/alerts/monitors/settings.md index a6ed2b8ef7..d0ae8686f1 100644 --- a/docs/alerts/monitors/settings.md +++ b/docs/alerts/monitors/settings.md @@ -52,17 +52,17 @@ Click on any monitor in your **Monitors** table, and the **Monitor Details** tab For logs monitors, the **View in Log Search** button opens a new **Log Search** page with the monitor’s query preloaded in the search field. You can run the query to compare the search results against the threshold values set in your monitor. -### View in Metrics Explorer +### View in Metrics Search -For metrics monitors, the **View in Metrics Explorer** button opens the Metrics Explorer with the monitor’s threshold values pre-applied. This allows you to compare the set thresholds against real-time data in the Metrics Explorer graph. +For metrics monitors, the **View in Metrics Search** button opens the Metrics Search with the monitor’s threshold values pre-applied. This allows you to compare the set thresholds against real-time data in the Metrics Search graph. 1. Navigate to the **Trigger Conditions** section and note the thresholds values defined for Critical and Warning data conditions. All other parameters, such as the 15-minute window and the "at all times" option, will be set to default.
view-in-explorer-page -1. Click **View in Metrics Explorer**. The Metrics Explorer page will display with the same threshold values applied to the panel and graph.
view-in-explorer-page +1. Click **View in Metrics Search**. The Metrics Search page will display with the same threshold values applied to the panel and graph. 1. On the **Panel settings** page, click threshold icon to view the defined threshold values for the monitor.
thresholds-icon 1. To adjust the chart view, you may need to change the time range in the graph, as the default window is set to 15 minutes.
thresholds-graph :::note -The same threshold translation functionality applies when [creating a monitor from Metrics Explorer](/docs/alerts/monitors/create-monitor/#from-metrics-explorer) and when [opening the Alert Response page in Metrics Explorer](/docs/alerts/monitors/alert-response/#translating-thresholds). +The same threshold translation functionality applies when [creating a monitor from Metrics Search](/docs/alerts/monitors/create-monitor/#from-metrics-search) and when [opening the Alert Response page in Metrics Search](/docs/alerts/monitors/alert-response/#translating-thresholds). ::: ### Edit a monitor diff --git a/docs/apm/real-user-monitoring/metrics.md b/docs/apm/real-user-monitoring/metrics.md index 6dd3d47c5b..5182d9f244 100644 --- a/docs/apm/real-user-monitoring/metrics.md +++ b/docs/apm/real-user-monitoring/metrics.md @@ -10,7 +10,7 @@ RUM metrics are automatically generated for you from browser traces. They provid Metrics are collected for user actions representing document loads, which means actual retrieval and execution of web documents in the browser as well as XHR calls and route changes. Measurements include W3C navigation timings, XHR delays, Core Web Vitals KPIs, longtask events (delays) and others. -For ad hoc queries, you can find these metrics in [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer.md) by querying for: +For ad hoc queries, you can find these metrics in [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer.md) by querying for: ```sql _contenttype=rummetricfromtrace ``` diff --git a/docs/dashboards/about.md b/docs/dashboards/about.md index 6db982c18e..d476fe4fa4 100644 --- a/docs/dashboards/about.md +++ b/docs/dashboards/about.md @@ -27,7 +27,7 @@ See [Migrate to Dashboards](/docs/dashboards/dashboards-migration). * Dashboard template variables provide full replacement control over what is inserted, and the variables work across both log and metric panels. * Dashboard provides a dashboard-first view to build, maintain, and interact with dashboards. With Dashboard you can build panels inside the dashboard rather than adding panels from the Search or Metrics pages. -* Dashboard utilizes the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer/) with full text auto-complete capabilities, so you can quickly find the metrics you are looking for. +* Dashboard utilizes the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer/) with full text auto-complete capabilities, so you can quickly find the metrics you are looking for. The following table shows the availability of features for Dashboard. diff --git a/docs/dashboards/create-dashboard-new.md b/docs/dashboards/create-dashboard-new.md index 991c93bb3c..cafd667d61 100644 --- a/docs/dashboards/create-dashboard-new.md +++ b/docs/dashboards/create-dashboard-new.md @@ -67,7 +67,7 @@ Enter your aggregate [search query](/docs/search/search-query-language/group-agg Click the left-most dropdown option and select **Metrics**. You should be familiar with the basics of creating [metrics queries](/docs/metrics/metrics-queries) to ensure successful results. By default, the query builder is set to **Logs**. -To create a metrics query utilize the [Metrics Explorer](../metrics/metrics-queries/metrics-explorer.md). +To create a metrics query utilize the [Metrics Search](../metrics/metrics-queries/metrics-explorer.md). ### Multiple Query @@ -104,7 +104,7 @@ To create a Dashboard from the [Log Search page](/docs/search): To create a Dashboard from the [Metrics page](/docs/metrics/metrics-queries): -1. From the Metrics page click the **Add to Dashboard** button on the [Metrics Explorer](../metrics/metrics-queries/metrics-explorer.md).
metrics explorer add to dashboard +1. From the Metrics page click the **Add to Dashboard** button on the [Metrics Search](../metrics/metrics-queries/metrics-explorer.md).
metrics explorer 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 will have an option to select **Create New Dashboard** with your name. Select that option.
Enter dashboard new name logs 1. In the updated window toggle the **Create as Dashboard** option.
Create new dashboard new from search page 1. Click **Add** and your new Dashboard is created. diff --git a/docs/dashboards/panels/single-value-charts.md b/docs/dashboards/panels/single-value-charts.md index 9cc11f6701..86227b7ead 100644 --- a/docs/dashboards/panels/single-value-charts.md +++ b/docs/dashboards/panels/single-value-charts.md @@ -26,7 +26,7 @@ To add a panel with a single value chart: Click the left-most dropdown option and select **Metrics**. You should be familiar with the basics of creating [metrics queries](/docs/metrics/metrics-queries) to ensure successful results. By default, the query builder is set to **Logs**.
Metrics selection for query builder - To create a metrics query utilize the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer.md).
new single value chart metrics + To create a metrics query utilize the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer.md).
new single value chart metrics 1. [Modify the chart](./modify-chart.md) as desired. 1. Click the **Add to Dashboard** button on the top right of the window to add the panel to your dashboard.
Add to Dashboard button diff --git a/docs/dashboards/panels/table-charts.md b/docs/dashboards/panels/table-charts.md index 8a29f5f882..dc0875157a 100644 --- a/docs/dashboards/panels/table-charts.md +++ b/docs/dashboards/panels/table-charts.md @@ -28,7 +28,7 @@ To add a panel with a table chart: Click the left-most dropdown option and select **Metrics**. You should be familiar with the basics of creating [metrics queries](/docs/metrics/metrics-queries) to ensure successful results. By default, the query builder is set to **Logs**.
Metrics selection for query builder - To create a metrics query utilize the [Metrics Explorer](/docs/metrics/metrics-queries). + To create a metrics query utilize the [Metrics Search](/docs/metrics/metrics-queries). 1. Once the query runs you will need to flip the chart type to **Table**.
new table chart 1. [Modify the chart](./modify-chart.md) as desired. diff --git a/docs/integrations/containers-orchestration/strimzi-kafka.md b/docs/integrations/containers-orchestration/strimzi-kafka.md index c43128ab31..6353369f7f 100644 --- a/docs/integrations/containers-orchestration/strimzi-kafka.md +++ b/docs/integrations/containers-orchestration/strimzi-kafka.md @@ -196,7 +196,7 @@ If your Kafka helm chart/pod is writing the logs to standard output, then the [S curl http://localhost:8778/jolokia/list ``` -3. The Sumo Logic Kubernetes collection will automatically start collecting logs and metrics from the pods having the annotations and labels defined in the previous steps. Verify logs and metrics are flowing into Sumo Logic by running the following query in [Log Search](/docs/search/get-started-with-search/search-basics/about-search-basics/) and [Metrics Explorer](/docs/metrics/introduction/#metrics-queries): +3. The Sumo Logic Kubernetes collection will automatically start collecting logs and metrics from the pods having the annotations and labels defined in the previous steps. Verify logs and metrics are flowing into Sumo Logic by running the following query in [Log Search](/docs/search/get-started-with-search/search-basics/about-search-basics/) and [Metrics Search](/docs/metrics/introduction/#metrics-queries): ```sql component="messaging" and messaging_system="kafka" ``` diff --git a/docs/metrics/introduction/index.md b/docs/metrics/introduction/index.md index 6402ec62f8..dffbcabb48 100644 --- a/docs/metrics/introduction/index.md +++ b/docs/metrics/introduction/index.md @@ -5,6 +5,8 @@ sidebar_label: Introduction to Metrics description: Sumo Logic Metrics is an effective tool for monitoring, troubleshooting, and identifying the root causes of problems. --- +import useBaseUrl from '@docusaurus/useBaseUrl'; + Metrics are an effective tool for monitoring, troubleshooting, and identifying the root causes of problems. This page is a high-level overview of metrics in Sumo Logic and the terminology we use to talk about metrics. @@ -86,15 +88,16 @@ For more information, see [About Metrics Rules](/docs/metrics/metric-rules-edito ## Metrics queries -[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access Metrics Explorer, go to the **Home** screen and select **Metrics**. +[**Classic UI**](/docs/get-started/sumo-logic-ui-classic). To access Metrics Search, go to the **Home** screen and select **Metrics**. -[**New UI**](/docs/get-started/sumo-logic-ui/). To access Metrics Explorer, in the main Sumo Logic menu select **Observability**, and then under **Metrics** select **Metrics Search**. You can also click the **Go To...** menu at the top of the screen and select **Metrics Search**. +[**New UI**](/docs/get-started/sumo-logic-ui/). To access Metrics Search, in the main Sumo Logic menu select **Observability**, and then under **Metrics** select **Metrics Search**. You can also click the **Go To...** menu at the top of the screen and select **Metrics Search**. -In the screenshot below, the Metrics Explorer shows the results of two queries. +In the screenshot below, the Metrics Search shows the results of two queries. + +Before joining queries -![two-queries.png](/img/metrics/two-queries.png) ### What’s in a metric query? @@ -102,7 +105,7 @@ A metric query consists of a metric, one or more filters and optionally, one or #### Metric -When you [create a metric query](/docs/metrics/metrics-queries/metrics-explorer/#create-a-metric-query) in the Metrics Explorer, the first thing you do is select a metric. When you click in the **Metrics** field, a list of metrics appears.  +When you [create a metric query](/docs/metrics/metrics-queries/metrics-explorer/#create-a-metric-query) in the Metrics Search, the first thing you do is select a metric. When you click in the **Metrics** field, a list of metrics appears.  #### Filters   @@ -119,7 +122,7 @@ For more information, see [Metrics Operators](/docs/metrics/metrics-operators). ## Creating a query -For instructions on how to create a metric query, see [Metrics Explorer](../metrics-queries/metrics-explorer.md#create-a-metric-query).  +For instructions on how to create a metric query, see [Metrics Search](../metrics-queries/metrics-explorer.md#create-a-metric-query).  ### Metricmonitors diff --git a/docs/metrics/introduction/joins.md b/docs/metrics/introduction/joins.md index 4efe406c23..a4dd0e16b8 100644 --- a/docs/metrics/introduction/joins.md +++ b/docs/metrics/introduction/joins.md @@ -23,9 +23,9 @@ By using the [`along`](docs/metrics/metrics-operators/along.md) statement in joi This section explains the benefit of using `along` when you join metrics queries. -In the Metrics Explorer you can run up to six separate queries and display and compare the query results on the same chart. The queries are labeled from #A to #F. +In the Metrics Search you can run up to six separate queries and display and compare the query results on the same chart. The queries are labeled from #A to #F. -multiple-queries.png +multiple-queries.png You can combine (join) the results of multiple queries, or use values from one query to filter values from another. @@ -33,7 +33,7 @@ Here’s an example of a simple join that sums two metrics: `#C: #A + #B` -simple-join.png +simple-join.png This join works fine, if each of the joined queries returns a single result. But, if a query contains references to multiple rows, and two or more of the referenced rows return more than one result, you need to use an `along` statement to match time series from different rows using one or more fields that you specify. @@ -89,7 +89,7 @@ Query #C returns 9 result sets: (metric=CPU_User, account=prod) + (metric=CPU_Sys, account=prod) ``` -join-results-without-along.png +Join results without along Including `along account` in the query ensures that only result sets in which the value of the `account` field match should be used for computation. This narrows down the result set list to the result sets expected. @@ -108,7 +108,7 @@ return same result sets for row #A and #B and only three results for row #C: (metric=CPU_User, account=stage) + (metric=CPU_Sys, account=stage) (metric=CPU_User, account=prod) + (metric=CPU_Sys, account=prod) ``` -three-rows.png +Join results with along ## Quantization and joined queries @@ -124,7 +124,7 @@ For example, consider a joined query that compares the `CPU_User` metric from tw Doing a quick comparison of metrics and average value over a short period can yield can surprising results, as the screenshot below illustrates. -odd-join-results.png +odd-join-results.png :::note query `#C` computed the two values of the average value. diff --git a/docs/metrics/introduction/metric-quantization.md b/docs/metrics/introduction/metric-quantization.md index 96fb5ed62b..0add8b78d0 100644 --- a/docs/metrics/introduction/metric-quantization.md +++ b/docs/metrics/introduction/metric-quantization.md @@ -65,7 +65,7 @@ If you do not use the `quantize to INTERVAL` in your metric query, Sumo automati The age of the metrics in the time range governs the minimum quantization interval (based on what rollups are available for the query time range). Sumo retains only the last 30 days of raw metric data. So, when you query metrics that are more than 30 days old, Sumo must quantize the data to at least 1 hour, because that’s the minimum resolution rollup available given the age of the data. -If you want, you can override the automatic quantization interval. In the Metrics Explorer’s basic mode you can set the quantization interval in the row creator in the UI. In advanced mode, use the `quantize` operator and specify the interval that fits your need +If you want, you can override the automatic quantization interval. In the Metrics Search’s basic mode you can set the quantization interval in the row creator in the UI. In advanced mode, use the `quantize` operator and specify the interval that fits your need Sumo Logic sets the actual quantization interval to be as close to your selection as possible. If it is not possible to set the actual interval to the targeted interval—typically because too many buckets would be produced to reasonably show on the chart—Sumo displays a message like the following: diff --git a/docs/metrics/metrics-operators/count.md b/docs/metrics/metrics-operators/count.md index e1f0011156..46e7fdc8a9 100644 --- a/docs/metrics/metrics-operators/count.md +++ b/docs/metrics/metrics-operators/count.md @@ -33,7 +33,7 @@ metric=size | count by src_ip ### Count of 4xx errors by method -This example shows a query in the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer) in basic mode. In advanced mode, the query would look like: +This example shows a query in the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer) in basic mode. In advanced mode, the query would look like: ```sql metric=4XXError | count by method diff --git a/docs/metrics/metrics-operators/quantize.md b/docs/metrics/metrics-operators/quantize.md index fca312c924..ec7abc45fe 100644 --- a/docs/metrics/metrics-operators/quantize.md +++ b/docs/metrics/metrics-operators/quantize.md @@ -29,7 +29,7 @@ To apply the quantization directly to the selector, `quantize` has to follow the ::: :::note -In the Metrics Explorer, you must [switch to Advanced Mode](/docs/metrics/metrics-queries/metrics-explorer) to enter the `drop last` option. +In the Metrics Search, you must [switch to Advanced Mode](/docs/metrics/metrics-queries/metrics-explorer) to enter the `drop last` option. ::: ## Examples  diff --git a/docs/metrics/metrics-queries/aggregation-tips.md b/docs/metrics/metrics-queries/aggregation-tips.md index 31c8dd4c10..5229f95390 100644 --- a/docs/metrics/metrics-queries/aggregation-tips.md +++ b/docs/metrics/metrics-queries/aggregation-tips.md @@ -6,7 +6,7 @@ sidebar_label: Metric Aggregation Tips import useBaseUrl from '@docusaurus/useBaseUrl'; -When you run a metrics query that returns high cardinality results, the [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer.md) displays a tip for how to use an aggregation clause to produce more readable results. An aggregation tip is displayed for a query based on the cardinality of the query. It is presented when a query’s cardinality exceeds these thresholds: +When you run a metrics query that returns high cardinality results, the [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer.md) displays a tip for how to use an aggregation clause to produce more readable results. An aggregation tip is displayed for a query based on the cardinality of the query. It is presented when a query’s cardinality exceeds these thresholds: @@ -27,7 +27,7 @@ When you run a metrics query that returns high cardinality results, the [Metrics
-Aggregation tips are available in the Metrics Explorer, and in metrics queries in Dashboards. +Aggregation tips are available in the Metrics Search, and in metrics queries in Dashboards. ## View aggregation tips @@ -47,6 +47,6 @@ If you’re running multiple queries, a tip will be provided for each of the que ## Disable tips -If you prefer not to see query tips, choose **Disable Query Tips** from the three-dot kebab menu in the Metrics Explorer. +If you prefer not to see query tips, choose **Disable Query Tips** from the three-dot kebab menu in the Metrics Search. line-commented.png diff --git a/docs/metrics/metrics-queries/funnel-chart.md b/docs/metrics/metrics-queries/funnel-chart.md index 581dafb926..0aa2e9fa27 100644 --- a/docs/metrics/metrics-queries/funnel-chart.md +++ b/docs/metrics/metrics-queries/funnel-chart.md @@ -11,7 +11,7 @@ A funnel chart visualizes categorical data. It’s useful for visualizing the st ## Create a funnel chart -1. Enter and run a metrics query in the Metrics Explorer. +1. Enter and run a metrics query in the Metrics Search. :::note Don't include the `outlier` operator in your query, as it isn't supported in this chart type. 1. Click the **Chart** tab. diff --git a/docs/metrics/metrics-queries/index.md b/docs/metrics/metrics-queries/index.md index 1cad61bea1..914915b175 100644 --- a/docs/metrics/metrics-queries/index.md +++ b/docs/metrics/metrics-queries/index.md @@ -14,8 +14,8 @@ In this section, we'll introduce the following concepts:
- icon

Metrics Explorer

 -

Learn how to use the Metrics Explorer to query your metrics.

+ icon

Metrics Search

 +

Learn how to use the Metrics Search to query your metrics.

diff --git a/docs/metrics/metrics-queries/map-charts.md b/docs/metrics/metrics-queries/map-charts.md index e836043d69..e71c79b9e0 100644 --- a/docs/metrics/metrics-queries/map-charts.md +++ b/docs/metrics/metrics-queries/map-charts.md @@ -13,7 +13,7 @@ A map chart visualizes metric query results by geographic location. To use a map chart your query results must include dimensions that provide latitude and longitude. We assume the geolocation dimensions are named _latitude_ and _longitude_. If the dimensions have different names, you can identify the correct fields in the **Chart** tab. -Map visualizations are supported in the Metrics Explorer and dashboard panel builder. +Map visualizations are supported in the Metrics Search and dashboard panel builder. For a Map visualization, you can choose either **Cluster** or **Heatmap** as the **Chart Type**. diff --git a/docs/metrics/metrics-queries/metric-query-autocomplete.md b/docs/metrics/metrics-queries/metric-query-autocomplete.md index 19becfbb8f..251322eff6 100644 --- a/docs/metrics/metrics-queries/metric-query-autocomplete.md +++ b/docs/metrics/metrics-queries/metric-query-autocomplete.md @@ -2,14 +2,14 @@ id: metric-query-autocomplete title: Metric Query Autocomplete sidebar_label: Metric Query Autocomplete -description: The Metrics Explorer provides an autocomplete dropdown dialog that offers suggestions to make query writing easier. +description: The Metrics Search provides an autocomplete dropdown dialog that offers suggestions to make query writing easier. --- -The [Metrics Explorer](/docs/metrics/metrics-queries/metrics-explorer) provides an autocomplete dropdown dialog that offers suggestions to make query writing easier. Autocomplete is supported in both Basic and Advanced mode. +The [Metrics Search](/docs/metrics/metrics-queries/metrics-explorer) provides an autocomplete dropdown dialog that offers suggestions to make query writing easier. Autocomplete is supported in both Basic and Advanced mode. ## Basic Mode autocomplete -In Basic Mode, the Metrics Explorer provides a query builder UI with +In Basic Mode, the Metrics Search provides a query builder UI with three fields for building a query. * **Metric** — When you click the field, a list of metrics is displayed. As you start to enter text, the metrics that match your entry appear. @@ -20,7 +20,7 @@ three fields for building a query. ## Advanced Mode autocomplete -In Advanced Mode, the Metrics Explorer allows you to enter a free-form metric query.  +In Advanced Mode, the Metrics Search allows you to enter a free-form metric query.  When you click in the query area, metric query autocomplete presents a list of Sumo Logic metadata fields, dimensions, and metatags. When you select an item from the list, autocomplete offers a list of values for the item. If you look at a metric query as a set of key-value pairs, autocomplete presents a list of keys, and when you choose one, it then presents a list of values. diff --git a/docs/metrics/metrics-queries/metrics-explorer.md b/docs/metrics/metrics-queries/metrics-explorer.md index ed6531af2d..3cee70990d 100644 --- a/docs/metrics/metrics-queries/metrics-explorer.md +++ b/docs/metrics/metrics-queries/metrics-explorer.md @@ -1,20 +1,20 @@ --- id: metrics-explorer -title: Metrics Explorer -sidebar_label: Metrics Explorer -description: Learn how to use the Metrics Explorer to query your metrics. +title: Metrics Search +sidebar_label: Metrics Search +description: Learn how to use the Metrics Search to query your metrics. --- import useBaseUrl from '@docusaurus/useBaseUrl'; -This page describes the Metrics Explorer UI and how to use it. +This page describes the Metrics Search UI and how to use it. ## About the UI -The Metrics Explorer appears when you open a new metrics tab. The page +The Metrics Search appears when you open a new metrics tab. The page has two modes: -* **Basic**. Basic Mode provides a query builder UI: you can construct metric queries by selecting metadata fields, dimensions, metrics, and operators from pull-down lists. This makes it easier to create your search scope and to apply operators to the metrics that are returned. You’ll still want to understand the functionality of [metric operators](/docs/metrics/metrics-operators), but the Metrics Explorer helps you by prompting you with a list of available operators, and after you choose an operator, the options or qualifiers that the operator supports. +* **Basic**. Basic Mode provides a query builder UI: you can construct metric queries by selecting metadata fields, dimensions, metrics, and operators from pull-down lists. This makes it easier to create your search scope and to apply operators to the metrics that are returned. You’ll still want to understand the functionality of [metric operators](/docs/metrics/metrics-operators), but the Metrics Search helps you by prompting you with a list of available operators, and after you choose an operator, the options or qualifiers that the operator supports. * **Advanced**. In Advanced Mode, you can enter free-form metric queries. You can enter your entire query manually, but Advanced Mode will also prompt you with pull-down lists of metadata fields, dimensions, metrics, and operators. If your query supports basic mode, you can freely move between basic and advanced mode to build and run your query. @@ -32,7 +32,7 @@ Example of queries that *will not* convert: When converted, the filters convert allowing you to select and modify, make different selections, remove filters, and add operators as you would normally in Basic Mode. -![switch-modes.png](/img/metrics/metric-explorer-switch-modes.png) +Metrics Search switch modes ## View Metrics Query History @@ -47,32 +47,32 @@ If the query editor mode cannot be adjusted, it is changed to advanced mode so t ## Create a metric query 1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to the **Home** screen and select **Metrics**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu select **Observability**, and then under **Metrics** select **Metrics Search**. You can also click the **Go To...** menu at the top of the screen and select **Metrics Search**. -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. +1. The Metrics Search 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) + Select metric 1. Click the **Filters** field. A list of metadata fields and metric dimensions appears. Scroll through the list, or begin typing to dynamically narrow the list. Click a field or dimension. In the screenshot below, we clicked the `_sourceCategory` metadata field. A dropdown list of values for the selected item appears. - ![filter-values.png](/img/metrics/filter-values.png) + Filter values 1. Scroll through the list, or begin typing to dynamically narrow the list. Click the desired value. The **Filter** field now contains the key-value pair you selected. You can click a filter setting to edit it. You can preface a filter value with and exclamation point (!) to NOT the value. 1. As desired, repeat the previous steps to add additional filters to the query.  1. When you are ready to run your query, click the run button: ![run-button.png](/img/metrics/run-button.png) 1. The metrics returned by your query appear in the **Time Series Table**. - ![results-in-table.png](/img/metrics/results-in-table.png) + Metrics search results in time series table 1. At any time, you can click **Chart** to see a visualization of the metrics. The chart area now displays a visualization of the selected metric. - ![query-visualization.png](/img/metrics/query-visualization.png) + Metrics search results in a chart 1. If you want to apply an operator, click **Add Operator** to the right of the **Filters** field. A list of metric operators appears. Note that when you hover over an operator, a tool tip displays the [Advanced Mode](#switch-betweenbasic-and-advancedmode) syntax and a description of the operator. - ![delta-hover.png](/img/metrics/delta-hover.png) + Add operator 1. Choose an operator from the list. If you choose an operator that supports or requires arguments, you are prompted to supply them. Click the run button to run the updated query. The chart area updates to show your query results with the operator applied. - ![results.png](/img/metrics/results-with-operator.png) + Results with operator 1. Apply additional operators to the query, as desired.  @@ -82,9 +82,9 @@ For some chart types, you can use the **Thresholds** tab in the **Display Settin **To set threshold values** -1. After you enter your query, in the **Chart** view, click the **Thresholds** icon in the right-side pane of icons.
thresholds-icon.png -2. Click the toggle in the **Thresholds** pane.
thresholds-icon.png -3. The **Thresholds** area updates to display default settings.
thresholds-default.png +1. After you enter your query, in the **Chart** view, click the **Thresholds** icon in the right-side pane of icons.
Thresholds icon.png +2. Click the toggle in the **Thresholds** pane.
thresholds-icon.png +3. The **Thresholds** area updates to display default settings.
Thresholds default settings 4. Configure the appropriate comparator and threshold values, based on your data and requirements. You can choose from the following comparators. * **greater than**. Any value greater than the value you specify will violate the threshold. * **greater than or equal to**. Any value greater than or equal to the value you specify will violate the threshold. @@ -95,8 +95,8 @@ For some chart types, you can use the **Thresholds** tab in the **Display Settin 5. Threshold bands appear on the chart. The red band shows the Critical threshold, the yellow band is Warning.
The chart type in the screenshot below is a line chart. For other chart types, the threshold visualization may vary. For example, in bar and column charts, the bars and columns are shaded yellow, red, and green in accordance with the thresholds defined.
The critical threshold has higher priority than the warning threshold. If the thresholds you define overlap, only the Critical shading (red) is applied to the overlapping area. fill-green.png -6. If you toggle the **Fill remaining area as green** option, the portion of the chart with no thresholds is shaded in green.
fill-green.png -7. If you toggle the **Highlight Violations** option, the horizontal threshold shading is removed. Instead you’ll see vertical red and yellow highlighting in the timelices where those thresholds were violated.
highlig-mode.png +6. If you toggle the **Fill remaining area as green** option, the portion of the chart with no thresholds is shaded in green.
Fill remaining area as green +7. If you toggle the **Highlight Violations** option, the horizontal threshold shading is removed. Instead you’ll see vertical red and yellow highlighting in the timelices where those thresholds were violated.
Highlight violations ## Add another metric query @@ -104,10 +104,10 @@ You can specify up to six queries in the same Metrics tab. To add an additional query: -1. Click **Add Query** to the right of the query builder area.
![add-query.png](/img/metrics/add-query.png) +1. Click **Add Query** to the right of the query builder area.
Add Query button 1. A new row, labeled #B, is added to the query builder area. 1. Follow the steps in [Create a metric query](/docs/metrics/metrics-queries/metrics-explorer/#create-a-metric-query) to build another query, and click the run icon to run the query. -1. Your visualization is updated to chart the additional query.
![two-queries.png](/img/metrics/two-queries.png) +1. Your visualization is updated to chart the additional query.
Two queries ## Join metric queries @@ -117,7 +117,7 @@ Metric query joins are only supported in Advanced Mode. The instructions below s You can perform basic math operations (+, -, \*, /) on two or more metrics queries, and use an additional query to apply an operation to the results of the other queries. For example, in the metric query tab below, the two queries return the incoming and outgoing network bytes. -![pre-join.png](/img/metrics/pre-join.png) +Before joining queries To join the queries, add a third query row, and then switch to advanced mode by choosing **Advanced Mode** from the three-dot kebab menu in that row. @@ -129,7 +129,7 @@ In Advanced mode, enter: It returns the difference between the incoming rate and the outgoing rate. In the visualization, display of the first two queries is toggled off, so only the join results are shown. -![joined-query.png](/img/metrics/joined-query.png) +After joining queries ## Hide a query @@ -146,7 +146,7 @@ You can hide a query so that it is not visualized in the chart. ## Convert query mode -The Metrics Explorer opens in Basic Mode by default. You can convert +The Metrics Search opens in Basic Mode by default. You can convert between Basic and Advanced anytime. 1. Select **Advanced Mode** from the more options menu. @@ -154,8 +154,6 @@ between Basic and Advanced anytime. 1. To convert to Basic, select **Basic Mode** from the more options menu. 1. The query converts with each filter loaded for editing or removing as needed. You can also add more operators. If the query cannot be converted, a message displays. -![advanced-basic.gif](/img/metrics/advanced-basic.gif) - ## Duplicate a metric query 1. Select **Duplicate Query** from the more options menu.
![duplicate-query.png](/img/metrics/duplicate-query.png) @@ -170,18 +168,18 @@ For information about tailoring charts, see modify a chart. To add a metric chart to a dashboard, click the **Add to Dashboard** button in the upper right corner of the Metric tab. -## Metrics Explorer FAQs +## Metrics Search FAQs -Below are some FAQs about the Metrics Explorer. +Below are some FAQs about the Metrics Search. -### What value does Metrics Explorer provide? +### What value does Metrics Search provide? -The Metrics Explorer gives you more visualization types and makes your metrics easier to  discover. Metrics Explorer provides the same visualizations available in Dashboards (New), from tables and category charts, to time series charts and honeycomb visualizations. The Metrics Explorer has richer and more comprehensive autocomplete support, providing suggestions for even very high cardinality queries. The structured query builder approach also makes the metrics experience friendlier to infrequent and inexperienced metrics users. +The Metrics Search gives you more visualization types and makes your metrics easier to  discover. Metrics Search provides the same visualizations available in Dashboards (New), from tables and category charts, to time series charts and honeycomb visualizations. The Metrics Search has richer and more comprehensive autocomplete support, providing suggestions for even very high cardinality queries. The structured query builder approach also makes the metrics experience friendlier to infrequent and inexperienced metrics users. -### Can I put logs and metrics on the same panel in the Metrics Explorer? +### Can I put logs and metrics on the same panel in the Metrics Search? Yes you can. The experience is consistent with the Dashboards (New) experience and has the same features. ### How does autocomplete when searching metrics work? -Autocomplete in the Metrics Explorer works by taking what you type and looking for tokenized prefixes that match your input. We tokenize based on spaces, underscores, hyphens, and a variety of other special characters. For example, assume you have a metric `metric_this_is`. If you enter `is` in the **Metric** field, Sumo Logic will suggest `metric_this_is` because `is` is a token in the metric. Similarly, entering `met` will result in the same recommendation because `met` is a prefix for the token `metric`. However, if you enter `ric`, we won't suggest `metric_this_is` because `ric` isn’t a prefix of any of the tokens in token in that metric name.  +Autocomplete in the Metrics Search works by taking what you type and looking for tokenized prefixes that match your input. We tokenize based on spaces, underscores, hyphens, and a variety of other special characters. For example, assume you have a metric `metric_this_is`. If you enter `is` in the **Metric** field, Sumo Logic will suggest `metric_this_is` because `is` is a token in the metric. Similarly, entering `met` will result in the same recommendation because `met` is a prefix for the token `metric`. However, if you enter `ric`, we won't suggest `metric_this_is` because `ric` isn’t a prefix of any of the tokens in token in that metric name.  diff --git a/docs/metrics/metrics-queries/query-comments.md b/docs/metrics/metrics-queries/query-comments.md index 56be84c6c8..a492d854ef 100644 --- a/docs/metrics/metrics-queries/query-comments.md +++ b/docs/metrics/metrics-queries/query-comments.md @@ -6,7 +6,7 @@ sidebar_label: Using Comments in Queries import useBaseUrl from '@docusaurus/useBaseUrl'; -In the Metrics Explorer, in [Advanced Mode](/docs/metrics/metrics-queries/metrics-explorer#switch-betweenbasic-and-advancedmode) you can add comments to a metrics query and comment out portions of the query by using comment formatting. +In the Metrics Search, in [Advanced Mode](/docs/metrics/metrics-queries/metrics-explorer#switch-betweenbasic-and-advancedmode) you can add comments to a metrics query and comment out portions of the query by using comment formatting. Comments are helpful for troubleshooting during query development, and also for other users who may use or edit your queries at a later date—comments you add will be visible in saved and shared queries. diff --git a/docs/observability/about.md b/docs/observability/about.md index 3b0c7716b3..29c217523f 100644 --- a/docs/observability/about.md +++ b/docs/observability/about.md @@ -60,5 +60,5 @@ The solution understands how the different datasets and services are connected, The solution also offers features and capabilities that support each step of the troubleshooting process. * **Monitor** your systems effectively with new and improved alerting and dashboarding capabilities. The Observability Solution includes rich pre-built content that you can leverage to quickly start monitoring specific services.  -* **Diagnose** issues quickly using features like the Entity Explorer, trace analytics, and the  Metrics Explorer.   +* **Diagnose** issues quickly using features like the Entity Explorer, trace analytics, and the  Metrics Search.   * **Troubleshoot** issues and find root causes through behavior insights and log search. diff --git a/docs/observability/diagnose-issues.md b/docs/observability/diagnose-issues.md index 3d612e1542..ca30be324d 100644 --- a/docs/observability/diagnose-issues.md +++ b/docs/observability/diagnose-issues.md @@ -19,9 +19,9 @@ Observe apps and microservices using [Transaction Tracing](/docs/apm/traces) and ![transaction-tracing.png](/img/observability/transaction-tracing.png) -## Analyze Key Metrics quickly using Metrics Explorer  +## Analyze Key Metrics quickly using Metrics Search  -Easily find and visualize your metrics with the [Re-vamped Metrics Explorer](../metrics/metrics-queries/metrics-explorer.md) that comes with a new structured query builder, and an extended range of visualizations for ad hoc analysis.  Mimicking the Dashboard workflow, you now have the same unified experience in the main metrics tab. +Easily find and visualize your metrics with the [Re-vamped Metrics Search](../metrics/metrics-queries/metrics-explorer.md) that comes with a new structured query builder, and an extended range of visualizations for ad hoc analysis.  Mimicking the Dashboard workflow, you now have the same unified experience in the main metrics tab. ![metrics-explorer.png](/img/observability/metrics-explorer.png) diff --git a/docs/observability/reliability-management-slo/create-slo.md b/docs/observability/reliability-management-slo/create-slo.md index d8356e3eb0..7148193a97 100644 --- a/docs/observability/reliability-management-slo/create-slo.md +++ b/docs/observability/reliability-management-slo/create-slo.md @@ -118,7 +118,7 @@ You can create SLOs directly from your Sumo Logic log search. This allows you to To create an SLO from the **Metrics** page: 1. [**Classic UI**](/docs/get-started/sumo-logic-ui-classic). Go to the **Home** screen and select **Metrics**.
[**New UI**](/docs/get-started/sumo-logic-ui). In the main Sumo Logic menu, select **Metrics > All Metric Searches**. You can also click the **Go To...** menu at the top of the screen and select **All Metric Searches**. -1. Under **Metrics Explorer**, select your desired **Metric** and **Filters**. Optionally, you can **Add Operator**.
metrics-slo.png +1. Under **Metrics Search**, select your desired **Metric** and **Filters**. Optionally, you can **Add Operator**.
metrics-slo.png 1. Click the three-dot kebab icon, then select **Create an SLO**. 1. Follow the instructions under [Create an SLO (General)](#create-an-slo-general). diff --git a/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source.md b/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source.md index fb4acb16d8..c3e130909d 100644 --- a/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source.md +++ b/docs/send-data/hosted-collectors/amazon-aws/aws-kinesis-firehose-metrics-source.md @@ -22,7 +22,7 @@ The diagram below illustrates the metrics collection pipeline. 1. AWS CloudWatch Metrics are streamed at a 1-minute resolution to the Metric Stream service. 1. The Metric Streams service delivers metrics to the Kinesis Data Firehose service. 1. The Kinesis Data Firehose service delivers the metrics to the AWS Kinesis Firehose for Metrics source for ingestion. The metrics are in the [OpenTelemetry](https://opentelemetry.io/) format. -1. You can query the metrics in the Sumo Logic Metrics Explorer. +1. You can query the metrics in the Sumo Logic Metrics Search. 1. Undelivered metrics are routed to a customer S3 bucket. How long it takes for metrics to be delivered to Sumo Logic depends on the buffering settings configured for the Firehose stream—such buffering is expressed in maximum payload size or maximum wait time, whichever is reached first. If these are set to the minimum values, which are 60 seconds and 1MB respectively, the expected latency is within 3 minutes, if the selected resources have active metric updates. diff --git a/static/img/dashboards/create-dashboard/metrics-explorer-add-to-dashboard.png b/static/img/dashboards/create-dashboard/metrics-explorer-add-to-dashboard.png index b8c3941241..9332561afe 100644 Binary files a/static/img/dashboards/create-dashboard/metrics-explorer-add-to-dashboard.png and b/static/img/dashboards/create-dashboard/metrics-explorer-add-to-dashboard.png differ diff --git a/static/img/metrics/add-query.png b/static/img/metrics/add-query.png index 8efe108877..01b3a4eb95 100644 Binary files a/static/img/metrics/add-query.png and b/static/img/metrics/add-query.png differ diff --git a/static/img/metrics/advanced-autocomplete.png b/static/img/metrics/advanced-autocomplete.png index c7e7a347f2..a872f80253 100644 Binary files a/static/img/metrics/advanced-autocomplete.png and b/static/img/metrics/advanced-autocomplete.png differ diff --git a/static/img/metrics/basic-autocomplete.png b/static/img/metrics/basic-autocomplete.png index 873fb0ba9f..bfb04c0672 100644 Binary files a/static/img/metrics/basic-autocomplete.png and b/static/img/metrics/basic-autocomplete.png differ diff --git a/static/img/metrics/click-in-metrici-area.png b/static/img/metrics/click-in-metrici-area.png index ebd61caa02..f1473e5d1b 100644 Binary files a/static/img/metrics/click-in-metrici-area.png and b/static/img/metrics/click-in-metrici-area.png differ diff --git a/static/img/metrics/cluster-map-one-metric.png b/static/img/metrics/cluster-map-one-metric.png index 317df5a8d3..7a0ba1534a 100644 Binary files a/static/img/metrics/cluster-map-one-metric.png and b/static/img/metrics/cluster-map-one-metric.png differ diff --git a/static/img/metrics/count-example.png b/static/img/metrics/count-example.png index e0790d6075..8ba8b1338a 100644 Binary files a/static/img/metrics/count-example.png and b/static/img/metrics/count-example.png differ diff --git a/static/img/metrics/disable-query-tips.png b/static/img/metrics/disable-query-tips.png index ef0bf1824a..4b0ec96085 100644 Binary files a/static/img/metrics/disable-query-tips.png and b/static/img/metrics/disable-query-tips.png differ diff --git a/static/img/metrics/fill-green.png b/static/img/metrics/fill-green.png index 08db16180a..00bf55436c 100644 Binary files a/static/img/metrics/fill-green.png and b/static/img/metrics/fill-green.png differ diff --git a/static/img/metrics/filter-values.png b/static/img/metrics/filter-values.png index 5da90c35b9..01477209db 100644 Binary files a/static/img/metrics/filter-values.png and b/static/img/metrics/filter-values.png differ diff --git a/static/img/metrics/highlight-mode.png b/static/img/metrics/highlight-mode.png index dfe705eaee..091f803a7e 100644 Binary files a/static/img/metrics/highlight-mode.png and b/static/img/metrics/highlight-mode.png differ diff --git a/static/img/metrics/hint1.png b/static/img/metrics/hint1.png index fc92d707bf..4e1df7d7f7 100644 Binary files a/static/img/metrics/hint1.png and b/static/img/metrics/hint1.png differ diff --git a/static/img/metrics/hint2.png b/static/img/metrics/hint2.png index 77195a7a65..8869c63972 100644 Binary files a/static/img/metrics/hint2.png and b/static/img/metrics/hint2.png differ diff --git a/static/img/metrics/hint3.png b/static/img/metrics/hint3.png index ac8790a560..f8dad5fb7e 100644 Binary files a/static/img/metrics/hint3.png and b/static/img/metrics/hint3.png differ diff --git a/static/img/metrics/join-results-without-along.png b/static/img/metrics/join-results-without-along.png index 44bc3472b2..41bf0df5d7 100644 Binary files a/static/img/metrics/join-results-without-along.png and b/static/img/metrics/join-results-without-along.png differ diff --git a/static/img/metrics/joined-query.png b/static/img/metrics/joined-query.png index 751703aaa5..9ca2dbd60d 100644 Binary files a/static/img/metrics/joined-query.png and b/static/img/metrics/joined-query.png differ diff --git a/static/img/metrics/map-option.png b/static/img/metrics/map-option.png index 85c73ab7fb..6cf6144e04 100644 Binary files a/static/img/metrics/map-option.png and b/static/img/metrics/map-option.png differ diff --git a/static/img/metrics/metric-explorer-switch-modes.png b/static/img/metrics/metric-explorer-switch-modes.png index 6b5ce1e3dc..6a615d1018 100644 Binary files a/static/img/metrics/metric-explorer-switch-modes.png and b/static/img/metrics/metric-explorer-switch-modes.png differ diff --git a/static/img/metrics/odd-join-results.png b/static/img/metrics/odd-join-results.png index 0fd71dc292..20b839e513 100644 Binary files a/static/img/metrics/odd-join-results.png and b/static/img/metrics/odd-join-results.png differ diff --git a/static/img/metrics/pre-join.png b/static/img/metrics/pre-join.png index 0e2626a6d8..18394085dc 100644 Binary files a/static/img/metrics/pre-join.png and b/static/img/metrics/pre-join.png differ diff --git a/static/img/metrics/quantization-warning.png b/static/img/metrics/quantization-warning.png index bfc0ff4119..9a7ebbcd54 100644 Binary files a/static/img/metrics/quantization-warning.png and b/static/img/metrics/quantization-warning.png differ diff --git a/static/img/metrics/query-visualization.png b/static/img/metrics/query-visualization.png index b86acbb143..b7a0ce67ed 100644 Binary files a/static/img/metrics/query-visualization.png and b/static/img/metrics/query-visualization.png differ diff --git a/static/img/metrics/results-in-table.png b/static/img/metrics/results-in-table.png index 961ce119f2..1a15e1a12c 100644 Binary files a/static/img/metrics/results-in-table.png and b/static/img/metrics/results-in-table.png differ diff --git a/static/img/metrics/results-with-operator.png b/static/img/metrics/results-with-operator.png index 5a45f45a13..7d3e7af86a 100644 Binary files a/static/img/metrics/results-with-operator.png and b/static/img/metrics/results-with-operator.png differ diff --git a/static/img/metrics/secondary-metric.png b/static/img/metrics/secondary-metric.png index 06a6992153..9a69064ad2 100644 Binary files a/static/img/metrics/secondary-metric.png and b/static/img/metrics/secondary-metric.png differ diff --git a/static/img/metrics/three-rows.png b/static/img/metrics/three-rows.png index 7ad155e1cf..e00531118d 100644 Binary files a/static/img/metrics/three-rows.png and b/static/img/metrics/three-rows.png differ diff --git a/static/img/metrics/thresholds-icon.png b/static/img/metrics/thresholds-icon.png index 04897c4fb3..1e82805d23 100644 Binary files a/static/img/metrics/thresholds-icon.png and b/static/img/metrics/thresholds-icon.png differ diff --git a/static/img/metrics/two-queries.png b/static/img/metrics/two-queries.png index a0911e237c..68fd7a07b0 100644 Binary files a/static/img/metrics/two-queries.png and b/static/img/metrics/two-queries.png differ diff --git a/static/img/observability/metrics-explorer.png b/static/img/observability/metrics-explorer.png index a8994a12fb..596f130e7e 100644 Binary files a/static/img/observability/metrics-explorer.png and b/static/img/observability/metrics-explorer.png differ diff --git a/static/img/observability/metrics-slo.png b/static/img/observability/metrics-slo.png index d49f34ed29..9ccef64ab4 100644 Binary files a/static/img/observability/metrics-slo.png and b/static/img/observability/metrics-slo.png differ