File tree Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Expand file tree Collapse file tree 1 file changed +6
-3
lines changed Original file line number Diff line number Diff line change 22
22
//! * `otel.name`: Override the span name sent to OpenTelemetry exporters.
23
23
//! Setting this field is useful if you want to display non-static information
24
24
//! in your span name.
25
- //! * `otel.kind`: Set the span kind to one of the supported OpenTelemetry [span kinds].
25
+ //! * `otel.kind`: Set the span kind to one of the supported OpenTelemetry [span kinds]. These must
26
+ //! be specified as strings such as `"client"` or `"server"`. If it is not specified, the span is
27
+ //! assumed to be internal.
26
28
//! * `otel.status_code`: Set the span status code to one of the supported OpenTelemetry [span status codes].
27
- //! * `otel.status_message`: Set the span status message.
29
+ //! * `otel.status_description`: Set the span description of the status. This should be used only if
30
+ //! `otel.status_code` is also set.
28
31
//!
29
32
//! [span kinds]: opentelemetry::trace::SpanKind
30
33
//! [span status codes]: opentelemetry::trace::Status
33
36
//!
34
37
//! OpenTelemetry defines conventional names for attributes of common
35
38
//! operations. These names can be assigned directly as fields, e.g.
36
- //! `trace_span!("request", "otel.kind " = %SpanKind::Client , "url.full" = ..)`, and they
39
+ //! `trace_span!("request", "server.port " = 80 , "url.full" = ..)`, and they
37
40
//! will be passed through to your configured OpenTelemetry exporter. You can
38
41
//! find the full list of the operations and their expected field names in the
39
42
//! [semantic conventions] spec.
You can’t perform that action at this time.
0 commit comments