```
public interface NamingConvention
```
Monitoring systems make different recommendations regarding naming convention.
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).

Fields
Modifier and Type	Field	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`	`snakeCase`
`static NamingConvention`	`upperCamelCase`

All Methods Instance Methods Abstract Methods Default Methods
Modifier and Type	Method	Description
`default String`	`name(String name, Meter.Type type)`
`String`	`name(String name, Meter.Type type, String baseUnit)`
`default String`	`tagKey(String key)`
`default String`	`tagValue(String value)`

dot
```
static final NamingConvention dot
```
This maps to identity because we suggest using dot notation everywhere in Micrometer-instrumented code

static final NamingConvention snakeCase

static final NamingConvention camelCase

static final NamingConvention upperCamelCase

default String name(String name,
                    Meter.Type type)

String name(String name,
            Meter.Type type,
            @Nullable
            String baseUnit)

default String tagValue(String value)

Interface NamingConvention