Skip to content

docs(monitoring): recommend OpenTelemetry, mark observability plugin legacy - #629

Closed
mrusan wants to merge 1 commit into
spinnaker:masterfrom
armory-io:otel
Closed

docs(monitoring): recommend OpenTelemetry, mark observability plugin legacy#629
mrusan wants to merge 1 commit into
spinnaker:masterfrom
armory-io:otel

Conversation

@mrusan

@mrusan mrusan commented Jul 27, 2026

Copy link
Copy Markdown
Contributor
  • Document the OpenTelemetry Java agent as the recommended way to collect Spinnaker metrics and traces, including how the agent's Micrometer bridge reaches the registry that Spectator wraps.

  • Mark the Spinnaker Observability Plugin as legacy while retaining its New Relic registry as a compatibility option. Note the plugin version to Spinnaker version mapping for existing users.

  • Clarify that New Relic's OpenTelemetry API support does not automatically export Spinnaker's Micrometer meters, the two Java agents cannot share a JVM, and the OpenTelemetry path provides broad but non-identical APM coverage.

…legacy

Document the OpenTelemetry Java agent as the recommended way to collect
Spinnaker metrics and traces, including how the agent's Micrometer bridge
reaches the registry that Spectator wraps.

Mark the Spinnaker Observability Plugin as legacy while retaining its New
Relic registry as a compatibility option. Note the plugin version to
Spinnaker version mapping for existing users.

Clarify that New Relic's OpenTelemetry API support does not automatically
export Spinnaker's Micrometer meters, the two Java agents cannot share a JVM,
and the OpenTelemetry path provides broad but non-identical APM coverage.
@mrusan

mrusan commented Jul 30, 2026

Copy link
Copy Markdown
Contributor Author

#632

@mrusan mrusan closed this Jul 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant