Abhinav Chandel created ATLAS-5292:
--------------------------------------
Summary: Add optional OpenTelemetry Java agent with Prometheus
metrics export
Key: ATLAS-5292
URL: https://issues.apache.org/jira/browse/ATLAS-5292
Project: Atlas
Issue Type: New Feature
Components: atlas-core, atlas-ci-build, atlas-docker
Affects Versions: 2.4.0
Reporter: Abhinav Chandel
Assignee: Abhinav Chandel
This work adds an optional OpenTelemetry Java auto-instrumentation agent to the
Atlas server. When enabled, it emits runtime and JVM telemetry (for example
process/uptime, memory pools, GC, threads, class loading, and standard HTTP
server request metrics for instrumented stacks) and exposes them via the
agent’s Prometheus exporter for scraping. Atlas does not introduce custom
Atlas-specific metric names in this change; metrics come from the agent’s
default instrumentations plus the JVM/runtime instrumentations bundled with the
agent.
The feature is opt-in: operators turn it on with configuration (environment
variables in Docker, or the equivalent exports in atlas-env.sh / the process
environment for non-Docker installs). When enabled, the Atlas server process is
started with the OpenTelemetry Java agent on the classpath and Prometheus
exporter settings applied via standard JVM system properties so metrics are
exposed on a configurable host and port.
The agent JAR is delivered with the Atlas distribution as part of the web
application packaging so a separate download is not required for the default
path. Container images and Compose metadata can pass the same variables and
publish the metrics port when observability is desired. Default behavior
remains unchanged when the feature flag is off—no agent, no extra listener.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
