1. Ownership #
Who is responsible for what.
Configuring #
Teams are declared in the settings (identifier, contacts, channels). Entities are attached to them through a dt.owner metadata: host property, environment variable, Kubernetes label or tag.
# Hôte
sudo /opt/dynatrace/oneagent/agent/tools/oneagentctl --set-host-property=dt.owner=team-paiement --restart-service
# Pod Kubernetes
metadata:
labels:
dt.owner: team-paiementGood practice: With owners filled in, notifications and workflows can directly notify the team concerned by a problem.
2. Maintenance windows #
Not alerting during an intervention.
Options #
| Behavior | Usage |
|---|---|
| Detect problems and alert | Maintenance with no expected impact |
| Detect without alerting | The most common case: problems remain visible but no notification is sent |
| Do not detect | Heavy intervention, irrelevant data |
A window is planned (one-off or recurring) or unplanned, and applies to a scope defined by filters (tags, entities, zones).
3. Naming rules #
Readable names.
Examples #
Naming rules rename hosts, process groups and services based on their metadata, for example to include the Kubernetes namespace:
Règle de nommage de groupe de processus :
Format : {ProcessGroup:KubernetesNamespace} - {ProcessGroup:KubernetesContainerName}
Condition : Kubernetes namespace existeCommon mistake: Renaming changes the display, not the entity's identity: history is preserved.
4. Key requests and tags #
Highlighting and organizing.
Key requests #
A key request is a service request marked as important (payment, login). It gets its own long-term metrics, dedicated thresholds and tracking in dashboards.
Tags #
| Type | Principle |
|---|---|
| Automatic tags | Rules with conditions (for example: process groups whose host group starts with prod_ get env:prod) |
| Manual tags | Added on an entity, or through the API |
| Environment tags | DT_TAGS variable, Kubernetes labels and annotations, cloud tags |
Good practice: Prefer automatic tags based on reliable metadata: they also apply to future entities, unlike manual tags.
