Skip to content

Use Level::ERROR for all tracing spans#24

Merged
jorajeev merged 1 commit into
awslabs:mainfrom
jamesbornholt:tracing-level
May 26, 2021
Merged

Use Level::ERROR for all tracing spans#24
jorajeev merged 1 commit into
awslabs:mainfrom
jamesbornholt:tracing-level

Conversation

@jamesbornholt

Copy link
Copy Markdown
Member

The level of the span determines when it will be included in tracing output:
a span at level TRACE will only be included in messages at level TRACE, a span
at level INFO will be included in messages at level INFO or lower, etc. So we
want to put these spans at level ERROR to include them in all output. The
idea is that Shuttle users can use e.g. tracing::info! in their program to
debug, and those messages will include the span info (most importantly, the
task ID) from Shuttle.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

The level of the span determines when it will be included in tracing output:
a span at level TRACE will only be included in messages at level TRACE, a span
at level INFO will be included in messages at level INFO or lower, etc. So we
want to put these spans at level ERROR to include them in *all* output. The
idea is that Shuttle users can use e.g. `tracing::info!` in their program to
debug, and those messages will include the span info (most importantly, the
task ID) from Shuttle.
@jamesbornholt jamesbornholt requested a review from jorajeev May 26, 2021 01:27
@jorajeev jorajeev merged commit ba014d6 into awslabs:main May 26, 2021
@jamesbornholt jamesbornholt deleted the tracing-level branch June 11, 2021 22:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants