[HN Gopher] Using the "X-AMZN-Trace-Id" Header for Request Traci...
       ___________________________________________________________________
        
       Using the "X-AMZN-Trace-Id" Header for Request Tracing Through AWS
       Load Balancer
        
       Author : rmason
       Score  : 44 points
       Date   : 2021-05-26 18:35 UTC (4 hours ago)
        
 (HTM) web link (www.bennadel.com)
 (TXT) w3m dump (www.bennadel.com)
        
       | wdb wrote:
       | Have a look at this propagator from Opentelemetry:
       | https://github.com/open-telemetry/opentelemetry-go-contrib/b...
       | 
       | If you extract this trace id and use it as your request id you
       | can follow it from the load balancer all the way to the end.
        
       | booleanbetrayal wrote:
       | I recently implemented support for this in the prometheus-
       | exporter gem.
       | 
       | https://github.com/discourse/prometheus_exporter/pull/150
       | 
       | What's annoying about the encoded time value is version 1 (the
       | only version still) is in seconds precision. Makes the value non-
       | viable for any sort of queue time metric. Better than nothing,
       | but would have been nice if it were micro.
        
       | Spivak wrote:
       | I think this the AWS docs explain this fairly well.
       | 
       | https://docs.aws.amazon.com/elasticloadbalancing/latest/appl...
       | 
       | The format for the field is                    X-Amzn-Trace-Id:
       | Field=version-time-id
       | 
       | and you're allowed to add custom fields that don't follow this
       | format and they will be preserved.
        
       ___________________________________________________________________
       (page generated 2021-05-26 23:00 UTC)