elastic/elasticsearch

Add X-Opaque-Id to root level application.log

Open

#51,451 opened on Jan 24, 2020

View on GitHub
 (4 comments) (1 reaction) (0 assignees)Java (76,700 stars) (25,882 forks)batch import
:Core/Infra/LoggingTeam:Core/Infrahelp wantedtriaged

Description

In #31521 X-Opaque-Id was added to access logs and slow logs. It would be very useful for investigation if whenever Elasticsearch throws an exception, X-Opaque-Id is appended to the exception log which locates at root level application.log.

Contributor guide

Tech stack
java
Domain
backendobservability
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
familiarity with Elasticsearch loggingunderstanding of X Opaque Id
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60
Research direction
The goal is to include X Opaque Id in exception logs at the root application.log level. Refer to issue #31521 which added it to access logs and slow logs. Investigate where Elasticsearch throws exceptions and logs them, likely in the main logging framework (Log4j2). Find the relevant log statements and add X Opaque Id from the thread context to those log messages. Ensure consistency with existing implementation. No linked PRs or assignees; the issue is open for contribution.