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

Standardize TraceId/SpandId/TraceFlags field casing in log formats #1283

Commits on Dec 14, 2020

  1. Standardize TraceId/SpandId/TraceFlags field casing in log formats

    OTLP/JSON is currently using trace_id, span_id field naming. The snake case
    with underscores comes from Protobuf/JSON mapping rules.
    
    Elsewhere we were previously using traceid, spanid, traceflags without underscores.
    
    This changes standardizes field names to use underscores for all text log mediums
    where these fields may be recorded.
    
    Note: the alternate approach, i.e. keeping traceid, spanid, traceflags and renaming
    them in OTLP/JSON would result in OTLP/JSON format having an inconsistent naming,
    since all other fields use snake casing.
    tigrannajaryan committed Dec 14, 2020
    Configuration menu
    Copy the full SHA
    32915b0 View commit details
    Browse the repository at this point in the history