Browse Source

Refer to OTLP instead of OpenTelemetry

Closes gh-43727
pull/43904/head
Andy Wilkinson 12 months ago
parent
commit
7754b2e450
  1. 8
      spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/metrics.adoc

8
spring-boot-project/spring-boot-docs/src/docs/antora/modules/reference/pages/actuator/metrics.adoc

@ -507,10 +507,10 @@ Finally, you can take full control by defining your own javadoc:io.micrometer.ne @@ -507,10 +507,10 @@ Finally, you can take full control by defining your own javadoc:io.micrometer.ne
[[actuator.metrics.export.otlp]]
=== OpenTelemetry
=== OTLP
By default, metrics are exported to {url-micrometer-docs-implementations}/otlp[OpenTelemetry] running on your local machine.
You can provide the location of the https://opentelemetry.io/[OpenTelemetry metric endpoint] to use by using:
By default, metrics are exported over the {url-micrometer-docs-implementations}/otlp[OpenTelemetry protocol (OTLP)] to a consumer running on your local machine.
To export to another location, provide the location of the https://opentelemetry.io/[OTLP metrics endpoint] using configprop:management.otlp.metrics.export.url[]:
[configprops,yaml]
----
@ -521,6 +521,8 @@ management: @@ -521,6 +521,8 @@ management:
url: "https://otlp.example.com:4318/v1/metrics"
----
Custom headers, for example for authentication, can also be provided using configprop:management.otlp.metrics.export.headers.*[] properties.
[[actuator.metrics.export.prometheus]]

Loading…
Cancel
Save