When you add tags via the UI or API, this occurs at the entity level. You can't remove these available-by-default tags. For example, the account name, the account ID, and some basic host and server metadata. Some important attributes are available by default to be used as tags. In the case of OpenTelemetry services, the tagging definitions are on ext-service entities. This automated tagging is done using New Relic entity synthesis, which is documented on GitHub. When the following attributes are present on span data associated with a service entity, they will be attached to that entity: Ĭertain OpenTelemetry resource attributes are automatically applied as entity tags. You can also programmatically automate tags using our API or the New Relic CLI. Tags from these sources can be removed or changed only by modifying the source of the tag, not via the UI or API. Tags are automatically applied to your monitored entities in some cases, from the following sources: If you want to add more fine-grained detail, like capturing user names or other high-cardinality values, we recommend using custom attributes or custom events. Tags are useful for organizing your data at a high level. Better organize and search dashboards and workloads.Identify teams, roles, environments, or regions to know who's responsible for what.Organize data coming from a large number of sources and/or to a large number of New Relic accounts.Here you can see an accountId tag being used to filter workloads to a specific account. You can use tags in the UI to filter down to relevant entities. We make some important attributes available as tags: this includes app metadata, like the app name and the language, and host metadata like the host name and the cloud provider region. Tags are key-value pairs, for example team: operations, added to your monitored entities, or to your dashboards or workloads.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |