Settings API - Ownership teams schema table
Ownership teams (builtin:ownership.teams)
Set up teams and assign responsibilities to them. Link teams to monitored entities in Dynatrace by referencing the team identifier in entity metadata. See documentation
builtin:ownership.teams
group:ownership
environment
GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:ownership.teams |
SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:ownership.teams | |
Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:ownership.teams |
Authentication
To execute this request, you need an access token with Read settings (settings.read
) scope. To learn how to obtain and use it, see Tokens and authentication.
Parameters
name
description
identifier
The team identifier is used to reference the team from any entity in Dynatrace. If you are using Kubernetes labels, keep in mind the 63 character limit that they enforce.
supplementaryIdentifiers
The supplementary team identifiers can be optionally used in addition to the main team identifier to reference this team from any entity in Dynatrace. Up to 3 supplementary identifiers are supported.
responsibilities
Turn on all responsibility assignments that apply to this team.
contactDetails
Define options for messaging integration or other means of contacting this team.
links
Include links to online resources where information relevant to this team’s responsibilities can be found.
additionalInformation
Define key/value pairs that further describe this team — for example, cost center, solution type, or business unit assignments.
externalId
This field should only be used for the automation purpose when importing team information.
The SupplementaryIdentifier
object
supplementaryIdentifier
The Responsibilities
object
development
Responsible for developing and maintaining high quality software. Development teams are responsible for making code changes to address performance regressions, errors, or security vulnerabilities.
security
Responsible for the security posture of the organization. Teams with security responsibility must understand the impact, priority, and team responsible for addressing security vulnerabilities.
operations
Responsible for deploying and managing software, with a focus on high availability and performance. Teams with operations responsibilities needs to understand the impact, priority, and team responsible for addressing problems detected by Dynatrace.
infrastructure
Responsible for the administration, management, and support of the IT infrastructure including physical servers, virtualization, and cloud. Teams with infrastructure responsibility are responsible for addressing hardware issues, resource limits, and operating system vulnerabilities.
lineOfBusiness
Responsible for ensuring that applications in development align with business needs and meet the usability requirements of users, stakeholders, customers, and external partners. Teams with line of business responsibility are responsible for understanding the customer experience and how it affects business goals.
The ContactDetails
object
integrationType
JIRA
EMAIL
MS_TEAMS
SLACK
email
msTeams
slackChannel
url
The Link
object
linkType
DOCUMENTATION
RUNBOOK
WIKI
DASHBOARD
HEALTH_APP
URL
REPOSITORY
url
The AdditionalInformation
object
key
value
url
The JiraConnection
object
project
defaultAssignee