Skip to content

Commit 01bce6a

Browse files
opentelemetrybotopentelemetrybot
committed
Merge remote-tracking branch 'origin/main' into opentelemetrybot/semconv-integration-v1.31.0-dev
2 parents b2aa2d6 + 0642571 commit 01bce6a

File tree

12 files changed

+1156
-1173
lines changed

12 files changed

+1156
-1173
lines changed

‎.htmltest.yml

+3-15
Original file line numberDiff line numberDiff line change
@@ -44,23 +44,11 @@ IgnoreURLs: # list of regexs of paths or URLs to be ignored
4444
- ^https://pdf.sciencedirectassets.com/280203/1-s2.0-S1877050919X0006X/1-s2.0-S1877050919303576/main.pdf\?
4545

4646
# Sites that deny access, always yielding 401, 403 Forbidden, 406, or other:
47-
- ^https://(www\.)?linkedin\.com\b # 999 Request Denied
48-
- ^https://(www\.)?mvnrepository\.com
49-
- ^https://(www\.|eng\.)?uber\.com/(blog|flipr)/ # 406
50-
- ^https://kofo.dev
51-
- ^https://platform.openai.com
52-
- ^https://openai.com
53-
- ^https://star-history.com
47+
- ^https://platform.openai.com # Really hard to trick into giving a 200 when using a script; manually verify links
48+
- ^https://star-history.com # link contain ampersands in URL anchor part, which htmltest escapes, so it's not found
5449
- ^https://twitter.com
55-
- ^https://www.chathamhouse.org
56-
- ^https://www.farfetch.com
57-
- ^https://www.zocdoc.com
50+
- ^https://www.youtube.com/playlist\?list= # htmltest doesn't process query parameters
5851
- ^https://x.com
59-
- ^https://maven.org
60-
# OTel Google calendar - curl returns 200, but the link checker gets a 401:
61-
- ^https://calendar.google.com/calendar/embed\?src=google.com_b79e3e90j7bbsa2n2p5an5lf60%40group.calendar.google.com
62-
# YouTube playlists sometimes give a 404, although they give a 200 when accessed via browser:
63-
- ^https://www.youtube.com/playlist\?list=
6452

6553
# Ignore Docsy-generated GitHub links for now, until
6654
# https://github.com/google/docsy/issues/1432 is fixed

‎content/en/blog/2025/otel-mainframe-priorities-survey.md

+68
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,68 @@
1+
---
2+
title: OpenTelemetry on Mainframe Priorities Survey
3+
linkTitle: Mainframe Priorities Survey
4+
date: 2025-01-31
5+
author: '[Ruediger Schulze](https://github.com/rrschulze) (IBM)'
6+
canonical_url: https://openmainframeproject.org/blog/opentelemetry-on-mainframe-priorities-survey/
7+
issue: https://github.com/open-telemetry/opentelemetry.io/issues/6045
8+
sig: SIG OpenTelemetry on Mainframe
9+
cSpell:ignore: Ruediger Schulze
10+
---
11+
12+
The [OpenTelemetry](/) project and
13+
[The Open Mainframe Project](https://openmainframeproject.org/) established the
14+
[SIG “OpenTelemetry on Mainframe”](https://github.com/open-telemetry/sig-mainframe)
15+
at the beginning of 2024. Our focus is to enable OpenTelemetry on the mainframe
16+
for improved end-to-end observability and to support mainframe participation in
17+
hybrid cloud applications. **The SIG launched a new [survey] that calls for your
18+
participation.**
19+
20+
## Background
21+
22+
While there are many definitions of observability, we will refer here to the
23+
ability to receive actionable insight about the behavior of hybrid applications
24+
spanning multiple landing zones such as public and private cloud and mainframe
25+
environments.
26+
27+
OpenTelemetry is a well-adopted open source framework for observability that
28+
aims to make high quality telemetry data such as traces, metrics, and logs
29+
available from any source to any target. OpenTelemetry remains the second most
30+
active project under the Cloud Native Computing Foundation (CNCF). The community
31+
of the OpenTelemetry project has made major efforts to provide specifications
32+
and implementations that unify the collection, processing, and distribution of
33+
telemetry.
34+
35+
Given the breadth of the OpenTelemetry project and sophisticated capabilities of
36+
the mainframe, we as contributors to the SIG want to better understand the
37+
priorities for making the best use of OpenTelemetry on the mainframes. We seek
38+
feedback from a broad range of mainframe users and users of observability
39+
solutions, developers, site reliability engineers, application owners,
40+
architects, DevOps engineers, and all other experts in the field.
41+
42+
The results of the [survey] will help us prioritize and implement targeted
43+
activities to accelerate the adoption of OpenTelemetry on the mainframe
44+
platform. Such activities could be the expedited porting of selected SDKs for
45+
code instrumentation to z/OS or the definition of Semantic Conventions for
46+
specific aspects of the platform. Once the survey is complete, we will publish
47+
the results and a prioritized list of activities on the websites of the
48+
OpenTelemetry project and The Open Mainframe Project.
49+
50+
## Taking the survey
51+
52+
The [survey] is structured in two sections. The first section gathers input
53+
about your role and background. The second section gathers the priorities of
54+
your organization for enabling OpenTelemetry on mainframes. Responding to the 20
55+
questions will take approximately 15 minutes. We appreciate your time spent on
56+
the survey and look forward to receiving your feedback!
57+
58+
We invite you to take the [survey]. To learn more about the work of the
59+
OpenTelemetry on Mainframe SIG, join the conversation at
60+
[#otel-mainframes](https://cloud-native.slack.com/archives/C05PXDFTCPJ) on
61+
[CNCF Slack](https://slack.cncf.io/).
62+
63+
_A version of this article was [originally posted] on the Open Mainframe Project
64+
blog._
65+
66+
[originally posted]: {{% param canonical_url %}}
67+
68+
[survey]: https://www.surveymonkey.com/r/HGTD2KJ

‎content/en/docs/languages/java/api.md

+1-2
Original file line numberDiff line numberDiff line change
@@ -912,8 +912,7 @@ The instrument APIs have share a variety of features:
912912
- Record values which are `long` or `double`, which is configured via the
913913
builder.
914914

915-
See
916-
[metric guidelines](http://localhost:1313/docs/specs/semconv/general/metrics/#general-guidelines)
915+
See [metric guidelines](/docs/specs/semconv/general/metrics/#general-guidelines)
917916
for details on metric naming and units.
918917

919918
See

‎content/pt/docs/languages/sdk-configuration/_index.md

+14
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,14 @@
1+
---
2+
title: Configurações de SDK
3+
linkTitle: SDK Config
4+
aliases: [/docs/concepts/sdk-configuration]
5+
redirects: [{ from: /docs/concepts/sdk-configuration/*, to: ':splat' }]
6+
weight: 1
7+
default_lang_commit: 3e474f0f2a7976bf2637b12dab240ed84c1712b7
8+
---
9+
10+
Os SDKs do OpenTelemetry oferecem suporte à configuração em cada linguagem e por
11+
meio de variáveis de ambiente. As páginas a seguir descrevem as variáveis de
12+
ambiente que você pode usar para configurar seu SDK. Valores definidos com
13+
variáveis de ambiente substituem a configuração equivalente no código usando as
14+
APIs do SDK.

‎content/pt/docs/languages/sdk-configuration/general.md

+194
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,194 @@
1+
---
2+
title: Configurações gerais de SDK
3+
linkTitle: Geral
4+
aliases: [general-sdk-configuration]
5+
cSpell:ignore: ottrace
6+
default_lang_commit: 1e4970e9193c8af1d1f9b86901b13492071aecc7
7+
---
8+
9+
{{% alert title="Nota" color="info" %}}
10+
11+
O suporte a variáveis de ambiente é opcional. Para informações detalhadas sobre
12+
quais variáveis de ambiente cada implementação de linguagem suporta, consulte a
13+
[Matriz de Conformidade de Implementação](https://github.com/open-telemetry/opentelemetry-specification/blob/main/spec-compliance-matrix.md#environment-variables).
14+
15+
{{% /alert %}}
16+
17+
## `OTEL_SERVICE_NAME`
18+
19+
Define o valor do atributo de recurso
20+
[`service.name`](/docs/specs/semconv/resource/#service).
21+
22+
**Valor padrão:** `"unknown_service"`
23+
24+
Se `service.name` também for fornecido em `OTEL_RESOURCE_ATTRIBUTES`, então
25+
`OTEL_SERVICE_NAME` terá precedência.
26+
27+
**Exemplo:**
28+
29+
`export OTEL_SERVICE_NAME="your-service-name"`
30+
31+
## `OTEL_RESOURCE_ATTRIBUTES`
32+
33+
Pares de chave-valor que serão utilizados como atributos de recurso. Consulte a
34+
página de
35+
[Recurso do SDK](/docs/specs/otel/resource/sdk#specifying-resource-information-via-an-environment-variable)
36+
para mais detalhes.
37+
38+
**Valor padrão:** Vazio.
39+
40+
Consulte a página
41+
[convenção semântica de Recursos](/docs/specs/semconv/resource/#semantic-attributes-with-sdk-provided-default-value)
42+
para obter informações sobre as convenções semânticas a serem seguidas para
43+
tipos de recursos comuns.
44+
45+
**Exemplo:**
46+
47+
`export OTEL_RESOURCE_ATTRIBUTES="key1=value1,key2=value2"`
48+
49+
## `OTEL_TRACES_SAMPLER`
50+
51+
Especifica o Sampler utilizado pelo SDK para realizar amostragem de rastros.
52+
53+
**Valor padrão:** `"parentbased_always_on"`
54+
55+
**Exemplo:**
56+
57+
`export OTEL_TRACES_SAMPLER="traceidratio"`
58+
59+
Os valores aceitos para `OTEL_TRACES_SAMPLER` são:
60+
61+
- `"always_on"`: `AlwaysOnSampler`
62+
- `"always_off"`: `AlwaysOffSampler`
63+
- `"traceidratio"`: `TraceIdRatioBased`
64+
- `"parentbased_always_on"`: `ParentBased(root=AlwaysOnSampler)`
65+
- `"parentbased_always_off"`: `ParentBased(root=AlwaysOffSampler)`
66+
- `"parentbased_traceidratio"`: `ParentBased(root=TraceIdRatioBased)`
67+
- `"parentbased_jaeger_remote"`: `ParentBased(root=JaegerRemoteSampler)`
68+
- `"jaeger_remote"`: `JaegerRemoteSampler`
69+
- `"xray"`:
70+
[AWS X-Ray Centralized Sampling](https://docs.aws.amazon.com/xray/latest/devguide/xray-console-sampling.html)
71+
(_terceiro_)
72+
73+
## `OTEL_TRACES_SAMPLER_ARG`
74+
75+
Especifica os argumentos, se aplicável, para o Sampler definido em
76+
`OTEL_TRACES_SAMPLER`. O valor especificado será utilizado apenas se
77+
`OTEL_TRACES_SAMPLER` for definido. Cada tipo de Sampler define sua própria
78+
entrada esperada, se houver. Entradas inválidas ou não reconhecidas são
79+
registradas como erro.
80+
81+
**Valor padrão:** Vazio.
82+
83+
**Exemplo:**
84+
85+
```shell
86+
export OTEL_TRACES_SAMPLER="traceidratio"
87+
export OTEL_TRACES_SAMPLER_ARG="0.5"
88+
```
89+
90+
Dependendo do valor definido em `OTEL_TRACES_SAMPLER`, a definição de
91+
`OTEL_TRACES_SAMPLER_ARG` pode ocorrer da seguinte maneira:
92+
93+
- Para os Samplers `traceidratio` e `parentbased_traceidratio`: Probabilidade de
94+
amostragem, um número no intervalo [0..1], por exemplo, "0.25". Caso não seja
95+
definido, o valor padrão é 1.0.
96+
- Para `jaeger_remote` e `parentbased_jaeger_remote`: O valor é uma lista
97+
separada por vírgulas:
98+
- Exemplo:
99+
`"endpoint=http://localhost:14250,pollingIntervalMs=5000,initialSamplingRate=0.25"`
100+
- `endpoint`: A rota em formato `scheme://host:port` do servidor gRPC que
101+
fornece a estratégia de amostragem para o serviço
102+
([sampling.proto](https://github.com/jaegertracing/jaeger-idl/blob/main/proto/api_v2/sampling.proto)).
103+
- `pollingIntervalMs`: em milissegundos, indicando com que frequência o
104+
Sampler consultará o _backend_ para atualizações na estratégia de
105+
amostragem.
106+
- `initialSamplingRate`: no intervalo [0..1], utilizado como valor da
107+
probabilidade de amostragem caso não seja possível recuperar a estratégia de
108+
amostragem no _backend_. Este valor perde efeito assim que uma estratégia de
109+
amostragem é recuperada com sucesso, então a estratégia remota será
110+
utilizada até que uma nova atualização seja obtida com sucesso.
111+
112+
## `OTEL_PROPAGATORS`
113+
114+
Especifica os Propagators a serem utilizados em uma lista separada por vírgulas.
115+
116+
**Valor padrão:** `"tracecontext,baggage"
117+
118+
**Exemplo:**
119+
120+
`export OTEL_PROPAGATORS="b3"`
121+
122+
Os valores aceitos para `OTEL_PROPAGATORS` são:
123+
124+
- `"tracecontext"`: [W3C Trace Context](https://www.w3.org/TR/trace-context/)
125+
- `"baggage"`: [W3C Baggage](https://www.w3.org/TR/baggage/)
126+
- `"b3"`: [B3 Single](/docs/specs/otel/context/api-propagators#configuration)
127+
- `"b3multi"`:
128+
[B3 Multi](/docs/specs/otel/context/api-propagators#configuration)
129+
- `"jaeger"`:
130+
[Jaeger](https://www.jaegertracing.io/docs/1.21/client-libraries/#propagation-format)
131+
- `"xray"`:
132+
[AWS X-Ray](https://docs.aws.amazon.com/xray/latest/devguide/xray-concepts.html#xray-concepts-tracingheader)
133+
(_terceiro_)
134+
- `"ottrace"`:
135+
[OT Trace](https://github.com/opentracing?q=basic&type=&language=)
136+
(_terceiro_)
137+
- `"none"`: Nenhum propagador configurado automaticamente.
138+
139+
## `OTEL_TRACES_EXPORTER`
140+
141+
Especifica qual Exporter é utilizado para os rastros. Dependendo da
142+
implementação, pode ser uma lista separada por vírgulas.
143+
144+
**Valor padrão:** `"otlp"`
145+
146+
**Exemplo:**
147+
148+
`export OTEL_TRACES_EXPORTER="jaeger"`
149+
150+
Os valores aceitos são:
151+
152+
- `"otlp"`: [OTLP][]
153+
- `"jaeger"`: exportar no modelo de dados Jaeger
154+
- `"zipkin"`: [Zipkin](https://zipkin.io/zipkin-api/)
155+
- `"console"`: [Saída Padrão](/docs/specs/otel/trace/sdk_exporters/stdout/)
156+
- `"none"`: Nenhum exportador de rastros configurado automaticamente.
157+
158+
## `OTEL_METRICS_EXPORTER`
159+
160+
Especifica qual Exporter é utilizado para as métricas. Dependendo da
161+
implementação, pode ser uma lista separada por vírgulas.
162+
163+
**Valor padrão:** `"otlp"`
164+
165+
**Exemplo:**
166+
167+
`export OTEL_METRICS_EXPORTER="prometheus"`
168+
169+
Os valores aceitos para `OTEL_METRICS_EXPORTER` são:
170+
171+
- `"otlp"`: [OTLP][]
172+
- `"prometheus"`:
173+
[Prometheus](https://github.com/prometheus/docs/blob/main/content/docs/instrumenting/exposition_formats.md)
174+
- `"console"`: [Saída Padrão](/docs/specs/otel/metrics/sdk_exporters/stdout/)
175+
- `"none"`: Nenhum exportador de métricas configurado automaticamente.
176+
177+
## `OTEL_LOGS_EXPORTER`
178+
179+
Especifica qual Exporter é utilizado para os logs. Dependendo da implementação,
180+
pode ser uma lista separada por vírgulas.
181+
182+
**Valor padrão:** `"otlp"`
183+
184+
**Exemplo:**
185+
186+
`export OTEL_LOGS_EXPORTER="otlp"`
187+
188+
Os valores aceitos para `OTEL_LOGS_EXPORTER` são:
189+
190+
- `"otlp"`: [OTLP][]
191+
- `"console"`: [Saída Padrão](/docs/specs/otel/logs/sdk_exporters/stdout/)
192+
- `"none"`: Nenhum exportador de logs configurado automaticamente.
193+
194+
[otlp]: /docs/specs/otlp/

0 commit comments

Comments
 (0)