Added exemplar topic (#34147)

* Added topic and definition.

* More changes.

* Update docs/sources/basics/exemplars.md

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

* Update docs/sources/basics/exemplars.md

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

* Update docs/sources/basics/exemplars.md

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

* Added the time series topic back.

* Update docs/sources/basics/exemplars.md

* Updated title.

Co-authored-by: Diana Payton <52059945+oddlittlebird@users.noreply.github.com>

docs/sources/basics/exemplars.md

@@ -0,0 +1,22 @@
++++
+title = "Exemplars"
+description = "Exemplars"
+keywords = ["grafana", "concepts", "exemplars", "prometheus"]
+weight = 400
++++
+
+# Introduction to exemplars
+
+An exemplar is a specific trace representative of a repeated pattern of data in a given time interval. It helps you identify higher cardinality metadata from specific events within time series data.
+
+Suppose your company website is experiencing a surge in traffic volumes. While more than eighty percent of the users are able to access the website in under two seconds, some users are experiencing a higher than normal response time resulting in bad user experience
+
+To identify the factors that are contributing to the latency, you must compare a trace for a fast response against a trace for a slow response. Given the vast amount of data in a typical production environment, it will be extremely laborious and time-consuming effort. 
+
+Use exemplars to help isolate problems within your data distribution by pinpointing query traces exhibiting high latency within a time interval. Once you localize the latency problem to a few exemplar traces, you can combine it with additional system based information or location properties to perform a root cause analysis faster, leading to quick resolutions to performance issues.
+
+Support for exemplars is available for the Prometheus data source only. Once you enable the functionality, exemplars data is available by default. For more information on exemplar configuration and how to enable exemplars, refer to [configuring exemplars in Prometheus data source]({{< relref "../datasources/prometheus.md" >}}).
+
+Grafana shows exemplars alongside a metric in the Explore view and in dashboards. Each exemplar displays as a highlighted star. You can hover your cursor over an exemplar to view the unique traceID, which is a combination of a key value pair. To investigate further, click the blue button next to the `traceID` property. 
+
+{{< docs-imagebox img="/img/docs/v74/exemplars.png" class="docs-image--no-shadow" max-width= "750px" caption="Screenshot showing the detail window of an Exemplar" >}}

docs/sources/basics/timeseries.md

@@ -2,8 +2,7 @@
 title = "Time series"
 description = "Introduction to time series"
 keywords = ["grafana", "intro", "guide", "concepts", "timeseries"]
-aliases = ["/docs/grafana/latest/guides/timeseries", "/docs/grafana/latest/getting-started/timeseries"]
-weight = 500
+weight = 400
 +++
 
 # Introduction to time series
@@ -121,3 +120,4 @@ A collector either _pushes_ data to a database or lets the database _pull_ the d
 | Pull | Better control of how much data that gets ingested, and its authenticity. | Firewalls, VPNs or load balancers can make it hard to access the agents. |
 
 Since it would be inefficient to write every measurement to the database, collectors pre-aggregate the data and write to the time series database at regular intervals.
+

docs/sources/datasources/prometheus.md

@@ -212,7 +212,7 @@ To connect the Prometheus data source to Amazon Managed Service for Prometheus u
 
 If you are running Grafana in an Amazon EKS cluster, follow the AWS guide to [Query using Grafana running in an Amazon EKS cluster](https://docs.aws.amazon.com/prometheus/latest/userguide/AMP-onboard-query-grafana-7.3.html).
 
-## Exemplars
+## Configuring exemplars
 
 > **Note:** This feature is available in Prometheus 2.26+ and Grafana 7.4+.