diff --git a/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md b/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md index 09e4024302f6..4c85a4da72fb 100644 --- a/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md +++ b/content/en/blog/2019/opentelemetry-governance-committee-explained/index.md @@ -77,4 +77,4 @@ feedback! _A version of this article was [originally posted][] on [medium.com/opentelemetry](https://medium.com/opentelemetry)._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/auto-instrumentation-k8s.md b/content/en/blog/2021/auto-instrumentation-k8s.md index 6f37dc2dff63..9aa48672f7f7 100644 --- a/content/en/blog/2021/auto-instrumentation-k8s.md +++ b/content/en/blog/2021/auto-instrumentation-k8s.md @@ -9,4 +9,4 @@ This article introduces OpenTelemetry Operator’s new feature that significantl simplifies instrumenting workloads deployed on Kubernetes. Read all the details from the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/collector.md b/content/en/blog/2021/collector.md index b0d1daf6c1bf..facd58df90ff 100644 --- a/content/en/blog/2021/collector.md +++ b/content/en/blog/2021/collector.md @@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/opentelemetry-collector-achieves The OpenTelemetry Collector has made its first GA release. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/cpp.md b/content/en/blog/2021/cpp.md index db630f056f8f..36dd3d6195c1 100644 --- a/content/en/blog/2021/cpp.md +++ b/content/en/blog/2021/cpp.md @@ -9,4 +9,4 @@ OpenTelemetry C++ released its v1.0 stable version last month, which implements the OpenTelemetry distributed tracing specification! For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/gc-election.md b/content/en/blog/2021/gc-election.md index 7fad088401b3..41415f9bf63e 100644 --- a/content/en/blog/2021/gc-election.md +++ b/content/en/blog/2021/gc-election.md @@ -9,4 +9,4 @@ The OpenTelemetry project is excited to announce the 2021 OpenTelemetry Governance Committee (GC) election. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/malabi.md b/content/en/blog/2021/malabi.md index 3e156e7066da..8115d18eff16 100644 --- a/content/en/blog/2021/malabi.md +++ b/content/en/blog/2021/malabi.md @@ -10,4 +10,4 @@ cSpell:ignore: Malabi This article introduces you to Malabi, a new open source tool for trace-based testing. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/otel-gc.md b/content/en/blog/2021/otel-gc.md index a3d5496b3454..a5647fc76618 100644 --- a/content/en/blog/2021/otel-gc.md +++ b/content/en/blog/2021/otel-gc.md @@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/welcome-to-the-incoming-2021-ope The OpenTelemetry project just completed its 2021 election for the Governance Committee (GC). For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/python.md b/content/en/blog/2021/python.md index e4f48cee06b1..fe2df0c4552f 100644 --- a/content/en/blog/2021/python.md +++ b/content/en/blog/2021/python.md @@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/announcing-opentelemetry-python- Today, OpenTelemetry Python distributed tracing API/SDK released its 1.0 version. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/swift.md b/content/en/blog/2021/swift.md index f93cbf1da8c9..8abc8c782d5b 100644 --- a/content/en/blog/2021/swift.md +++ b/content/en/blog/2021/swift.md @@ -8,4 +8,4 @@ canonical_url: https://medium.com/opentelemetry/opentelemetry-swift-1-0-beta-8f7 Today, OpenTelemetry Swift distributed tracing API/SDK has released its 1.0 version. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2021/womens-day.md b/content/en/blog/2021/womens-day.md index 65966a157fbd..184e889e4a36 100644 --- a/content/en/blog/2021/womens-day.md +++ b/content/en/blog/2021/womens-day.md @@ -9,4 +9,4 @@ Happy International Women’s Day! The OpenTelemetry project would like to exten our thanks to all our women contributors. For all the details, see the [original post][]. -[original post]: {{% param canonical_url %}} +[original post]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/apisix/index.md b/content/en/blog/2022/apisix/index.md index 8be837184052..64435c550e4a 100644 --- a/content/en/blog/2022/apisix/index.md +++ b/content/en/blog/2022/apisix/index.md @@ -395,4 +395,4 @@ _A version of this article was [originally posted][] on the Apache APISIX blog._ [^1]: {{% param notes.docker-compose-v2 %}} -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/exponential-histograms/index.md b/content/en/blog/2022/exponential-histograms/index.md index e5c666358263..f013f91215a8 100644 --- a/content/en/blog/2022/exponential-histograms/index.md +++ b/content/en/blog/2022/exponential-histograms/index.md @@ -278,8 +278,6 @@ documentation on [instrumentation][] or [github.com/open-telemetry][]. _A version of this article was [originally posted][] on the New Relic blog._ -[originally posted]: {{% param canonical_url %}} - [api]: /docs/specs/otel/metrics/api/ [sdk]: /docs/specs/otel/metrics/sdk/ [meter provider]: /docs/specs/otel/metrics/api/#meterprovider @@ -304,3 +302,4 @@ _A version of this article was [originally posted][] on the New Relic blog._ [environment variable]: /docs/specs/otel/metrics/sdk_exporters/otlp/ [instrumentation]: /docs/languages [github.com/open-telemetry]: https://github.com/open-telemetry +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/go-web-app-instrumentation/index.md b/content/en/blog/2022/go-web-app-instrumentation/index.md index db423abc7ab5..0abe9f0fcb0b 100644 --- a/content/en/blog/2022/go-web-app-instrumentation/index.md +++ b/content/en/blog/2022/go-web-app-instrumentation/index.md @@ -415,4 +415,4 @@ find all files ready to use in our GitHub _A version of this article was [originally posted][] on the Aspecto blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/k8s-metadata/index.md b/content/en/blog/2022/k8s-metadata/index.md index 8d41d0a41def..d73d4db79e4e 100644 --- a/content/en/blog/2022/k8s-metadata/index.md +++ b/content/en/blog/2022/k8s-metadata/index.md @@ -9,8 +9,8 @@ cSpell:ignore: k8sattributes k8sattributesprocessor k8sprocessor KUBE replicaset {{% alert title="Note" color="info" %}} 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 %}} +[Getting Started with Kubernetes](/docs/platforms/kubernetes/getting-started/) +for more info. {{% /alert %}} Attaching Kubernetes resource metadata to OpenTelemetry traces is useful to identify which resource (such as a pod) is failing or having performance diff --git a/content/en/blog/2022/k8s-otel-expose/index.md b/content/en/blog/2022/k8s-otel-expose/index.md index 6c52ad6d8099..37000fad36ce 100644 --- a/content/en/blog/2022/k8s-otel-expose/index.md +++ b/content/en/blog/2022/k8s-otel-expose/index.md @@ -106,8 +106,8 @@ in this setup are mentioned in brackets. [v1.2.1] installed. - A Kubernetes [v1.23.3] edge cluster to create a test cluster. Using [Kind](https://kind.sigs.k8s.io/) is recommended. -- Installed [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) [v0.58.0] on - both ends. +- Installed [OpenTelemetry Operator](/docs/platforms/kubernetes/operator/) + [v0.58.0] on both ends. - Installed [Jaeger Operator](https://www.jaegertracing.io/docs/1.37/operator/) [v1.37.0] on your public cluster. - Installed [cert-manager](https://cert-manager.io/) [v1.9.1] on your public diff --git a/content/en/blog/2022/tail-sampling/index.md b/content/en/blog/2022/tail-sampling/index.md index f84b7a6132cb..fdb0a3daaf68 100644 --- a/content/en/blog/2022/tail-sampling/index.md +++ b/content/en/blog/2022/tail-sampling/index.md @@ -227,4 +227,4 @@ for more information. _A version of this article was [originally posted][] on the New Relic blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/troubleshooting-nodejs.md b/content/en/blog/2022/troubleshooting-nodejs.md index e58745b4b8d1..fb8f6f5eb2a8 100644 --- a/content/en/blog/2022/troubleshooting-nodejs.md +++ b/content/en/blog/2022/troubleshooting-nodejs.md @@ -385,4 +385,4 @@ For a list of OpenTelemetry vendors, see [Vendors](/ecosystem/vendors/). _A version of this article was [originally posted][] on the Aspecto blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/v1.0-trio.md b/content/en/blog/2022/v1.0-trio.md index 0bf3fa4f7be2..706fcfc813f2 100644 --- a/content/en/blog/2022/v1.0-trio.md +++ b/content/en/blog/2022/v1.0-trio.md @@ -10,4 +10,4 @@ new languages (Ruby, JavaScript, and Erlang/Elixir) have had their first 1.0 releases, joining the existing GA releases from C++, Go, Java, .NET, Python and Swift. Read all the details from the [announcement][]. -[announcement]: {{% param canonical_url %}} +[announcement]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md b/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md index c3517b8e125d..004454c150e3 100644 --- a/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md +++ b/content/en/blog/2022/why-and-how-ebay-pivoted-to-opentelemetry/index.md @@ -21,8 +21,8 @@ ongoing issues in critical workflows that could potentially impact customer experience. The Observability landscape is an ever-changing one and recent developments in the OpenTelemetry world forced us to rethink our strategy in order to pivot to using it. eBay’s observability platform Sherlock.io provides -developers and Site Reliability Engineers (SREs) with a robust set of -cloud native offerings to observe the various applications that power the eBay +developers and Site Reliability Engineers (SREs) with a robust set of cloud +native offerings to observe the various applications that power the eBay ecosystem. Sherlock.io supports the three pillars of observability — metrics, logs and traces. The platform’s metric store is a clustered and sharded implementation of the Prometheus storage engine. We use the Metricbeat agent to @@ -353,4 +353,4 @@ OpenTelemetry Collector community: _A version of this article was [originally posted][] on the eBay Tech Blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2023/contributing-to-otel/index.md b/content/en/blog/2023/contributing-to-otel/index.md index d870b075facf..03bf1ba531b9 100644 --- a/content/en/blog/2023/contributing-to-otel/index.md +++ b/content/en/blog/2023/contributing-to-otel/index.md @@ -145,11 +145,11 @@ Feeling a little more adventurous? Then why not join one of the other OTel (SIGs)? By joining a SIG, you can contribute to things like (but not limited to) SDK development, auto-instrumentation of libraries, the [OTel Collector](/docs/collector/), and the -[OTel Operator](/docs/platforms/kubernetes/operator/). You don't even need to be a regular -contributor. Sometimes, contributions come out of necessity. Like maybe you -found a bug in the Collector. Why not take a stab at fixing it? Or maybe there's -a feature that you and your team desperately need. Again, why not take a stab at -implementing it? +[OTel Operator](/docs/platforms/kubernetes/operator/). You don't even need to be +a regular contributor. Sometimes, contributions come out of necessity. Like +maybe you found a bug in the Collector. Why not take a stab at fixing it? Or +maybe there's a feature that you and your team desperately need. Again, why not +take a stab at implementing it? Now, before you go off writing code, you should make sure that you: diff --git a/content/en/blog/2023/end-user-q-and-a-03.md b/content/en/blog/2023/end-user-q-and-a-03.md index 13437b190335..906d0230974e 100644 --- a/content/en/blog/2023/end-user-q-and-a-03.md +++ b/content/en/blog/2023/end-user-q-and-a-03.md @@ -156,8 +156,8 @@ others are still instrumented using the [legacy OpenTracing [using shims](/docs/migration/opentracing/). The OpenTelemetry Operator is being implemented to auto-instrument Java and .NET -code. Among other things, the [OTel Operator](/docs/platforms/kubernetes/operator/) -supports injecting and +code. Among other things, the +[OTel Operator](/docs/platforms/kubernetes/operator/) supports injecting and [configuring auto-instrumentation](/docs/platforms/kubernetes/operator/automatic/#configure-automatic-instrumentation) in .NET, Java, Python, and Node.js. Iris hopes that Go auto-instrumentation will be available in the near-future. To track progress of auto-instrumentation in @@ -255,8 +255,9 @@ would be a bottleneck in terms of load and single point of failure. The team currently has one [OpenTelemetry Collector agent](/docs/collector/deployment/agent/) per Kubernetes cluster. The end goal is to replace those agents with the -[OTel Operator](/docs/platforms/kubernetes/operator/) instead, which allows you to deploy -and configure the OTel Collector and inject and configure auto-instrumentation. +[OTel Operator](/docs/platforms/kubernetes/operator/) instead, which allows you +to deploy and configure the OTel Collector and inject and configure +auto-instrumentation. Everything is then sent to a central OTel Collector (i.e. an [OTel Collector gateway](/docs/collector/deployment/gateway/)) per data center, diff --git a/content/en/blog/2023/exponential-histograms.md b/content/en/blog/2023/exponential-histograms.md index 0bfb3eef5671..c402f41d590b 100644 --- a/content/en/blog/2023/exponential-histograms.md +++ b/content/en/blog/2023/exponential-histograms.md @@ -198,5 +198,4 @@ _A version of this article was [originally posted][] to the author's blog._ /docs/specs/otel/metrics/sdk/#base2-exponential-bucket-histogram-aggregation [Why Histograms?]: ../why-histograms/ [Histograms vs Summaries]: ../histograms-vs-summaries/ - -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2023/histograms-vs-summaries/index.md b/content/en/blog/2023/histograms-vs-summaries/index.md index 8c9df8907efe..8ebc07463478 100644 --- a/content/en/blog/2023/histograms-vs-summaries/index.md +++ b/content/en/blog/2023/histograms-vs-summaries/index.md @@ -110,4 +110,4 @@ Until then, here are some talks I found helpful: _A version of this article was [originally posted][] to the author's blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2023/lambda-release.md b/content/en/blog/2023/lambda-release.md index 018c404cc1c2..85ffef589ba9 100644 --- a/content/en/blog/2023/lambda-release.md +++ b/content/en/blog/2023/lambda-release.md @@ -9,8 +9,8 @@ cSpell:ignore: adot otel-faas socha The [Functions-as-a-Service (FaaS) SIG](https://docs.google.com/document/d/187XYoQcXQ9JxS_5v2wvZ0NEysaJ02xoOYNXj08pT0zc) is incredibly excited to announce that the release of OpenTelemetry Lambda -layers, and associated [documentation](/docs/platforms/faas/) on how to monitor Amazon Web -Services (AWS) Lambdas. +layers, and associated [documentation](/docs/platforms/faas/) on how to monitor +Amazon Web Services (AWS) Lambdas. ## OTel FaaS repackaged diff --git a/content/en/blog/2023/opamp-status/index.md b/content/en/blog/2023/opamp-status/index.md index 51847b6a1a54..9beb3dfd6de5 100644 --- a/content/en/blog/2023/opamp-status/index.md +++ b/content/en/blog/2023/opamp-status/index.md @@ -105,8 +105,8 @@ with a backlog of issues created to guide further development. ## OpAMP in Kubernetes In OTel we have dedicated support for Kubernetes as a compute platform via the -[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/). In this -context, we're also working on OpAMP support in Kubernetes which will be +[OpenTelemetry Operator for Kubernetes](/docs/platforms/kubernetes/operator/). +In this context, we're also working on OpAMP support in Kubernetes which will be available through a [bridge component](https://docs.google.com/document/d/1M8VLNe_sv1MIfu5bUR5OV_vrMBnAI7IJN-7-IAr37JY/) to be deployed by the OpenTelemetry Operator: diff --git a/content/en/blog/2023/why-histograms/index.md b/content/en/blog/2023/why-histograms/index.md index c3c265b6e006..a1207c9c2b6b 100644 --- a/content/en/blog/2023/why-histograms/index.md +++ b/content/en/blog/2023/why-histograms/index.md @@ -93,4 +93,4 @@ avoid these subtle problems if they apply to you. _A version of this article was [originally posted][] to the author's blog._ -[originally posted]: {{% param canonical_url %}} +[originally posted]: <{{% param canonical_url %}}> diff --git a/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md b/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md index 86075446176c..be461be26602 100644 --- a/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md +++ b/content/en/blog/2024/collecting-otel-compliant-java-logs-from-files/index.md @@ -205,7 +205,7 @@ OTLP/JSON format, with a JSON object per line. The log records are nested in the ## Configure the Collector to ingest the OTLP/JSON logs -{{< figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink="https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a" >}} +{{< figure class="figure" src="otel-collector-otlpjson-pipeline.png" attr="View OTel Collector pipeline with OTelBin" attrlink=`https://www.otelbin.io/s/69739d790cf279c203fc8efc86ad1a876a2fc01a` >}} ```yaml # tested with otelcol-contrib v0.112.0 diff --git a/content/en/blog/2025/otel-mainframe-priorities-survey.md b/content/en/blog/2025/otel-mainframe-priorities-survey.md index ea71aed115f6..01bd71819346 100644 --- a/content/en/blog/2025/otel-mainframe-priorities-survey.md +++ b/content/en/blog/2025/otel-mainframe-priorities-survey.md @@ -63,6 +63,5 @@ OpenTelemetry on Mainframe SIG, join the conversation at _A version of this article was [originally posted] on the Open Mainframe Project blog._ -[originally posted]: {{% param canonical_url %}} - +[originally posted]: <{{% param canonical_url %}}> [survey]: https://www.surveymonkey.com/r/HGTD2KJ diff --git a/content/en/docs/collector/building/receiver.md b/content/en/docs/collector/building/receiver.md index 011ab8c351f4..83e835ce18f4 100644 --- a/content/en/docs/collector/building/receiver.md +++ b/content/en/docs/collector/building/receiver.md @@ -279,8 +279,8 @@ type Config struct { Now that you have access to the settings, you can provide any kind of validation needed for those values by implementing the `Validate` method according to the optional -[ConfigValidator](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/component/config.go#L50) interface. +[ConfigValidator]() +interface. In this case, the `interval` value will be optional (we will look at generating default values later) but when defined should be at least 1 minute (1m) and the @@ -330,18 +330,18 @@ func (cfg *Config) Validate() error { If you want to take a closer look at the structs and interfaces involved in the configuration aspects of a component, take a look at the -[component/config.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/component/config.go) file inside the Collector's GitHub project. +[component/config.go]() +file inside the Collector's GitHub project. ## Implementing the receiver.Factory interface The `tailtracer` receiver has to provide a `receiver.Factory` implementation, and although you will find a `receiver.Factory` interface (you can find its definition in the -[receiver/receiver.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/receiver/receiver.go#L58) file within the Collector's project), -the right way to provide the implementation is by using the functions available -within the `go.opentelemetry.io/collector/receiver` package. +[receiver/receiver.go]() +file within the Collector's project), the right way to provide the +implementation is by using the functions available within the +`go.opentelemetry.io/collector/receiver` package. Create a file named `factory.go`: @@ -595,9 +595,9 @@ func NewFactory() receiver.Factory { ## Implementing the receiver component All the receiver APIs are currently declared in the -[receiver/receiver.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/receiver/receiver.go) file within the Collector's project, open -the file and take a minute to browse through all the interfaces. +[receiver/receiver.go]() +file within the Collector's project, open the file and take a minute to browse +through all the interfaces. Notice that `receiver.Traces` (and its siblings `receiver.Metrics` and `receiver.Logs`) at this point in time, doesn't describe any specific methods @@ -1393,8 +1393,7 @@ creating a trace. You will start with a type called `ptrace.ResourceSpans` which represents the resource and all the operations that it either originated or received while participating in a trace. You can find its definition within the -[/pdata/internal/data/protogen/trace/v1/trace.pb.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/pdata/internal/data/protogen/trace/v1/trace.pb.go). +[/pdata/internal/data/protogen/trace/v1/trace.pb.go](). `ptrace.Traces` has a method named `ResourceSpans()` which returns an instance of a helper type called `ptrace.ResourceSpansSlice`. The @@ -1454,8 +1453,8 @@ pair format represented by the `pcommon.Map` type. You can check the definition of the `pcommon.Map` type and the related helper functions to create attribute values using the supported formats in the -[/pdata/pcommon/map.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/pdata/pcommon/map.go) file within the Collector's GitHub project. +[/pdata/pcommon/map.go]() +file within the Collector's GitHub project. Key/value pairs provide a lot of flexibility to help model your `Resource` data, so the OTel specification has some guidelines in place to help organize and @@ -1517,9 +1516,8 @@ convention to represent that information on its `Resource`. All the resource semantic convention attribute names and well known-values are kept within the -[/semconv/v1.9.0/generated_resource.go](https://github.com/open-telemetry/opentelemetry-collector/blob/v{{% -param vers %}}/semconv/v1.9.0/generated_resource.go) file within the Collector's -GitHub project. +[/semconv/v1.9.0/generated_resource.go]() +file within the Collector's GitHub project. Let's create a function to read the field values from an `BackendSystem` instance and write them as attributes into a `pcommon.Resource` instance. Open diff --git a/content/en/docs/contributing/issues.md b/content/en/docs/contributing/issues.md index bd6757211891..1f711309da48 100644 --- a/content/en/docs/contributing/issues.md +++ b/content/en/docs/contributing/issues.md @@ -33,9 +33,8 @@ One of the best ways to help make OTel docs better is to fix an existing issue. > process. {.mt-3} - - [good first issue]: {{% param _issue %}}%22good+first+issue%22 - [help wanted]: {{% param _issue %}}%3A%22help+wanted%22 + [good first issue]: <{{% param _issue %}}%22good+first+issue%22> + [help wanted]: <{{% param _issue %}}%3A%22help+wanted%22> [org]: https://github.com/open-telemetry {{% /alert %}} diff --git a/content/en/docs/demo/forking.md b/content/en/docs/demo/forking.md index e3f4930d5078..949ee6a07fdd 100644 --- a/content/en/docs/demo/forking.md +++ b/content/en/docs/demo/forking.md @@ -30,4 +30,4 @@ Live demos can be added to the demo If you have any questions or would like to suggest ways that we can make your life easier as a fork maintainer, please open an issue. -[demo repository]: {{% param repo %}} +[demo repository]: <{{% param repo %}}> diff --git a/content/en/docs/languages/cpp/exporters.md b/content/en/docs/languages/cpp/exporters.md index 6e7abe8bc90b..1ff1d2b126f4 100644 --- a/content/en/docs/languages/cpp/exporters.md +++ b/content/en/docs/languages/cpp/exporters.md @@ -353,7 +353,7 @@ void InitTracer() } ``` -{{% docs/languages/exporters/outro python "https://opentelemetry-cpp.readthedocs.io/en/latest/otel_docs/classopentelemetry_1_1sdk_1_1trace_1_1SpanExporter.html" %}} +{{% docs/languages/exporters/outro python `https://opentelemetry-cpp.readthedocs.io/en/latest/otel_docs/classopentelemetry_1_1sdk_1_1trace_1_1SpanExporter.html` %}} {{< tabpane text=true >}} {{% tab Batch %}} diff --git a/content/en/docs/languages/java/intro.md b/content/en/docs/languages/java/intro.md index b13717564c1f..99fecd75167b 100644 --- a/content/en/docs/languages/java/intro.md +++ b/content/en/docs/languages/java/intro.md @@ -168,17 +168,10 @@ dependencies { {{% /tab %}} {{< /tabpane >}} [opentelemetry-bom]: -https://repo1.maven.org/maven2/io/opentelemetry/opentelemetry-bom/{{% param -vers.otel %}}/opentelemetry-bom-{{% param vers.otel %}}.pom + [opentelemetry-bom-alpha]: -https://repo1.maven.org/maven2/io/opentelemetry/opentelemetry-bom-alpha/{{% -param vers.otel -%}}-alpha/opentelemetry-bom-alpha-{{% param vers.otel %}}-alpha.pom + [opentelemetry-instrumentation-bom]: -https://repo1.maven.org/maven2/io/opentelemetry/instrumentation/opentelemetry-instrumentation-bom/{{% -param vers.instrumentation -%}}/opentelemetry-instrumentation-bom-{{% param vers.instrumentation %}}.pom + [opentelemetry-instrumentation-alpha-bom]: -https://repo1.maven.org/maven2/io/opentelemetry/instrumentation/opentelemetry-instrumentation-bom-alpha/{{% -param vers.instrumentation -%}}-alpha/opentelemetry-instrumentation-bom-alpha-{{% param vers.instrumentation %}}-alpha.pom + diff --git a/content/en/docs/languages/js/exporters.md b/content/en/docs/languages/js/exporters.md index e4d74225b128..dbac8c823bcf 100644 --- a/content/en/docs/languages/js/exporters.md +++ b/content/en/docs/languages/js/exporters.md @@ -345,7 +345,7 @@ const sdk = new opentelemetry.NodeSDK({ {{% /tab %}} {{< /tabpane >}} -{{% docs/languages/exporters/outro js "https://open-telemetry.github.io/opentelemetry-js/interfaces/_opentelemetry_sdk_trace_base.SpanExporter.html" %}} +{{% docs/languages/exporters/outro js `https://open-telemetry.github.io/opentelemetry-js/interfaces/_opentelemetry_sdk_trace_base.SpanExporter.html` %}} {{< tabpane text=true >}} {{% tab TypeScript %}} diff --git a/content/en/docs/languages/python/exporters.md b/content/en/docs/languages/python/exporters.md index c299c4465b88..0434854e9525 100644 --- a/content/en/docs/languages/python/exporters.md +++ b/content/en/docs/languages/python/exporters.md @@ -306,7 +306,7 @@ trace.set_tracer_provider(provider) {{% /tab %}} {{< /tabpane >}} -{{% docs/languages/exporters/outro python "https://opentelemetry-python.readthedocs.io/en/latest/sdk/trace.export.html#opentelemetry.sdk.trace.export.SpanExporter" %}} +{{% docs/languages/exporters/outro python `https://opentelemetry-python.readthedocs.io/en/latest/sdk/trace.export.html#opentelemetry.sdk.trace.export.SpanExporter` %}} ```python from opentelemetry.exporter.otlp.proto.grpc.trace_exporter import OTLPSpanExporter diff --git a/content/ja/docs/demo/forking.md b/content/ja/docs/demo/forking.md index 252c035e74ff..a238eca7e6e6 100644 --- a/content/ja/docs/demo/forking.md +++ b/content/ja/docs/demo/forking.md @@ -22,4 +22,4 @@ default_lang_commit: 99b15da7137cde4a6352576768f4c9203170d569 フォークメンテナーとしての作業をより容易にする方法についての質問や提案がありましたら、イシューを作成してください。 -[demo repository]: {{% param repo %}} +[demo repository]: <{{% param repo %}}> diff --git a/package.json b/package.json index 3ad92bb8b564..cb2a538a507f 100644 --- a/package.json +++ b/package.json @@ -54,6 +54,7 @@ "check:links:internal": "npm run _check:links:internal", "check:links": "npm run _check:links", "check:markdown": "scripts/check-markdown-wrapper.sh", + "check:markdown2": "npx markdownlint-cli2 'content/**/*.md' '*.md'", "check:registry": "npm run _check:registry -- ", "check:spelling": "npx cspell --no-progress -c .cspell.yml content data 'layouts/**/*.md'", "check:text": "npm run _check:text -- ", @@ -116,9 +117,9 @@ "@cspell/dict-es-es": "^3.0.3", "@cspell/dict-fr-fr": "^2.2.5", "@cspell/dict-pt-br": "^2.3.3", + "ajv": "^8.17.1", "ajv-errors": "^3.0.0", "ajv-formats": "^3.0.1", - "ajv": "^8.17.1", "autoprefixer": "^10.4.20", "cspell": "^8.17.3", "gulp": "^5.0.0", @@ -126,14 +127,15 @@ "js-yaml": "^4.1.0", "markdown-link-check": "^3.13.6", "markdownlint": "^0.37.4", + "markdownlint-cli2": "^0.17.2", "postcss-cli": "^11.0.0", "prettier": "3.4.2", "puppeteer": "^24.2.0", "require-dir": "^1.2.0", + "textlint": "^14.4.2", "textlint-filter-rule-allowlist": "^4.0.0", "textlint-filter-rule-comments": "^1.2.2", "textlint-rule-terminology": "^5.2.12", - "textlint": "^14.4.2", "through2": "^4.0.2", "yargs": "^17.7.2" }, @@ -147,11 +149,11 @@ "@opentelemetry/resources": "^1.30.1", "@opentelemetry/sdk-trace-base": "^1.30.1", "@opentelemetry/sdk-trace-web": "^1.30.1", - "@opentelemetry/semantic-conventions": "^1.28.0", + "@opentelemetry/semantic-conventions": "^1.29.0", "path": "^0.12.7" }, "optionalDependencies": { - "netlify-cli": "^18.0.3", + "netlify-cli": "^18.0.4", "npm-check-updates": "^17.1.14" }, "enginesComment": "Ensure that engines.node value stays consistent with the project's .nvmrc",