public interface NamingConvention
Also, many systems have constraints on valid characters that may appear in a tag key/value or metric name. While it is recommended to choose tag keys/values that are absent special characters that are invalid on any common metrics backend, sometimes this is hard to avoid (as in the format of the URI template for parameterized URIs like /api/person/{id} emanating from Spring Web).
Modifier and Type | Field and Description |
---|---|
static NamingConvention |
camelCase |
static NamingConvention |
dot
This maps to identity because we suggest using dot notation everywhere in Micrometer-instrumented code
|
static NamingConvention |
identity |
static NamingConvention |
slashes |
static NamingConvention |
snakeCase |
static NamingConvention |
upperCamelCase |
Modifier and Type | Method and Description |
---|---|
default java.lang.String |
name(java.lang.String name,
Meter.Type type) |
java.lang.String |
name(java.lang.String name,
Meter.Type type,
java.lang.String baseUnit) |
default java.lang.String |
tagKey(java.lang.String key) |
default java.lang.String |
tagValue(java.lang.String value) |
static final NamingConvention identity
static final NamingConvention dot
static final NamingConvention snakeCase
static final NamingConvention camelCase
static final NamingConvention upperCamelCase
static final NamingConvention slashes
default java.lang.String name(java.lang.String name, Meter.Type type)
java.lang.String name(java.lang.String name, Meter.Type type, @Nullable java.lang.String baseUnit)
default java.lang.String tagKey(java.lang.String key)
default java.lang.String tagValue(java.lang.String value)