com.netflix.atlas.core.validation

Verifies that all of the tag rules match.

Verifies that the tags contain a specified key. Sample config:

key = name

Verifies that the keys are within the specified length bounds. Sample config:

min-length = 2
max-length = 60

Verifies that the keys match a specified pattern. Sample config:

pattern = "^[-_.a-zA-Z0-9]{4,60}$"

Verifies that the number of custom user tags are within a specified limit. Sample config:

limit = 10

Verifies that the name and values are within the specified length bounds. The limits for the value of the name key can be set independently from the values of other keys. Sample config:

name {
 min-length = 2
 max-length = 80
}
others {
 min-length = 2
 max-length = 60
}

Verifies that only allowed keys are used for reserved prefixes. Reserved prefixes are used to prevent user defined tags from overlapping with common infrastructure tagging that should be consistent for all data. Sample config:

prefix = "nf."
allowed-keys = ["app", "cluster"]

This config would only allow "nf.app" and "nf.cluster" with a prefix of "nf.".

Base type for validation rules.

Helper for rules that can be checked using a single key and value pair.

Verifies that the keys and values only use the set of ASCII characters specificied in the config. By default it will be alpha-numeric, underscore, dash, and period. Sample config:

default-pattern = "-._A-Za-z0-9"
overrides = [
 {
   key = "nf.cluster"
   value = "-._A-Za-z0-9^~"
 },
 {
   key = "nf.asg"
   value = "-._A-Za-z0-9^~"
 }
]

Verifies that the values are within the specified length bounds. Sample config:

min-length = 2
max-length = 60

Verifies that the values match a specified pattern. Sample config:

pattern = "^[-_.a-zA-Z0-9]{4,60}$"