[DOC] Add blog link; update instrumentation scope doc (#4569)

(cherry picked from commit 89b9f7e)

docs/sources/tempo/release-notes/v2-7.md

@@ -16,15 +16,12 @@ This release gives you:
 * New TraceQL capabilities
 * Improvements to TraceQL metrics
 
-<!-- Add link to blog post
-Read the [Tempo 2.7 blog post](https://grafana.com/blog/2024/09/05/grafana-tempo-2.6-release-performance-improvements-and-new-traceql-features/) for more examples and details about these improvements. -->
+Read the [Tempo 2.7 blog post](https://grafana.com/blog/2025/01/16/grafana-tempo-2.7-release-new-traceql-metrics-functions-operational-improvements-and-more/) for more examples and details about these improvements.
 
 These release notes highlight the most important features and bugfixes.
 For a complete list, refer to the [Tempo changelog](https://github.com/grafana/tempo/releases).
 
-<!-- add link to video for blog post
-{{< youtube id="aIDkPJ_e3W4" >}}
--->
+{{< youtube id="0jUEvY-pCdw" >}}
 
 ## Features and enhancements
 

docs/sources/tempo/traceql/_index.md

@@ -239,11 +239,8 @@ The following table shows the current available scoped intrinsic fields:
 | `event:timeSinceStart`   | duration    | time of event in relation to the span start time                | `{ event:timeSinceStart > 2ms}`         |
 | `link:spanID`            | string      | link span ID using hex string                                   | `{ link:spanID = "0000000000000001" }`  |
 | `link:traceID`           | string      | link trace ID using hex string                                  | `{ link:traceID = "1234567890abcde" }`  |
-
-<!-- instrumentation scope isn't included in the 2.6 documentation
 | `instrumentation:name`   | string      | instrumentation scope name                                      | `{ instrumentation:name = "grpc" }`     |
 | `instrumentation:version`| string      | instrumentation scope version                                   | `{ instrumentation:version = "1.0.0" }` |
--->
 
 The trace-level intrinsics, `trace:duration`, `trace:rootName`, and `trace:rootService`, are the same for all spans in the same trace.
 Additionally, these intrinsics are significantly more performant because they have to inspect much less data then a span-level intrinsic.
@@ -261,9 +258,7 @@ This example searches all Kubernetes clusters called `service-name` that have a
 
 ### Attribute fields
 
-TraceQL has four different attribute scopes: span attributes, resource attributes, event attributes, and link attributes.
-<!-- instrumentation scope isn't in 2.6 >
-instrumentation scope attributes.  -->
+TraceQL supports these different attribute scopes: span attributes, resource attributes, event attributes, link attributes, and instrumentation scope attributes.
 
 By expanding a span in the Grafana UI, you can see both its span attributes (1 in the screenshot) and resource attributes (2 in the screenshot).
 
@@ -314,12 +309,21 @@ You can search for an attribute in your link:
 ```
 { link.opentracing.ref_type = "child_of" }
 ```
-<!-- instrumentation scope isn't included in the 2.6 release
+
+The instrumentation scope lets you query the [instrumentation scope](https://opentelemetry.io/docs/concepts/instrumentation-scope/) fields so you can filter and explore your traces based on where and how they were instrumented.
+The primary use of this scope is to query your trace data based on the various libraries and clients that are producing data.
+
 Find instrumentation scope programming language:
 ```
 { instrumentation.language = "java" }
 ```
--->
+
+Find the libraries producing instrumentation for a given service:
+```
+{ resource.service.name = "foo" } | rate() by (instrumentation:name)
+```
+
+The [Tempo 2.7 release video](https://www.youtube.com/watch?v=0jUEvY-pCdw) demos and explains the `instrumentation` scope, starting at 30 seconds.
 
 ### Unscoped attribute fields