DatadogConfig (micrometer-registry-datadog 1.3.0 API)

All Superinterfaces:

io.micrometer.core.instrument.config.MeterRegistryConfig, io.micrometer.core.instrument.push.PushRegistryConfig, io.micrometer.core.instrument.step.StepRegistryConfig
```
public interface DatadogConfig
extends io.micrometer.core.instrument.step.StepRegistryConfig
```
Configuration for DatadogMeterRegistry.

Method Summary

All Methods Instance Methods Default Methods
Modifier and Type	Method	Description
`default java.lang.String`	`apiKey()`
`default java.lang.String`	`applicationKey()`
`default boolean`	`descriptions()`
`default java.lang.String`	`hostTag()`
`default java.lang.String`	`prefix()`
`default java.lang.String`	`uri()`

Methods inherited from interface io.micrometer.core.instrument.config.MeterRegistryConfig
get

Methods inherited from interface io.micrometer.core.instrument.push.PushRegistryConfig
batchSize, connectTimeout, enabled, numThreads, readTimeout, step

- Method Detail
  - prefix
```
default java.lang.String prefix()
```
    Specified by:
    
    prefix in interface io.micrometer.core.instrument.config.MeterRegistryConfig
  - apiKey
```
default java.lang.String apiKey()
```
  - applicationKey
```
@Nullable
default java.lang.String applicationKey()
```
    Returns:
    
    The Datadog application key. This is only required if you care for metadata like base units, description, and meter type to be published to Datadog.
  - hostTag
```
@Nullable
default java.lang.String hostTag()
```
    Returns:
    
    The tag that will be mapped to "host" when shipping metrics to datadog.
  - uri
```
default java.lang.String uri()
```
    Returns:
    
    The URI to ship metrics to. If you need to publish metrics to an internal proxy en route to datadoghq, you can define the location of the proxy with this.
  - descriptions
```
default boolean descriptions()
```
    Returns:
    
    true if meter descriptions should be sent to Datadog. Turn this off to minimize the amount of data sent on each scrape.