Ownership Classic
- Dynatrace Classic
- Overview
- 3-min read
Support for assigning Ownership teams to Smartscape Classic monitored entities is deprecated. We recommend using Smartscape nodes. For more information on assigning Ownership teams to Smartscape nodes, see Assign ownership teams to Smartscape nodes.
Assigning team owners to monitored entities in Dynatrace drives effective DevSecOps collaboration and swift, smart resolution of incidents and service degradations.
Ownership metadata attached to entities feeds your BizDevSecOps workflows, ensuring that the right people from among your security, operations, infrastructure, line of business, and development teams are brought together with the right information in context.
Knowledge about the ownership of an entity enables additional automation, such as:
- Notification of relevant teams of production issues that need their attention.
- Creation of IT service management tickets (for example, in Jira and ServiceNow) and assignment to the right teams.
- Assignment of vulnerabilities to the responsible team members.
- Provision of information to all relevant stakeholders.
You can create ownership information in the web UI, via API, and using Configuration as Code. You can also import ownership teams from third-party directory services (Microsoft Entra ID) via Workflows. For scalability and complete coverage, assign ownership as part of deployment metadata. You can also use the settings and entity web interfaces for these purposes.
-
Create and maintain ownership teams with unique IDs and associated contact information to make problem routing easier. See also Best practices for entity ownership.
Ownership teams settings page -
Assign teams to Dynatrace-monitored entities via host metadata, Kubernetes labels and annotations, environment variables, and tags. See also Best practices for entity ownership.
-
View ownership information with routing details as part of Dynatrace entity details pages.
Owner of a Kubernetes workload
Basics
