apm.manage; owners,
administrators, and editors hold it. Without it the page reads the settings and changes nothing.
A saved setting applies at once on the node that saved it and within 30 seconds on the others.
Naming rules and the environment mapping apply to the spans read from then on; what APM already kept
keeps its names. Health lines, the default Apdex threshold, aliases, and catalog requirements apply
to every read, data already kept included.
Collection quality
The first card reads the past day and lists what needs a fix and what a setting would improve:
A suggestion added to a card waits there until Save.
Health and thresholds
The lines decide the health of each service in the catalog, on its page, on the map, and in the
overview’s health trend.
Catalog requirements
For each of Team, Owner, and Repository, the tier from which the catalog asks for it: Not required, or a tier and every tier above it. A service of such a tier without that field reads Needs with the missing fields in the catalog. A service without a tier is asked nothing.Service naming
Naming rules rewrite service names as spans are read. Each rule is a regular expression and a replacement, which may name the expression’s groups as$1 or ${name}. The rules are tried in
order, and the first whose expression matches the name rewrites it; a rewrite to an empty name keeps
the name. Try a service name shows what a name would be read as.
An organization keeps up to 20 rules. Traces keep the names that spans carry, so a trace search uses
the name before the rule.
Environment mapping
Each mapping reads an environment named one way as another, ignoring case, as spans are read: for exampleProduction and prod both as production. An environment is mapped at most once, and an
organization keeps up to 50 mappings.
Service aliases
An alias names a service by an older name, each side with its namespace,default when left blank.
What the alias reported is read as the service’s on every APM page, merged with what the service
reported itself, data already kept included. The service map and deployment reports follow the
aliases too. Removing an alias reads the two apart again.
A service is not its own alias, a name is an alias once, and an alias never leads to another alias.
An organization keeps up to 100 aliases. A page opened on the alias itself, from an older link,
still reads the alias’s own data.
Cardinality limits
Shown to whoever holdssys.settings.manage. The limits hold for the whole platform: each hour, APM
keeps apart at most this many of each kind and counts the rest as Other.
Each limit is a whole number from 1 to 100,000. Every node reads the limits again every 30 seconds.
Trace sampling
Shown to whoever holdssys.telemetry.read; changing it requires sys.telemetry.manage. The policy
decides which traces the platform keeps once they end:
- Normal traces kept is the share kept of the traces that no rule, error, or slowness keeps; 10% by default.
- Each rule matches the traces whose spans carry the Service, Route, and Operation it names, are at least From ms long, and failed when Errors only is set. The rule then keeps, drops, or keeps a share of them. Rules are tried in order before the normal share.