builtin:problem.fields)Problem fields allow you to define rules for extracting specific fields from events to problems. Events are stored in dt.davis.events and problems in dt.davis.problems. Each setting represents a unique rule, specifying which event fields should be extracted to the problem, ensuring critical information is carried over and easily accessible.
| Schema ID | Schema groups | Scope |
|---|---|---|
builtin:problem.fields | - | environment |
| GET | Managed | https://{your-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:problem.fields |
| SaaS | https://{your-environment-id}.live.dynatrace.com/api/v2/settings/schemas/builtin:problem.fields | |
| Environment ActiveGate | https://{your-activegate-domain}/e/{your-environment-id}/api/v2/settings/schemas/builtin:problem.fields |
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.
| Property | Type | Description | Required |
|---|---|---|---|
Enabledenabled | boolean | If this is true, the field is extracted from events to problems. | required |
Event fieldeventField | text | Field from the event that will be extracted. | required |
Problem fieldproblemField | text | Field under which the extracted event data will be stored on the problem. | required |