Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: run dns resolution in the same tracing-span as the caller #134

Merged
merged 5 commits into from
Aug 7, 2024

Commits on Jul 3, 2024

  1. fix: run dns resolution in the same tracing-span as the caller

    This makes it possible to trace the entire request, including DNS
    resolution.
    
    The use case for this is to be able to suppress specific requests from
    being traced in a situation where the request is used to transmit logs
    to a remote server. This would result in an infinite loop of logs being
    sent to the remote server. tokio-rs/tokio#6659
    has more details.
    joshka committed Jul 3, 2024
    Configuration menu
    Copy the full SHA
    2f77b84 View commit details
    Browse the repository at this point in the history

Commits on Jul 18, 2024

  1. Configuration menu
    Copy the full SHA
    9087273 View commit details
    Browse the repository at this point in the history

Commits on Jul 19, 2024

  1. Configuration menu
    Copy the full SHA
    0f690ae View commit details
    Browse the repository at this point in the history

Commits on Aug 6, 2024

  1. Configuration menu
    Copy the full SHA
    2bce070 View commit details
    Browse the repository at this point in the history
  2. remove tracing from example

    joshka committed Aug 6, 2024
    Configuration menu
    Copy the full SHA
    5f7432e View commit details
    Browse the repository at this point in the history