Best Practices For Tagging Events
Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel,
n'hésitez pas à nous contacter.
Overview
Datadog recommends using unified service tagging and the tags listed below on all your events for the following benefits:
- Identify potential issues faster
- Locate related events
- Filter more accurately in the Events Explorer, for example, to a specific environment
You have multiple options to improve your tagging strategy for events:
API: When using the API, you can add tags in the tags field.
Monitor: When creating or editing a monitor, you can add recommended tags in the Say what’s happening section.
Integrations: For more information about adding tags to integrations, see Assigning Tags or the specific integration.
You can add the following core attributes to your events:
| Attribute | Description |
|---|
| env | The environment in which the event is from, such as production, edge, or staging. This enables you to ensure that events from a lower environment are not confused as high priority. |
| service | The service name. Enables you to:
- Know which service(s) are impacted if an event is related to an error
- Pivot to the impacted service
- Filter for all events with that service |
| version | The build or service version. This allows you to identify, for example, if an outage or event is related to a particular version. |
| host | The host name. Enables you to:
- Automatically enrich events at intake with additional host tags
- Pivot to the Host Infrastructure and Metrics tabs in the Events Explorer. |
| team | The team that owns the event and are notified if need be. |
Further reading
Documentation, liens et articles supplémentaires utiles:
