parent
							
								
									91c0e23c64
								
							
						
					
					
						commit
						7754b2e450
					
				| 
						 | 
					@ -507,10 +507,10 @@ Finally, you can take full control by defining your own javadoc:io.micrometer.ne
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					
 | 
				
			||||||
[[actuator.metrics.export.otlp]]
 | 
					[[actuator.metrics.export.otlp]]
 | 
				
			||||||
=== OpenTelemetry
 | 
					=== OTLP
 | 
				
			||||||
 | 
					
 | 
				
			||||||
By default, metrics are exported to {url-micrometer-docs-implementations}/otlp[OpenTelemetry] running on your local machine.
 | 
					By default, metrics are exported over the {url-micrometer-docs-implementations}/otlp[OpenTelemetry protocol (OTLP)] to a consumer running on your local machine.
 | 
				
			||||||
You can provide the location of the https://opentelemetry.io/[OpenTelemetry metric endpoint] to use by using:
 | 
					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]
 | 
					[configprops,yaml]
 | 
				
			||||||
----
 | 
					----
 | 
				
			||||||
| 
						 | 
					@ -521,6 +521,8 @@ management:
 | 
				
			||||||
        url: "https://otlp.example.com:4318/v1/metrics"
 | 
					        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]]
 | 
					[[actuator.metrics.export.prometheus]]
 | 
				
			||||||
| 
						 | 
					
 | 
				
			||||||
		Loading…
	
		Reference in New Issue