Alert cleanup (#7090)

Author: chalin

content/en/blog/2022/k8s-metadata/index.md

@@ -7,7 +7,7 @@ author: '[Ruben Vargas](https://github.com/rubenvp8510)'
 cSpell:ignore: k8sattributes k8sattributesprocessor k8sprocessor KUBE replicaset replicasetname resourcedetection
 ---
 
-{{% alert title="Note" color="info" %}} The most up to date information for how
+{{% alert title="Note" %}} The most up to date information for how
 to enhance telemetry with Kubernetes metadata can be found in the docs. See
 [Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/)
 for more info. {{% /alert %}}

content/en/blog/2023/opamp-status/index.md

@@ -53,7 +53,7 @@ want to use OpAMP both as an collector extension, with limited functionality, as
 well as as an (collector-external) supervisor that implements a broader set of
 OpAMP capabilities.
 
-{{% alert title="Note" color="info" %}} For a deeper dive, see
+{{% alert title="Note" %}} For a deeper dive, see
 [OpAMP for OpenTelemetry Collector document](https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/cmd/opampsupervisor/specification),
 which describes how to implement both options while minimizing code duplication.
 {{% /alert %}}
@@ -113,7 +113,7 @@ to be deployed by the OpenTelemetry Operator:
 
 ![OpAMP bridge in the OTel Operator](opamp-kubernetes-bridge.png)
 
-{{% alert title="Note" color="info" %}} Currently, we don't have support for
+{{% alert title="Note" %}} Currently, we don't have support for
 deployment via Helm chart, however, if you'd like to contribute to this, you're
 welcome to contribute.{{% /alert %}}
 

content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md

@@ -50,7 +50,7 @@ This blog post shows how to set up this solution step by step.
 
 ## Configure Java application to output OTLP/JSON logs
 
-{{% alert title="Note" color="info" %}}
+{{% alert title="Note" %}}
 
 Blog post instructions can easily get outdated. In case of issues, check this
 [sample application deployed on Kubernetes](https://github.com/open-telemetry/opentelemetry-java-examples/blob/main/logging-k8s-stdout-otlp-json/README.md),
@@ -100,7 +100,7 @@ The `-Dotel.logs.exporter=experimental-otlp/stdout` JVM argument and the
 environment variable `OTEL_LOGS_EXPORTER="experimental-otlp/stdout"` can be used
 interchangeably.
 
-{{% alert title="Note" color="info" %}}
+{{% alert title="Note" %}}
 
 The OTLP logs exporter is experimental and subject to change. Check the
 [Specification PR](https://github.com/open-telemetry/opentelemetry-specification/pull/4183)

content/en/blog/2024/otel-generative-ai/index.md

@@ -75,7 +75,7 @@ model responses, providing a granular view of model interactions. These insights
 are invaluable for debugging and optimizing AI applications where unexpected
 behaviors may arise.
 
-{{% alert title="Note" color="info" %}}
+{{% alert title="Note" %}}
 
 Note that we decided to use [events emitted] with the
 [Logs API](/docs/specs/otel/logs/api/) specification in the Semantic Conventions

content/en/blog/2025/contribex-survey.md

@@ -8,12 +8,12 @@ sig: Contributor Experience
 cSpell:ignore: Baeyens Outreachy
 ---
 
-{{% alert-md title="TL;DR" color="secondary" %}}
+{{% alert title="TL;DR" color="secondary" %}}
 
 Take our [OpenTelemetry Contributor Survey][6] and help us **enhance the
 contributor experience**. We appreciate your time and feedback!
 
-{{% /alert-md %}}
+{{% /alert %}}
 
 Since its founding, OpenTelemetry has had [thousands of contributors][3] from
 around the world, including end users, vendors, and students. [Last summer][1]

content/en/blog/2025/kubecon-eu.md

@@ -11,7 +11,7 @@ cSpell:ignore: Adevinta Aftab Arianna Baeyens Bartłomiej Boulineau Celalettin C
 
 The OpenTelemetry governance and technical committees, along with the project's
 maintainers, invite you to join them and other members of the OpenTelemetry
-community at [KubeCon + CloudNativeCon Europe][] ([registration][]) and at the
+community at [KubeCon + CloudNativeCon Europe][] ([registration]) and at the
 co-located [Observability Day] in London from April 1 to 4, 2025.
 
 This post covers all currently scheduled activities related to OpenTelemetry
@@ -113,15 +113,12 @@ cloud native observability projects. This event will be held on Tuesday, April
 1, 2025, from 9:00 - 17:25. There will be several sessions on OpenTelemetry as
 well.
 
-{{% alert-md title="Important access note" color="danger" %}}
+{{% alert title="Important access note" color="danger" %}}
 
 You need an _all-access_ pass to attend **Observability Day**. For details, see
 [KubeCon registration][registration].
 
-[registration]:
-  https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/?utm_source=opentelemetry&utm_medium=all&utm_campaign=KubeCon-EU-2025&utm_content=blog
-
-{{% /alert-md %}}
+{{% /alert %}}
 
 - **[Sponsored Keynote: The Future of Observability: Trends, AI, and New Relic’s Vision for a Smarter Stack](https://sched.co/1u5jm)**<br>
   by Harry Kimpel, New Relic<br> Tuesday, April 1 • 10:00 - 10:05
@@ -230,4 +227,6 @@ Come listen, learn, and get involved in OpenTelemetry. See you in London!
   https://cloud-native.slack.com/archives/C01RT3MSWGZ
 [OTel Observatory Calendar]:
   https://calendar.google.com/calendar/embed?src=c_6b6b343737cc9bbf0393ba40c101d6b017514751e66951c9890d089eedd78a37@group.calendar.google.com&mode=WEEK&dates=20250331/20250406
+[registration]:
+  https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/register/?utm_source=opentelemetry&utm_medium=all&utm_campaign=KubeCon-EU-2025&utm_content=blog
 [Splunk]: https://www.splunk.com/

content/en/blog/2025/otel-js-sdk-2-0.md

@@ -13,15 +13,15 @@ Exciting news: [OpenTelemetry JavaScript](/docs/languages/js/) has released [SDK
 
 [v2.0.0]: https://github.com/open-telemetry/opentelemetry-js/releases/tag/v2.0.0
 
-{{% alert-md title="Migration guide" color="info" %}}
+{{% alert title="Migration guide" %}}
 
 For a detailed description of breaking changes, see the **migration guide**:
 [Upgrade to OpenTelemetry JS SDK 2.x][migration guide].
 
 [migration guide]:
   https://github.com/open-telemetry/opentelemetry-js/blob/main/doc/upgrade-to-2.x.md
 
-{{% /alert-md %}}
+{{% /alert %}}
 
 ## What is JS SDK 2.x?
 

content/en/docs/_includes/exporters/intro.md

@@ -42,13 +42,13 @@ them up.
 
 {{ if $zeroConfigPageExists }}
 
-<div class="alert alert-info" role="alert"><h4 class="alert-heading">Note</h4>
+{{% alert title=Note %}}
 
 If you use [zero-code instrumentation](</docs/zero-code/{{ $langIdAsPath }}>),
 you can learn how to set up exporters by following the
 [Configuration Guide](</docs/zero-code/{{ $langIdAsPath }}/configuration/>).
 
-</div>
+{{% /alert %}}
 
 {{ end }}
 
@@ -58,13 +58,13 @@ you can learn how to set up exporters by following the
 
 ### Collector Setup
 
-<div class="alert alert-info" role="alert"><h4 class="alert-heading">Note</h4>
+{{% alert title=Note %}}
 
 If you have a OTLP collector or backend already set up, you can skip this
 section and [setup the OTLP exporter dependencies](#otlp-dependencies) for your
 application.
 
-</div>
+{{% /alert %}}
 
 To try out and verify your OTLP exporters, you can run the collector in a docker
 container that writes telemetry directly to the console.

content/en/docs/collector/building/receiver.md

@@ -269,7 +269,7 @@ type Config struct {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Added the `Interval` and the `NumberOfTraces` fields to properly have access
   to their values from the config.yaml.
@@ -317,7 +317,7 @@ func (cfg *Config) Validate() error {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Imported the `fmt` package to properly format print error messages.
 - Added the `Validate` method to the Config struct to check if the `interval`
@@ -456,7 +456,7 @@ func NewFactory() receiver.Factory {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Importing the `time` package in order to support the time.Duration type for
   the defaultInterval.
@@ -577,7 +577,7 @@ func NewFactory() receiver.Factory {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Importing the `context` package in order to support the `context.Context` type
   referenced in the `createTracesReceiver` function.
@@ -676,7 +676,7 @@ func (tailtracerRcvr *tailtracerReceiver) Shutdown(ctx context.Context) error {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Importing the `context` package which is where the `Context` type and
   functions are declared.
@@ -751,7 +751,7 @@ func (tailtracerRcvr *tailtracerReceiver) Shutdown(ctx context.Context) error {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Updated the `Start()` method by adding the initialization to the `host` field
   with the `component.Host` reference passed by the Collector and the `cancel`
@@ -837,7 +837,7 @@ func (tailtracerRcvr *tailtracerReceiver) Shutdown(ctx context.Context) error {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Importing the `go.opentelemetry.io/collector/consumer` which is where the
   pipeline's consumer types and interfaces are declared.
@@ -932,7 +932,7 @@ func NewFactory() receiver.Factory {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Added a variable called `logger` and initialized it with the Collector's
   logger that is available as a field named `Logger` within the
@@ -1017,7 +1017,7 @@ func components() (otelcol.Factories, error) {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Importing the receiver module
   `github.com/open-telemetry/opentelemetry-tutorials/trace-receiver/tailtracer`
@@ -1336,7 +1336,7 @@ func getRandomNumber(min int, max int) int {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Imported the `math/rand` and `time` packages to support the implementation of
   the `generateRandomNumber` function.
@@ -1433,7 +1433,7 @@ func generateTraces(numberOfTraces int) ptrace.Traces{
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Added the `resourceSpan` variable and initialized it with the `ResourceSpan`
   reference returned by the `traces.ResourceSpans().AppendEmpty()` call.
@@ -1491,7 +1491,7 @@ func fillResourceWithAtm(resource *pcommon.Resource, atm Atm){
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Declared a variable called `atmAttrs` and initialized it with the
   `pcommon.Map` reference returned by the `resource.Attributes()` call.
@@ -1723,7 +1723,7 @@ func fillResourceWithBackendSystem(resource *pcommon.Resource, backend BackendSy
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Imported the `go.opentelemetry.io/collector/semconv/v1.9.0` package as
   `conventions`, in order to have access to all resource semantic conventions
@@ -1925,7 +1925,7 @@ func NewSpanID() pcommon.SpanID {
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Imported `crypto/rand` as `crand` (to avoid conflicts with `math/rand`).
 - Added new functions `NewTraceID()` and `NewSpanID()` to generate trace ID and
@@ -1962,7 +1962,7 @@ func appendTraceSpans(backend *BackendSystem, backendScopeSpans *ptrace.ScopeSpa
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Added `traceId` and `backendSpanId` variables to respectively represent the
   trace and the span ID and initialized them with the helper functions created
@@ -2260,7 +2260,7 @@ func (tailtracerRcvr *tailtracerReceiver) Start(ctx context.Context, host compon
 }
 ```
 
-{{% alert title="Check your work" color="primary" %}}
+{{% alert title="Check your work" %}}
 
 - Added a line under the `case <=ticker.C` condition calling the
   `tailtracerRcvr.nextConsumer.ConsumeTraces()` method passing the new context

content/en/docs/collector/configuration.md

@@ -50,7 +50,7 @@ otelcol --config=env:MY_CONFIG_IN_AN_ENVVAR --config=https://server/config.yaml
 otelcol --config="yaml:exporters::debug::verbosity: normal"
 ```
 
-{{% alert title="Tip" color="primary" %}}
+{{% alert title="Tip" %}}
 
 When referring to nested keys in YAML paths, make sure to use double colons (::)
 to avoid confusion with namespaces that contain dots. For example: