TraceSight
Investigate distribution requests with session context
Follow a specific request across configured services, inspect the evidence, and share a reproducible finding with the team responsible for the fix.
A reviewable investigation
01
Choose a request
Bring a trace ID from a search, availability, or booking issue.
02
Inspect the chain
Review service logs and request context for each configured hop.
03
Confirm the cause
Compare findings with source evidence and agree on a fix with the owner.
Procurement view
What to check when evaluating diagnostics
Ask for a demonstration using a real request to inspect trace coverage, evidence, and access control.
Can one request be reconstructed
Session context can support search and booking investigations.
Provide a real traceId and inspect the timeline and per-hop latency.
Is the supplier raw response visible
Raw-payload access depends on deployment configuration and permissions.
Inspect one real incident with an authorized account and check retention policy.
Frequently asked questions
What does TraceSight help investigate?
TraceSight helps teams inspect a distribution request using its trace ID, service logs, and relevant session context. The available view depends on the services and logging configured for the environment.
How do we validate a diagnosis?
Start from a real search or booking trace, compare each hop with the source logs, and have the responsible team confirm the suspected cause before changing production settings.