From d060fc92d37aaa06122aa234e8f9ae8f08caff9c Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Wed, 18 Sep 2024 12:53:17 -0700
Subject: [PATCH 01/16] docs: adds instructions for collecting and sending
 native histograms with otel collector

---
 .../mimir/send/native-histograms/_index.md    | 27 +++++++++++++++++++
 1 file changed, 27 insertions(+)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 79a40811958..67a9b045049 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -184,6 +184,33 @@ Use the latest version of [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_
    }
    ```
 
+## Collect and send native histograms with the OpenTelemetry Collector
+
+Use the OpenTelemetry SDK to collect and send native histograms with the OpenTelemetry Collector. You can instrument the collector using either Go or Java.
+
+### Instrument the OpenTelemetry Collector using Go
+
+Use the OpenTelemetry SDK version 1.17.0 or later.
+
+1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
+1. To aggregate a histogram instrument as an exponential histogram, include the following view:
+
+   ```
+   Aggregation: metric.AggregationBase2ExponentialHistogram{
+			MaxSize:  160,
+			MaxScale: 20,
+		}
+   ```
+
+   For more information, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go.
+
+### Instrument the OpenTelemetry Collector using Java
+
+Use the OpenTelemetry SDK version 1.35.0 or later.
+
+1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/java/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Java.
+1. To aggregate a histogram instrument as an exponential histogram, include the following view:
+
 ## Migrate from classic histograms
 
 To ease the migration process, you can keep the custom bucket definition of a classic histogram and add native histogram buckets at the same time.

From 83549c78756934b8682fa843df825643c1643509 Mon Sep 17 00:00:00 2001
From: Taylor C <41653732+tacole02@users.noreply.github.com>
Date: Thu, 19 Sep 2024 09:15:13 -0700
Subject: [PATCH 02/16] Update
 docs/sources/mimir/send/native-histograms/_index.md

Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
---
 docs/sources/mimir/send/native-histograms/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 67a9b045049..5876464d801 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -184,7 +184,7 @@ Use the latest version of [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_
    }
    ```
 
-## Collect and send native histograms with the OpenTelemetry Collector
+## Collect and send exponential histograms with the OpenTelemetry Collector
 
 Use the OpenTelemetry SDK to collect and send native histograms with the OpenTelemetry Collector. You can instrument the collector using either Go or Java.
 

From b92f185d26711b20363c3c6870a5b58cdf463e70 Mon Sep 17 00:00:00 2001
From: Taylor C <41653732+tacole02@users.noreply.github.com>
Date: Thu, 19 Sep 2024 09:15:41 -0700
Subject: [PATCH 03/16] Update
 docs/sources/mimir/send/native-histograms/_index.md

Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
---
 docs/sources/mimir/send/native-histograms/_index.md | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 5876464d801..4bd181035c0 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -186,7 +186,15 @@ Use the latest version of [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_
 
 ## Collect and send exponential histograms with the OpenTelemetry Collector
 
-Use the OpenTelemetry SDK to collect and send native histograms with the OpenTelemetry Collector. You can instrument the collector using either Go or Java.
+OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The only significant difference is that exponential histograms store the `min` and `max`  observation values explicitly, but native histograms don't, which means you need to estimate the minimum and maximum by using the 0.0 and 1.0 quantile respectively. 
+
+Use the OpenTelemetry Collector to collect and send exponential histograms. The Collector supports collecting exponential histograms or other compatible data formats (for example native histograms, DataDog sketches, etc) through its receivers. The Collector also supports sending the exponential histograms or compatible data formats such as native histograms through its exporters.
+
+Note: the availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
+
+Grafana Mimir can receive exponential histograms as is via the OTLP protocol or as Prometheus native histograms over the Prometheus remote write protocol.
+
+OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Multiple languages are supported, for the complete list see [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
 
 ### Instrument the OpenTelemetry Collector using Go
 

From 710ae7986e460658f38e7c9d1a63be45b060ab6f Mon Sep 17 00:00:00 2001
From: Taylor C <41653732+tacole02@users.noreply.github.com>
Date: Thu, 19 Sep 2024 09:15:58 -0700
Subject: [PATCH 04/16] Update
 docs/sources/mimir/send/native-histograms/_index.md

Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
---
 docs/sources/mimir/send/native-histograms/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 4bd181035c0..999f759f1ca 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -198,7 +198,7 @@ OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Mu
 
 ### Instrument the OpenTelemetry Collector using Go
 
-Use the OpenTelemetry SDK version 1.17.0 or later.
+Use the OpenTelemetry SDK version 1.17.0 or later for Go.
 
 1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
 1. To aggregate a histogram instrument as an exponential histogram, include the following view:

From b3a8d7fad9356973595bc2e0893a5b457207fe58 Mon Sep 17 00:00:00 2001
From: Taylor C <41653732+tacole02@users.noreply.github.com>
Date: Thu, 19 Sep 2024 09:16:52 -0700
Subject: [PATCH 05/16] Update
 docs/sources/mimir/send/native-histograms/_index.md

Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
---
 docs/sources/mimir/send/native-histograms/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 999f759f1ca..ca1c3d169bb 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -196,7 +196,7 @@ Grafana Mimir can receive exponential histograms as is via the OTLP protocol or
 
 OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Multiple languages are supported, for the complete list see [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
 
-### Instrument the OpenTelemetry Collector using Go
+### Instrument a Go application with the OpenTelemetry SDK
 
 Use the OpenTelemetry SDK version 1.17.0 or later for Go.
 

From cb17a5eb30baa053250d3a870c644f54c428b208 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Thu, 19 Sep 2024 12:14:00 -0700
Subject: [PATCH 06/16] docs: add new topic for exponential histograms

---
 .../mimir/send/native-histograms/_index.md    | 35 ------------------
 .../otel-exponential-histograms/_index.md     | 36 +++++++++++++++++++
 2 files changed, 36 insertions(+), 35 deletions(-)
 create mode 100644 docs/sources/mimir/send/otel-exponential-histograms/_index.md

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index ca1c3d169bb..79a40811958 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -184,41 +184,6 @@ Use the latest version of [Grafana Alloy](https://grafana.com/docs/alloy/<ALLOY_
    }
    ```
 
-## Collect and send exponential histograms with the OpenTelemetry Collector
-
-OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The only significant difference is that exponential histograms store the `min` and `max`  observation values explicitly, but native histograms don't, which means you need to estimate the minimum and maximum by using the 0.0 and 1.0 quantile respectively. 
-
-Use the OpenTelemetry Collector to collect and send exponential histograms. The Collector supports collecting exponential histograms or other compatible data formats (for example native histograms, DataDog sketches, etc) through its receivers. The Collector also supports sending the exponential histograms or compatible data formats such as native histograms through its exporters.
-
-Note: the availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
-
-Grafana Mimir can receive exponential histograms as is via the OTLP protocol or as Prometheus native histograms over the Prometheus remote write protocol.
-
-OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Multiple languages are supported, for the complete list see [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
-
-### Instrument a Go application with the OpenTelemetry SDK
-
-Use the OpenTelemetry SDK version 1.17.0 or later for Go.
-
-1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
-1. To aggregate a histogram instrument as an exponential histogram, include the following view:
-
-   ```
-   Aggregation: metric.AggregationBase2ExponentialHistogram{
-			MaxSize:  160,
-			MaxScale: 20,
-		}
-   ```
-
-   For more information, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go.
-
-### Instrument the OpenTelemetry Collector using Java
-
-Use the OpenTelemetry SDK version 1.35.0 or later.
-
-1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/java/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Java.
-1. To aggregate a histogram instrument as an exponential histogram, include the following view:
-
 ## Migrate from classic histograms
 
 To ease the migration process, you can keep the custom bucket definition of a classic histogram and add native histogram buckets at the same time.
diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
new file mode 100644
index 00000000000..2856050b366
--- /dev/null
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -0,0 +1,36 @@
+---
+description: Learn how to collect and send exponential histograms with the OpenTelemetry Collector
+menuTitle: OpenTelemetry exponential histograms
+title: Collect and send exponential histograms with the OpenTelemetry Collector
+weight: 100
+---
+
+# Collect and send exponential histograms with the OpenTelemetry Collector
+
+OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The only significant difference is that exponential histograms store the `min` and `max`  observation values explicitly, but native histograms don't, which means you need to estimate the minimum and maximum by using the 0.0 and 1.0 quantile respectively. 
+
+Use the OpenTelemetry Collector to collect and send exponential histograms. The Collector supports collecting exponential histograms or other compatible data formats (for example native histograms, DataDog sketches, etc) through its receivers. The Collector also supports sending the exponential histograms or compatible data formats such as native histograms through its exporters.
+
+Note: the availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
+
+Grafana Mimir can receive exponential histograms as is via the OTLP protocol or as Prometheus native histograms over the Prometheus remote write protocol.
+
+OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Multiple languages are supported, for the complete list see [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
+
+## Instrument a Go application with the OpenTelemetry SDK
+
+Use the OpenTelemetry SDK version 1.17.0 or later for Go.
+
+1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
+1. To aggregate a histogram instrument as an exponential histogram, include the following view:
+
+   ```
+   Aggregation: metric.AggregationBase2ExponentialHistogram{
+			MaxSize:  160,
+			MaxScale: 20,
+		}
+   ```
+
+   For more information, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go.
+
+## Migrate from classic histograms

From 7d7201c9d310d182226fa8037fd3d02161f0a1d6 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Thu, 19 Sep 2024 15:51:32 -0700
Subject: [PATCH 07/16] docs: otel histogram details

---
 .../otel-exponential-histograms/_index.md     | 31 ++++++++++++-------
 1 file changed, 20 insertions(+), 11 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 2856050b366..cdf14c0f6c1 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -1,27 +1,34 @@
 ---
 description: Learn how to collect and send exponential histograms with the OpenTelemetry Collector
+keywords:
+  - send metrics
+  - exponential histogram
+  - OpenTelemetry
+  - instrumentation
 menuTitle: OpenTelemetry exponential histograms
-title: Collect and send exponential histograms with the OpenTelemetry Collector
-weight: 100
+title: Send exponential histograms to Mimir
+weight: 200
 ---
 
-# Collect and send exponential histograms with the OpenTelemetry Collector
+# Send exponential histograms to Mimir
 
-OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The only significant difference is that exponential histograms store the `min` and `max`  observation values explicitly, but native histograms don't, which means you need to estimate the minimum and maximum by using the 0.0 and 1.0 quantile respectively. 
+You can collect and send exponential histograms to Mimir with the OpenTelemetry Collector. OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The key difference is that exponential histograms store the `min` and `max`  observation values explicitly, whereas native histograms don't. This means that for exponential histograms, you don't need to estimate these values using the 0.0 and 1.0 quantiles.
 
-Use the OpenTelemetry Collector to collect and send exponential histograms. The Collector supports collecting exponential histograms or other compatible data formats (for example native histograms, DataDog sketches, etc) through its receivers. The Collector also supports sending the exponential histograms or compatible data formats such as native histograms through its exporters.
+The OpenTelemetry Collector supports collecting exponential histograms and other compatible data formats, such as native histograms and DataDog sketches, through its receivers and sending them through its exporters.
 
-Note: the availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
+{{< admonition type="note" >}}
+The availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
+{{< /admonition >}}
 
-Grafana Mimir can receive exponential histograms as is via the OTLP protocol or as Prometheus native histograms over the Prometheus remote write protocol.
+You can use the OpenTelemetry (OTLP) protocol to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms.
 
-OpenTelemetry supports instrumenting applications with the OpenTelemetry SDK. Multiple languages are supported, for the complete list see [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
+The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/). 
 
-## Instrument a Go application with the OpenTelemetry SDK
+## Instrument an application with the OpenTelemetry SDK using Go
 
-Use the OpenTelemetry SDK version 1.17.0 or later for Go.
+Use the OpenTelemetry SDK version 1.17.0 or later.
 
-1. Set up the collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
+1. Set up the OpenTelemetry Collector to handle your metrics data. This includes setting up your resources, meter provider, meter, instruments, and views. Refer to [Metrics](https://opentelemetry.io/docs/languages/go/instrumentation/#metrics) in the OpenTelemetry SDK documentation for Go.
 1. To aggregate a histogram instrument as an exponential histogram, include the following view:
 
    ```
@@ -34,3 +41,5 @@ Use the OpenTelemetry SDK version 1.17.0 or later for Go.
    For more information, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go.
 
 ## Migrate from classic histograms
+
+## Bucket boundary calculation
\ No newline at end of file

From 3ba7ad2a3c49ae49c4c209ea15e16d959a6dcfff Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Thu, 19 Sep 2024 16:04:46 -0700
Subject: [PATCH 08/16] docs: otel histogram details

---
 .../mimir/send/otel-exponential-histograms/_index.md      | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index cdf14c0f6c1..318a2e353fb 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -6,21 +6,21 @@ keywords:
   - OpenTelemetry
   - instrumentation
 menuTitle: OpenTelemetry exponential histograms
-title: Send exponential histograms to Mimir
+title: Send OpenTelemetry exponential histograms to Mimir
 weight: 200
 ---
 
-# Send exponential histograms to Mimir
+# Send OpenTelemetry exponential histograms to Mimir
 
 You can collect and send exponential histograms to Mimir with the OpenTelemetry Collector. OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The key difference is that exponential histograms store the `min` and `max`  observation values explicitly, whereas native histograms don't. This means that for exponential histograms, you don't need to estimate these values using the 0.0 and 1.0 quantiles.
 
 The OpenTelemetry Collector supports collecting exponential histograms and other compatible data formats, such as native histograms and DataDog sketches, through its receivers and sending them through its exporters.
 
 {{< admonition type="note" >}}
-The availability of different receivers and exporters depends on your Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
+The availability of different receivers and exporters depends on your OpenTelemetry Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
 {{< /admonition >}}
 
-You can use the OpenTelemetry (OTLP) protocol to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms.
+You can use the OpenTelemetry (OTLP) protocol to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms. Refer to [Send native histograms to Mimir](https://grafana.com/docs/mimir/<MIMIR_VERSION>/send/native-histograms/).
 
 The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/). 
 

From 2ad64e568bf08c2c538556ea55d142dcef2536d7 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Mon, 23 Sep 2024 17:01:10 -0700
Subject: [PATCH 09/16] docs: add migration instructions for exp histograms

---
 .../mimir/send/native-histograms/_index.md    |  2 +-
 .../otel-exponential-histograms/_index.md     | 73 ++++++++++++++++++-
 2 files changed, 72 insertions(+), 3 deletions(-)

diff --git a/docs/sources/mimir/send/native-histograms/_index.md b/docs/sources/mimir/send/native-histograms/_index.md
index 79a40811958..12543d4f442 100644
--- a/docs/sources/mimir/send/native-histograms/_index.md
+++ b/docs/sources/mimir/send/native-histograms/_index.md
@@ -224,7 +224,7 @@ To ease the migration process, you can keep the custom bucket definition of a cl
 1. Send native histograms to remote write, along with the existing classic histograms.
 1. Modify dashboards to use the native histogram metrics. Refer to [Visualize native histograms](https://grafana.com/docs/mimir/<MIMIR_VERSION>/visualize/native-histograms/) for more information.
 
-   Use one of the following strategies to update dashbaords.
+   Use one of the following strategies to update dashboards.
 
    - (Recommended) Add new dashboards with the new native histogram queries. This solution requires looking at different dashboards for data before and after the migration, until data before the migration is removed due to passing its retention time. You can publish the new dashboard when sufficient time has passed to serve users with the new data.
    - Add a dashboard variable to your dashboard to enable switching between classic histograms and native histograms. There isn't support for selectively enabling and disabling queries in Grafana ([issue 79848](https://github.com/grafana/grafana/issues/79848)). As a workaround, add the dashboard variable `latency_metrics`, for example, and assign it a value of either `-1` or `1`. Then, add the following two queries to the panel:
diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 318a2e353fb..702221e5427 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -38,8 +38,77 @@ Use the OpenTelemetry SDK version 1.17.0 or later.
 		}
    ```
 
-   For more information, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go.
+   For more information about views, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go. For information about view configuration parameters, refer to [Base2 Exponential Bucket Histogram Aggregation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#base2-exponential-bucket-histogram-aggregation) in the OpenTelemetry Metrics SDK on GitHub.
 
-## Migrate from classic histograms
+## Migrate from explicit bucket histograms
+
+To ease the migration process, you can keep the custom bucket definition of an explicit bucket histogram and add a view for the exponential histogram.
+
+1. Start with an existing histogram that uses explicit buckets.
+1. Create a view for the exponential histogram. Assign this view a unique name and include the exponential aggregation. This creates a metric with the assigned name and exponential buckets.
+
+  The following example shows how to create a metric called `request_latency_exp` that uses exponential buckets.
+
+  ```
+  v := sdkmetric.NewView(sdkmetric.Instrument{
+		Name: "request_latency",
+		Kind: sdkmetric.InstrumentKindHistogram,
+	}, sdkmetric.Stream{
+		Name: "request_latency_exp",
+		Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
+		//Aggregation: sdkmetric.DefaultAggregationSelector(sdkmetric.InstrumentKindHistogram),
+	})
+  ```
+
+  For more information about creating a view, refer to [Views](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.
+1. Modify dashboards to use the exponential histogram metrics. Refer to [Visualize native histograms](https://grafana.com/docs/mimir/<MIMIR_VERSION>/visualize/native-histograms/) for more information.
+
+   Use one of the following strategies to update dashboards.
+
+   - (Recommended) Add new dashboards with the new exponential histogram queries. This solution requires looking at different dashboards for data before and after the migration, until data before the migration is removed due to passing its retention time. You can publish the new dashboard when sufficient time has passed to serve users with the new data.
+   - Add a dashboard variable to your dashboard to enable switching between explicit bucket histograms and exponential histograms. There isn't support for selectively enabling and disabling queries in Grafana ([issue 79848](https://github.com/grafana/grafana/issues/79848)). As a workaround, add the dashboard variable `latency_metrics`, for example, and assign it a value of either `-1` or `1`. Then, add the following two queries to the panel:
+
+     ```
+     <classic_query> < ($latency_metrics * +Inf)
+     ```
+
+     ```
+     <native_query> < ($latency_metrics * -Inf)
+     ```
+
+     Where `classic_query` is the original query and `native_query` is the same query using exponential histogram query syntax. This technique is employed in Mimir's dashboards. For an example, refer to the [Overview dashboard](https://github.com/grafana/mimir/blob/main/operations/mimir-mixin-compiled/dashboards/mimir-overview.json) in the Mimir repository.
+
+     This solution allows users to switch between the explicit bucket histogram and the exponential histogram without going to a different dashboard.
+
+   - Replace the existing explicit bucket queries with modified queries. For example, replace:
+
+     ```
+     <explicit_bucket_query>
+     ```
+
+     with
+
+     ```
+     <exponential_query> or <explicit_bucket_query>
+     ```
+
+     Where `explicit_bucket_query` is the original query and `exponential_query` is the same query using exponential histogram query syntax.
+
+     {{< admonition type="warning" >}}
+     Using the PromQL operator `or` can lead to unexpected results. For example, if a query uses a range of seven days, such as `sum(rate(http_request_duration_seconds[7d]))`, then this query returns a value as soon as there are two exponential histograms samples present before the end time specified in the query. In this case, the seven day rate is calculated from a couple of minutes, rather than seven days, worth of data. This results in an inaccuracy in the graph around the time you started scraping exponential histograms.
+     {{< /admonition >}}
+
+1. Start adding new recording rules and alerts to use exponential histograms. Don't remove the old recording rules and alerts at this time.
+1. It's important to keep scraping both explicit bucket and exponential histograms for at least the period of the longest range in your recording rules and alerts, plus one day. This is the minimum amount of time, but it's recommended to keep scraping both data types until you can verify the new rules and alerts.
+
+   For example, if you have an alert that calculates the rate of requests, such as `sum(rate(http_request_duration_seconds[7d]))`, this query looks at the data from the last seven days plus the Prometheus [lookback period](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness). When you start sending exponential histograms, the data isn't there for the entire seven days, and therefore, the results might be unreliable for alerting.
+
+1. After configuring exponential histogram collection, choose one of the following ways to stop collecting explicit bucket histograms.
+
+   - Remove the custom bucket definition, `Buckets`/`classicUpperBounds`, from the instrumentation. In Java, also use the `nativeOnly()` option. Refer to the examples in [Instrument application with Prometheus client libraries](#instrument-application-with-prometheus-client-libraries).
+   - Drop the explicit bucket histogram series with [Prometheus relabeling](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) or [Grafana Alloy prometheus.relabel](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/prometheus/prometheus.relabel) at the time of scraping.
+   - Stop scraping the explicit bucket histogram version of metrics. This option applies to all metrics of a scrape target.
+
+1. Clean up recording rules and alerts by deleting the explicit bucket histogram version of the rule or alert.
 
 ## Bucket boundary calculation
\ No newline at end of file

From e52640d8853002f95d574b18ce7d3854fbc44711 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Mon, 23 Sep 2024 17:30:25 -0700
Subject: [PATCH 10/16] add bucket boundary calculation info for exp histograms

---
 .../mimir/send/otel-exponential-histograms/_index.md   | 10 +++++++++-
 1 file changed, 9 insertions(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 702221e5427..10f8ad68e28 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -111,4 +111,12 @@ To ease the migration process, you can keep the custom bucket definition of an e
 
 1. Clean up recording rules and alerts by deleting the explicit bucket histogram version of the rule or alert.
 
-## Bucket boundary calculation
\ No newline at end of file
+## Bucket boundary calculation
+
+Bucket boundaries for exponential histograms are calculated similarly to those for native histograms. The only difference is that for exponential histograms, bucket offsets are shifted by one.
+
+For example:
+
+
+
+For more information, refer to [bucket boundary calculation](https://grafana.com/docs/mimir/next/send/native-histograms/#bucket-boundary-calculation) in the documentation for native histograms.

From 040368d4e8a8907f2efed0762d64feaba5033286 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gy=C3=B6rgy=20Krajcsovits?= <gyorgy.krajcsovits@grafana.com>
Date: Tue, 24 Sep 2024 10:08:33 +0200
Subject: [PATCH 11/16] Add otel bucket definition and remove stray line
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
---
 .../sources/mimir/send/otel-exponential-histograms/_index.md | 5 +++--
 .../send/otel-exponential-histograms/otel-pos-bucket-def.svg | 2 ++
 2 files changed, 5 insertions(+), 2 deletions(-)
 create mode 100644 docs/sources/mimir/send/otel-exponential-histograms/otel-pos-bucket-def.svg

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 10f8ad68e28..8e44a39cfd6 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -56,7 +56,6 @@ To ease the migration process, you can keep the custom bucket definition of an e
 	}, sdkmetric.Stream{
 		Name: "request_latency_exp",
 		Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
-		//Aggregation: sdkmetric.DefaultAggregationSelector(sdkmetric.InstrumentKindHistogram),
 	})
   ```
 
@@ -115,8 +114,10 @@ To ease the migration process, you can keep the custom bucket definition of an e
 
 Bucket boundaries for exponential histograms are calculated similarly to those for native histograms. The only difference is that for exponential histograms, bucket offsets are shifted by one.
 
-For example:
+Thus:
 
+<!--- LaTeX equation source: {\left( 2^{2^{-schema}} \right)}^{index} < v \leq {\left( 2^{2^{-schema}}\right)}^{index+1} -->
 
+![Positive bucket definition](otel-pos-bucket-def.svg)
 
 For more information, refer to [bucket boundary calculation](https://grafana.com/docs/mimir/next/send/native-histograms/#bucket-boundary-calculation) in the documentation for native histograms.
diff --git a/docs/sources/mimir/send/otel-exponential-histograms/otel-pos-bucket-def.svg b/docs/sources/mimir/send/otel-exponential-histograms/otel-pos-bucket-def.svg
new file mode 100644
index 00000000000..0506bb3306d
--- /dev/null
+++ b/docs/sources/mimir/send/otel-exponential-histograms/otel-pos-bucket-def.svg
@@ -0,0 +1,2 @@
+<?xml version="1.0" encoding="UTF-8" standalone="no" ?>
+<svg xmlns="http://www.w3.org/2000/svg" width="294.464px" height="36.504px" viewBox="0 -1367.3 16269.1 2016.8" xmlns:xlink="http://www.w3.org/1999/xlink" aria-hidden="true"><defs><path id="MJX-7-TEX-LO-28" d="M180 96T180 250T205 541T266 770T353 944T444 1069T527 1150H555Q561 1144 561 1141Q561 1137 545 1120T504 1072T447 995T386 878T330 721T288 513T272 251Q272 133 280 56Q293 -87 326 -209T399 -405T475 -531T536 -609T561 -640Q561 -643 555 -649H527Q483 -612 443 -568T353 -443T266 -270T205 -41Z"></path><path id="MJX-7-TEX-N-32" d="M109 429Q82 429 66 447T50 491Q50 562 103 614T235 666Q326 666 387 610T449 465Q449 422 429 383T381 315T301 241Q265 210 201 149L142 93L218 92Q375 92 385 97Q392 99 409 186V189H449V186Q448 183 436 95T421 3V0H50V19V31Q50 38 56 46T86 81Q115 113 136 137Q145 147 170 174T204 211T233 244T261 278T284 308T305 340T320 369T333 401T340 431T343 464Q343 527 309 573T212 619Q179 619 154 602T119 569T109 550Q109 549 114 549Q132 549 151 535T170 489Q170 464 154 447T109 429Z"></path><path id="MJX-7-TEX-N-2212" d="M84 237T84 250T98 270H679Q694 262 694 250T679 230H98Q84 237 84 250Z"></path><path id="MJX-7-TEX-I-1D460" d="M131 289Q131 321 147 354T203 415T300 442Q362 442 390 415T419 355Q419 323 402 308T364 292Q351 292 340 300T328 326Q328 342 337 354T354 372T367 378Q368 378 368 379Q368 382 361 388T336 399T297 405Q249 405 227 379T204 326Q204 301 223 291T278 274T330 259Q396 230 396 163Q396 135 385 107T352 51T289 7T195 -10Q118 -10 86 19T53 87Q53 126 74 143T118 160Q133 160 146 151T160 120Q160 94 142 76T111 58Q109 57 108 57T107 55Q108 52 115 47T146 34T201 27Q237 27 263 38T301 66T318 97T323 122Q323 150 302 164T254 181T195 196T148 231Q131 256 131 289Z"></path><path id="MJX-7-TEX-I-1D450" d="M34 159Q34 268 120 355T306 442Q362 442 394 418T427 355Q427 326 408 306T360 285Q341 285 330 295T319 325T330 359T352 380T366 386H367Q367 388 361 392T340 400T306 404Q276 404 249 390Q228 381 206 359Q162 315 142 235T121 119Q121 73 147 50Q169 26 205 26H209Q321 26 394 111Q403 121 406 121Q410 121 419 112T429 98T420 83T391 55T346 25T282 0T202 -11Q127 -11 81 37T34 159Z"></path><path id="MJX-7-TEX-I-210E" d="M137 683Q138 683 209 688T282 694Q294 694 294 685Q294 674 258 534Q220 386 220 383Q220 381 227 388Q288 442 357 442Q411 442 444 415T478 336Q478 285 440 178T402 50Q403 36 407 31T422 26Q450 26 474 56T513 138Q516 149 519 151T535 153Q555 153 555 145Q555 144 551 130Q535 71 500 33Q466 -10 419 -10H414Q367 -10 346 17T325 74Q325 90 361 192T398 345Q398 404 354 404H349Q266 404 205 306L198 293L164 158Q132 28 127 16Q114 -11 83 -11Q69 -11 59 -2T48 16Q48 30 121 320L195 616Q195 629 188 632T149 637H128Q122 643 122 645T124 664Q129 683 137 683Z"></path><path id="MJX-7-TEX-I-1D452" d="M39 168Q39 225 58 272T107 350T174 402T244 433T307 442H310Q355 442 388 420T421 355Q421 265 310 237Q261 224 176 223Q139 223 138 221Q138 219 132 186T125 128Q125 81 146 54T209 26T302 45T394 111Q403 121 406 121Q410 121 419 112T429 98T420 82T390 55T344 24T281 -1T205 -11Q126 -11 83 42T39 168ZM373 353Q367 405 305 405Q272 405 244 391T199 357T170 316T154 280T149 261Q149 260 169 260Q282 260 327 284T373 353Z"></path><path id="MJX-7-TEX-I-1D45A" d="M21 287Q22 293 24 303T36 341T56 388T88 425T132 442T175 435T205 417T221 395T229 376L231 369Q231 367 232 367L243 378Q303 442 384 442Q401 442 415 440T441 433T460 423T475 411T485 398T493 385T497 373T500 364T502 357L510 367Q573 442 659 442Q713 442 746 415T780 336Q780 285 742 178T704 50Q705 36 709 31T724 26Q752 26 776 56T815 138Q818 149 821 151T837 153Q857 153 857 145Q857 144 853 130Q845 101 831 73T785 17T716 -10Q669 -10 648 17T627 73Q627 92 663 193T700 345Q700 404 656 404H651Q565 404 506 303L499 291L466 157Q433 26 428 16Q415 -11 385 -11Q372 -11 364 -4T353 8T350 18Q350 29 384 161L420 307Q423 322 423 345Q423 404 379 404H374Q288 404 229 303L222 291L189 157Q156 26 151 16Q138 -11 108 -11Q95 -11 87 -5T76 7T74 17Q74 30 112 181Q151 335 151 342Q154 357 154 369Q154 405 129 405Q107 405 92 377T69 316T57 280Q55 278 41 278H27Q21 284 21 287Z"></path><path id="MJX-7-TEX-I-1D44E" d="M33 157Q33 258 109 349T280 441Q331 441 370 392Q386 422 416 422Q429 422 439 414T449 394Q449 381 412 234T374 68Q374 43 381 35T402 26Q411 27 422 35Q443 55 463 131Q469 151 473 152Q475 153 483 153H487Q506 153 506 144Q506 138 501 117T481 63T449 13Q436 0 417 -8Q409 -10 393 -10Q359 -10 336 5T306 36L300 51Q299 52 296 50Q294 48 292 46Q233 -10 172 -10Q117 -10 75 30T33 157ZM351 328Q351 334 346 350T323 385T277 405Q242 405 210 374T160 293Q131 214 119 129Q119 126 119 118T118 106Q118 61 136 44T179 26Q217 26 254 59T298 110Q300 114 325 217T351 328Z"></path><path id="MJX-7-TEX-LO-29" d="M35 1138Q35 1150 51 1150H56H69Q113 1113 153 1069T243 944T330 771T391 541T416 250T391 -40T330 -270T243 -443T152 -568T69 -649H56Q43 -649 39 -647T35 -637Q65 -607 110 -548Q283 -316 316 56Q324 133 324 251Q324 368 316 445Q278 877 48 1123Q36 1137 35 1138Z"></path><path id="MJX-7-TEX-I-1D456" d="M184 600Q184 624 203 642T247 661Q265 661 277 649T290 619Q290 596 270 577T226 557Q211 557 198 567T184 600ZM21 287Q21 295 30 318T54 369T98 420T158 442Q197 442 223 419T250 357Q250 340 236 301T196 196T154 83Q149 61 149 51Q149 26 166 26Q175 26 185 29T208 43T235 78T260 137Q263 149 265 151T282 153Q302 153 302 143Q302 135 293 112T268 61T223 11T161 -11Q129 -11 102 10T74 74Q74 91 79 106T122 220Q160 321 166 341T173 380Q173 404 156 404H154Q124 404 99 371T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Z"></path><path id="MJX-7-TEX-I-1D45B" d="M21 287Q22 293 24 303T36 341T56 388T89 425T135 442Q171 442 195 424T225 390T231 369Q231 367 232 367L243 378Q304 442 382 442Q436 442 469 415T503 336T465 179T427 52Q427 26 444 26Q450 26 453 27Q482 32 505 65T540 145Q542 153 560 153Q580 153 580 145Q580 144 576 130Q568 101 554 73T508 17T439 -10Q392 -10 371 17T350 73Q350 92 386 193T423 345Q423 404 379 404H374Q288 404 229 303L222 291L189 157Q156 26 151 16Q138 -11 108 -11Q95 -11 87 -5T76 7T74 17Q74 30 112 180T152 343Q153 348 153 366Q153 405 129 405Q91 405 66 305Q60 285 60 284Q58 278 41 278H27Q21 284 21 287Z"></path><path id="MJX-7-TEX-I-1D451" d="M366 683Q367 683 438 688T511 694Q523 694 523 686Q523 679 450 384T375 83T374 68Q374 26 402 26Q411 27 422 35Q443 55 463 131Q469 151 473 152Q475 153 483 153H487H491Q506 153 506 145Q506 140 503 129Q490 79 473 48T445 8T417 -8Q409 -10 393 -10Q359 -10 336 5T306 36L300 51Q299 52 296 50Q294 48 292 46Q233 -10 172 -10Q117 -10 75 30T33 157Q33 205 53 255T101 341Q148 398 195 420T280 442Q336 442 364 400Q369 394 369 396Q370 400 396 505T424 616Q424 629 417 632T378 637H357Q351 643 351 645T353 664Q358 683 366 683ZM352 326Q329 405 277 405Q242 405 210 374T160 293Q131 214 119 129Q119 126 119 118T118 106Q118 61 136 44T179 26Q233 26 290 98L298 109L352 326Z"></path><path id="MJX-7-TEX-I-1D465" d="M52 289Q59 331 106 386T222 442Q257 442 286 424T329 379Q371 442 430 442Q467 442 494 420T522 361Q522 332 508 314T481 292T458 288Q439 288 427 299T415 328Q415 374 465 391Q454 404 425 404Q412 404 406 402Q368 386 350 336Q290 115 290 78Q290 50 306 38T341 26Q378 26 414 59T463 140Q466 150 469 151T485 153H489Q504 153 504 145Q504 144 502 134Q486 77 440 33T333 -11Q263 -11 227 52Q186 -10 133 -10H127Q78 -10 57 16T35 71Q35 103 54 123T99 143Q142 143 142 101Q142 81 130 66T107 46T94 41L91 40Q91 39 97 36T113 29T132 26Q168 26 194 71Q203 87 217 139T245 247T261 313Q266 340 266 352Q266 380 251 392T217 404Q177 404 142 372T93 290Q91 281 88 280T72 278H58Q52 284 52 289Z"></path><path id="MJX-7-TEX-N-3C" d="M694 -11T694 -19T688 -33T678 -40Q671 -40 524 29T234 166L90 235Q83 240 83 250Q83 261 91 266Q664 540 678 540Q681 540 687 534T694 519T687 505Q686 504 417 376L151 250L417 124Q686 -4 687 -5Q694 -11 694 -19Z"></path><path id="MJX-7-TEX-I-1D463" d="M173 380Q173 405 154 405Q130 405 104 376T61 287Q60 286 59 284T58 281T56 279T53 278T49 278T41 278H27Q21 284 21 287Q21 294 29 316T53 368T97 419T160 441Q202 441 225 417T249 361Q249 344 246 335Q246 329 231 291T200 202T182 113Q182 86 187 69Q200 26 250 26Q287 26 319 60T369 139T398 222T409 277Q409 300 401 317T383 343T365 361T357 383Q357 405 376 424T417 443Q436 443 451 425T467 367Q467 340 455 284T418 159T347 40T241 -11Q177 -11 139 22Q102 54 102 117Q102 148 110 181T151 298Q173 362 173 380Z"></path><path id="MJX-7-TEX-N-2264" d="M674 636Q682 636 688 630T694 615T687 601Q686 600 417 472L151 346L399 228Q687 92 691 87Q694 81 694 76Q694 58 676 56H670L382 192Q92 329 90 331Q83 336 83 348Q84 359 96 365Q104 369 382 500T665 634Q669 636 674 636ZM84 -118Q84 -108 99 -98H678Q694 -104 694 -118Q694 -130 679 -138H98Q84 -131 84 -118Z"></path><path id="MJX-7-TEX-N-2B" d="M56 237T56 250T70 270H369V420L370 570Q380 583 389 583Q402 583 409 568V270H707Q722 262 722 250T707 230H409V-68Q401 -82 391 -82H389H387Q375 -82 369 -68V230H70Q56 237 56 250Z"></path><path id="MJX-7-TEX-N-31" d="M213 578L200 573Q186 568 160 563T102 556H83V602H102Q149 604 189 617T245 641T273 663Q275 666 285 666Q294 666 302 660V361L303 61Q310 54 315 52T339 48T401 46H427V0H416Q395 3 257 3Q121 3 100 0H88V46H114Q136 46 152 46T177 47T193 50T201 52T207 57T213 61V578Z"></path></defs><g stroke="#000000" fill="#000000" stroke-width="0" transform="scale(1,-1)"><g data-mml-node="math"><g data-mml-node="msup"><g data-mml-node="TeXAtom" data-mjx-texclass="ORD"><g data-mml-node="mrow"><g data-mml-node="mo" transform="translate(0 -0.5)"><use data-c="28" xlink:href="#MJX-7-TEX-LO-28"></use></g><g data-mml-node="msup" transform="translate(597,0)"><g data-mml-node="mn"><use data-c="32" xlink:href="#MJX-7-TEX-N-32"></use></g><g data-mml-node="TeXAtom" transform="translate(533,413) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="msup"><g data-mml-node="mn"><use data-c="32" xlink:href="#MJX-7-TEX-N-32"></use></g><g data-mml-node="TeXAtom" transform="translate(533,363) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="mo"><use data-c="2212" xlink:href="#MJX-7-TEX-N-2212"></use></g><g data-mml-node="mi" transform="translate(778,0)"><use data-c="1D460" xlink:href="#MJX-7-TEX-I-1D460"></use></g><g data-mml-node="mi" transform="translate(1247,0)"><use data-c="1D450" xlink:href="#MJX-7-TEX-I-1D450"></use></g><g data-mml-node="mi" transform="translate(1680,0)"><use data-c="210E" xlink:href="#MJX-7-TEX-I-210E"></use></g><g data-mml-node="mi" transform="translate(2256,0)"><use data-c="1D452" xlink:href="#MJX-7-TEX-I-1D452"></use></g><g data-mml-node="mi" transform="translate(2722,0)"><use data-c="1D45A" xlink:href="#MJX-7-TEX-I-1D45A"></use></g><g data-mml-node="mi" transform="translate(3600,0)"><use data-c="1D44E" xlink:href="#MJX-7-TEX-I-1D44E"></use></g></g></g></g></g><g data-mml-node="mo" transform="translate(3656.7,0) translate(0 -0.5)"><use data-c="29" xlink:href="#MJX-7-TEX-LO-29"></use></g></g></g><g data-mml-node="TeXAtom" transform="translate(4286.7,876.6) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="mi"><use data-c="1D456" xlink:href="#MJX-7-TEX-I-1D456"></use></g><g data-mml-node="mi" transform="translate(345,0)"><use data-c="1D45B" xlink:href="#MJX-7-TEX-I-1D45B"></use></g><g data-mml-node="mi" transform="translate(945,0)"><use data-c="1D451" xlink:href="#MJX-7-TEX-I-1D451"></use></g><g data-mml-node="mi" transform="translate(1465,0)"><use data-c="1D452" xlink:href="#MJX-7-TEX-I-1D452"></use></g><g data-mml-node="mi" transform="translate(1931,0)"><use data-c="1D465" xlink:href="#MJX-7-TEX-I-1D465"></use></g></g></g><g data-mml-node="mo" transform="translate(6384.4,0)"><use data-c="3C" xlink:href="#MJX-7-TEX-N-3C"></use></g><g data-mml-node="mi" transform="translate(7440.2,0)"><use data-c="1D463" xlink:href="#MJX-7-TEX-I-1D463"></use></g><g data-mml-node="mo" transform="translate(8203,0)"><use data-c="2264" xlink:href="#MJX-7-TEX-N-2264"></use></g><g data-mml-node="msup" transform="translate(9258.7,0)"><g data-mml-node="TeXAtom" data-mjx-texclass="ORD"><g data-mml-node="mrow"><g data-mml-node="mo" transform="translate(0 -0.5)"><use data-c="28" xlink:href="#MJX-7-TEX-LO-28"></use></g><g data-mml-node="msup" transform="translate(597,0)"><g data-mml-node="mn"><use data-c="32" xlink:href="#MJX-7-TEX-N-32"></use></g><g data-mml-node="TeXAtom" transform="translate(533,413) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="msup"><g data-mml-node="mn"><use data-c="32" xlink:href="#MJX-7-TEX-N-32"></use></g><g data-mml-node="TeXAtom" transform="translate(533,363) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="mo"><use data-c="2212" xlink:href="#MJX-7-TEX-N-2212"></use></g><g data-mml-node="mi" transform="translate(778,0)"><use data-c="1D460" xlink:href="#MJX-7-TEX-I-1D460"></use></g><g data-mml-node="mi" transform="translate(1247,0)"><use data-c="1D450" xlink:href="#MJX-7-TEX-I-1D450"></use></g><g data-mml-node="mi" transform="translate(1680,0)"><use data-c="210E" xlink:href="#MJX-7-TEX-I-210E"></use></g><g data-mml-node="mi" transform="translate(2256,0)"><use data-c="1D452" xlink:href="#MJX-7-TEX-I-1D452"></use></g><g data-mml-node="mi" transform="translate(2722,0)"><use data-c="1D45A" xlink:href="#MJX-7-TEX-I-1D45A"></use></g><g data-mml-node="mi" transform="translate(3600,0)"><use data-c="1D44E" xlink:href="#MJX-7-TEX-I-1D44E"></use></g></g></g></g></g><g data-mml-node="mo" transform="translate(3656.7,0) translate(0 -0.5)"><use data-c="29" xlink:href="#MJX-7-TEX-LO-29"></use></g></g></g><g data-mml-node="TeXAtom" transform="translate(4286.7,876.6) scale(0.707)" data-mjx-texclass="ORD"><g data-mml-node="mi"><use data-c="1D456" xlink:href="#MJX-7-TEX-I-1D456"></use></g><g data-mml-node="mi" transform="translate(345,0)"><use data-c="1D45B" xlink:href="#MJX-7-TEX-I-1D45B"></use></g><g data-mml-node="mi" transform="translate(945,0)"><use data-c="1D451" xlink:href="#MJX-7-TEX-I-1D451"></use></g><g data-mml-node="mi" transform="translate(1465,0)"><use data-c="1D452" xlink:href="#MJX-7-TEX-I-1D452"></use></g><g data-mml-node="mi" transform="translate(1931,0)"><use data-c="1D465" xlink:href="#MJX-7-TEX-I-1D465"></use></g><g data-mml-node="mo" transform="translate(2503,0)"><use data-c="2B" xlink:href="#MJX-7-TEX-N-2B"></use></g><g data-mml-node="mn" transform="translate(3281,0)"><use data-c="31" xlink:href="#MJX-7-TEX-N-31"></use></g></g></g></g></g></svg>
\ No newline at end of file

From 59c3f35326be4ee650c79fefba1d7c239e2ad73c Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Gy=C3=B6rgy=20Krajcsovits?= <gyorgy.krajcsovits@grafana.com>
Date: Tue, 24 Sep 2024 10:13:03 +0200
Subject: [PATCH 12/16] ran make docs
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Signed-off-by: György Krajcsovits <gyorgy.krajcsovits@grafana.com>
---
 .../otel-exponential-histograms/_index.md     | 21 ++++++++++---------
 1 file changed, 11 insertions(+), 10 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 8e44a39cfd6..a37f3a1beae 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -12,7 +12,7 @@ weight: 200
 
 # Send OpenTelemetry exponential histograms to Mimir
 
-You can collect and send exponential histograms to Mimir with the OpenTelemetry Collector. OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The key difference is that exponential histograms store the `min` and `max`  observation values explicitly, whereas native histograms don't. This means that for exponential histograms, you don't need to estimate these values using the 0.0 and 1.0 quantiles.
+You can collect and send exponential histograms to Mimir with the OpenTelemetry Collector. OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The key difference is that exponential histograms store the `min` and `max` observation values explicitly, whereas native histograms don't. This means that for exponential histograms, you don't need to estimate these values using the 0.0 and 1.0 quantiles.
 
 The OpenTelemetry Collector supports collecting exponential histograms and other compatible data formats, such as native histograms and DataDog sketches, through its receivers and sending them through its exporters.
 
@@ -22,7 +22,7 @@ The availability of different receivers and exporters depends on your OpenTeleme
 
 You can use the OpenTelemetry (OTLP) protocol to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms. Refer to [Send native histograms to Mimir](https://grafana.com/docs/mimir/<MIMIR_VERSION>/send/native-histograms/).
 
-The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/). 
+The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
 
 ## Instrument an application with the OpenTelemetry SDK using Go
 
@@ -33,9 +33,9 @@ Use the OpenTelemetry SDK version 1.17.0 or later.
 
    ```
    Aggregation: metric.AggregationBase2ExponentialHistogram{
-			MaxSize:  160,
-			MaxScale: 20,
-		}
+   		MaxSize:  160,
+   		MaxScale: 20,
+   	}
    ```
 
    For more information about views, refer to [Registering Views](https://opentelemetry.io/docs/languages/go/instrumentation/#registering-views) in the OpenTelemetry SDK documentation for Go. For information about view configuration parameters, refer to [Base2 Exponential Bucket Histogram Aggregation](https://github.com/open-telemetry/opentelemetry-specification/blob/main/specification/metrics/sdk.md#base2-exponential-bucket-histogram-aggregation) in the OpenTelemetry Metrics SDK on GitHub.
@@ -47,19 +47,20 @@ To ease the migration process, you can keep the custom bucket definition of an e
 1. Start with an existing histogram that uses explicit buckets.
 1. Create a view for the exponential histogram. Assign this view a unique name and include the exponential aggregation. This creates a metric with the assigned name and exponential buckets.
 
-  The following example shows how to create a metric called `request_latency_exp` that uses exponential buckets.
+The following example shows how to create a metric called `request_latency_exp` that uses exponential buckets.
 
-  ```
-  v := sdkmetric.NewView(sdkmetric.Instrument{
+```
+v := sdkmetric.NewView(sdkmetric.Instrument{
 		Name: "request_latency",
 		Kind: sdkmetric.InstrumentKindHistogram,
 	}, sdkmetric.Stream{
 		Name: "request_latency_exp",
 		Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
 	})
-  ```
+```
+
+For more information about creating a view, refer to [Views](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.
 
-  For more information about creating a view, refer to [Views](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.
 1. Modify dashboards to use the exponential histogram metrics. Refer to [Visualize native histograms](https://grafana.com/docs/mimir/<MIMIR_VERSION>/visualize/native-histograms/) for more information.
 
    Use one of the following strategies to update dashboards.

From 887f28fd0579c365f08f8660ffe9d4e9a1b4eb7c Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Tue, 24 Sep 2024 15:05:49 -0700
Subject: [PATCH 13/16] docs: add feedback for exponential histograms

---
 .../mimir/send/otel-exponential-histograms/_index.md       | 7 +------
 1 file changed, 1 insertion(+), 6 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index a37f3a1beae..fc0296ad207 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -103,12 +103,7 @@ For more information about creating a view, refer to [Views](https://opentelemet
 
    For example, if you have an alert that calculates the rate of requests, such as `sum(rate(http_request_duration_seconds[7d]))`, this query looks at the data from the last seven days plus the Prometheus [lookback period](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness). When you start sending exponential histograms, the data isn't there for the entire seven days, and therefore, the results might be unreliable for alerting.
 
-1. After configuring exponential histogram collection, choose one of the following ways to stop collecting explicit bucket histograms.
-
-   - Remove the custom bucket definition, `Buckets`/`classicUpperBounds`, from the instrumentation. In Java, also use the `nativeOnly()` option. Refer to the examples in [Instrument application with Prometheus client libraries](#instrument-application-with-prometheus-client-libraries).
-   - Drop the explicit bucket histogram series with [Prometheus relabeling](https://prometheus.io/docs/prometheus/latest/configuration/configuration/#relabel_config) or [Grafana Alloy prometheus.relabel](https://grafana.com/docs/alloy/<ALLOY_VERSION>/reference/components/prometheus/prometheus.relabel) at the time of scraping.
-   - Stop scraping the explicit bucket histogram version of metrics. This option applies to all metrics of a scrape target.
-
+1. After configuring exponential histogram collection, remove the explicit bucket histogram definition, as well as any views that expose explicit buckets.
 1. Clean up recording rules and alerts by deleting the explicit bucket histogram version of the rule or alert.
 
 ## Bucket boundary calculation

From 2f6fcabddce90ee01abd33a9b5b3dd11be315e68 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Tue, 24 Sep 2024 15:45:56 -0700
Subject: [PATCH 14/16] docs: add feedback for exponential histograms

---
 .../otel-exponential-histograms/_index.md     | 44 +++++++++----------
 1 file changed, 21 insertions(+), 23 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index fc0296ad207..2e1f7e102b8 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -14,15 +14,15 @@ weight: 200
 
 You can collect and send exponential histograms to Mimir with the OpenTelemetry Collector. OpenTelemetry [exponential histograms](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#exponentialhistogram) are compatible with Prometheus native histograms. The key difference is that exponential histograms store the `min` and `max` observation values explicitly, whereas native histograms don't. This means that for exponential histograms, you don't need to estimate these values using the 0.0 and 1.0 quantiles.
 
-The OpenTelemetry Collector supports collecting exponential histograms and other compatible data formats, such as native histograms and DataDog sketches, through its receivers and sending them through its exporters.
+The OpenTelemetry Collector supports collecting exponential histograms and other compatible data formats, including native histograms and Datadog sketches, through its receivers and sending them through its exporters.
 
 {{< admonition type="note" >}}
 The availability of different receivers and exporters depends on your OpenTelemetry Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
 {{< /admonition >}}
 
-You can use the OpenTelemetry (OTLP) protocol to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms. Refer to [Send native histograms to Mimir](https://grafana.com/docs/mimir/<MIMIR_VERSION>/send/native-histograms/).
+You can use the OpenTelemetry protocol (OTLP) to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms. Refer to [Send native histograms to Mimir](https://grafana.com/docs/mimir/<MIMIR_VERSION>/send/native-histograms/).
 
-The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/).
+The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/) for a complete list.
 
 ## Instrument an application with the OpenTelemetry SDK using Go
 
@@ -47,40 +47,40 @@ To ease the migration process, you can keep the custom bucket definition of an e
 1. Start with an existing histogram that uses explicit buckets.
 1. Create a view for the exponential histogram. Assign this view a unique name and include the exponential aggregation. This creates a metric with the assigned name and exponential buckets.
 
-The following example shows how to create a metric called `request_latency_exp` that uses exponential buckets.
+   The following example shows how to create a metric called `request_latency_exp` that uses exponential buckets.
 
-```
-v := sdkmetric.NewView(sdkmetric.Instrument{
-		Name: "request_latency",
-		Kind: sdkmetric.InstrumentKindHistogram,
-	}, sdkmetric.Stream{
-		Name: "request_latency_exp",
-		Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
-	})
-```
+   ```
+   v := sdkmetric.NewView(sdkmetric.Instrument{
+	   	Name: "request_latency",
+	   	Kind: sdkmetric.InstrumentKindHistogram,
+	   }, sdkmetric.Stream{
+		   Name: "request_latency_exp",
+		   Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
+	   })
+   ```
 
-For more information about creating a view, refer to [Views](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.
+   For more information about creating a view, refer to [View](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.
 
 1. Modify dashboards to use the exponential histogram metrics. Refer to [Visualize native histograms](https://grafana.com/docs/mimir/<MIMIR_VERSION>/visualize/native-histograms/) for more information.
 
    Use one of the following strategies to update dashboards.
 
-   - (Recommended) Add new dashboards with the new exponential histogram queries. This solution requires looking at different dashboards for data before and after the migration, until data before the migration is removed due to passing its retention time. You can publish the new dashboard when sufficient time has passed to serve users with the new data.
+   - (Recommended) Create dashboards with the exponential histogram queries. This solution requires looking at different dashboards for data before and after the migration, until data before the migration is removed due to passing its retention time. You can publish the dashboard when sufficient time has passed to serve users with the new data.
    - Add a dashboard variable to your dashboard to enable switching between explicit bucket histograms and exponential histograms. There isn't support for selectively enabling and disabling queries in Grafana ([issue 79848](https://github.com/grafana/grafana/issues/79848)). As a workaround, add the dashboard variable `latency_metrics`, for example, and assign it a value of either `-1` or `1`. Then, add the following two queries to the panel:
 
      ```
-     <classic_query> < ($latency_metrics * +Inf)
+     <explicit_bucket_query> < ($latency_metrics * +Inf)
      ```
 
      ```
-     <native_query> < ($latency_metrics * -Inf)
+     <exponential_query> < ($latency_metrics * -Inf)
      ```
 
-     Where `classic_query` is the original query and `native_query` is the same query using exponential histogram query syntax. This technique is employed in Mimir's dashboards. For an example, refer to the [Overview dashboard](https://github.com/grafana/mimir/blob/main/operations/mimir-mixin-compiled/dashboards/mimir-overview.json) in the Mimir repository.
+     Where `explicit_bucket_query` is the original query and `exponential_query` is the same query using exponential histogram query syntax. This technique is employed in Mimir's dashboards. For an example, refer to the [Overview dashboard](https://github.com/grafana/mimir/blob/main/operations/mimir-mixin-compiled/dashboards/mimir-overview.json) in the Mimir repository.
 
      This solution allows users to switch between the explicit bucket histogram and the exponential histogram without going to a different dashboard.
 
-   - Replace the existing explicit bucket queries with modified queries. For example, replace:
+   - Replace the explicit bucket queries with modified queries. For example, replace:
 
      ```
      <explicit_bucket_query>
@@ -98,7 +98,7 @@ For more information about creating a view, refer to [Views](https://opentelemet
      Using the PromQL operator `or` can lead to unexpected results. For example, if a query uses a range of seven days, such as `sum(rate(http_request_duration_seconds[7d]))`, then this query returns a value as soon as there are two exponential histograms samples present before the end time specified in the query. In this case, the seven day rate is calculated from a couple of minutes, rather than seven days, worth of data. This results in an inaccuracy in the graph around the time you started scraping exponential histograms.
      {{< /admonition >}}
 
-1. Start adding new recording rules and alerts to use exponential histograms. Don't remove the old recording rules and alerts at this time.
+1. Begin adding recording rules and alerts to use exponential histograms. Don't remove any existing recording rules and alerts at this time.
 1. It's important to keep scraping both explicit bucket and exponential histograms for at least the period of the longest range in your recording rules and alerts, plus one day. This is the minimum amount of time, but it's recommended to keep scraping both data types until you can verify the new rules and alerts.
 
    For example, if you have an alert that calculates the rate of requests, such as `sum(rate(http_request_duration_seconds[7d]))`, this query looks at the data from the last seven days plus the Prometheus [lookback period](https://prometheus.io/docs/prometheus/latest/querying/basics/#staleness). When you start sending exponential histograms, the data isn't there for the entire seven days, and therefore, the results might be unreliable for alerting.
@@ -108,9 +108,7 @@ For more information about creating a view, refer to [Views](https://opentelemet
 
 ## Bucket boundary calculation
 
-Bucket boundaries for exponential histograms are calculated similarly to those for native histograms. The only difference is that for exponential histograms, bucket offsets are shifted by one.
-
-Thus:
+Bucket boundaries for exponential histograms are calculated similarly to those for native histograms. The only difference is that for exponential histograms, bucket offsets are shifted by one, as shown in the following equation.
 
 <!--- LaTeX equation source: {\left( 2^{2^{-schema}} \right)}^{index} < v \leq {\left( 2^{2^{-schema}}\right)}^{index+1} -->
 

From 254f484fc0701de03fab260bdb45ecff42cb8101 Mon Sep 17 00:00:00 2001
From: Taylor C <41653732+tacole02@users.noreply.github.com>
Date: Wed, 25 Sep 2024 15:44:06 -0700
Subject: [PATCH 15/16] Update
 docs/sources/mimir/send/otel-exponential-histograms/_index.md

Co-authored-by: George Krajcsovits <krajorama@users.noreply.github.com>
---
 docs/sources/mimir/send/otel-exponential-histograms/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 2e1f7e102b8..3c1d37661ac 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -20,7 +20,7 @@ The OpenTelemetry Collector supports collecting exponential histograms and other
 The availability of different receivers and exporters depends on your OpenTelemetry Collector [distribution](https://opentelemetry.io/docs/concepts/distributions/).
 {{< /admonition >}}
 
-You can use the OpenTelemetry protocol (OTLP) to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms. Refer to [Send native histograms to Mimir](https://grafana.com/docs/mimir/<MIMIR_VERSION>/send/native-histograms/).
+You can use the OpenTelemetry protocol (OTLP) over HTTP to send exponential histograms to Grafana Mimir in their existing format, or you can use the Prometheus remote write protocol to send them as Prometheus native histograms.
 
 The OpenTelemetry SDK supports instrumenting applications in multiple languages. Refer to [Language APIs & SDKs](https://opentelemetry.io/docs/languages/) for a complete list.
 

From 94384dbe33f9fd68039195b22ede025c8c7c9d80 Mon Sep 17 00:00:00 2001
From: Taylor Cole <tacole02@gmail.com>
Date: Thu, 26 Sep 2024 12:54:52 -0700
Subject: [PATCH 16/16] docs: make doc output

---
 .../mimir/send/otel-exponential-histograms/_index.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/docs/sources/mimir/send/otel-exponential-histograms/_index.md b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
index 3c1d37661ac..22382fafb28 100644
--- a/docs/sources/mimir/send/otel-exponential-histograms/_index.md
+++ b/docs/sources/mimir/send/otel-exponential-histograms/_index.md
@@ -51,12 +51,12 @@ To ease the migration process, you can keep the custom bucket definition of an e
 
    ```
    v := sdkmetric.NewView(sdkmetric.Instrument{
-	   	Name: "request_latency",
-	   	Kind: sdkmetric.InstrumentKindHistogram,
-	   }, sdkmetric.Stream{
-		   Name: "request_latency_exp",
-		   Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
-	   })
+      	Name: "request_latency",
+      	Kind: sdkmetric.InstrumentKindHistogram,
+      }, sdkmetric.Stream{
+   	   Name: "request_latency_exp",
+   	   Aggregation: sdkmetric.AggregationBase2ExponentialHistogram{MaxSize: 160, NoMinMax: true, MaxScale: 20},
+      })
    ```
 
    For more information about creating a view, refer to [View](https://opentelemetry.io/docs/specs/otel/metrics/sdk/#view) in the OpenTelemetry Metrics SDK.