This page describes certain legacy Settings schemas that have been removed in Latest Dynatrace.
Use this information as you migrate from Dynatrace Classic to Latest Dynatrace.
These changes are part of the continuous evolution of the Dynatrace platform towards a unified, scalable observability platform.
These changes enable enhanced capabilities through Grail's data lakehouse architecture and the flexible
Workflows automation engine.
If you use configuration-as-code or other automations that reference these schemas by ID, you need to update these automations before the schemas are removed from your environment. Otherwise, your automations may fail.
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Dashboard image allowlist | Removed | ||
Dashboard general settings | Removed | ||
Preset settings | Replaced by ready-made dashboards | Upgrade from Dashboards Classic to Dashboards, Ready-made dashboards | |
Custom units | Removed |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Problem notifications | Replaced by Workflows | Upgrade from Classic problem notification to simple workflows | |
Alerting profiles | Replaced by Workflows | Upgrade from Classic problem notification to simple workflows | |
Process group availability monitoring | Replaced by health alerts | ||
Dynatrace mobile app | Removed | ||
Maintenance windows | Replaced by maintenance windows |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Anomaly detection for infrastructure: Disk | Replaced by disk edge anomaly detection | ||
| Anomaly detection for infrastructure | Replaced by disk edge anomaly detection | |
Disk anomaly detection rules | Replaced by disk edge anomaly detection | ||
Metric events | Replaced by metric events | ||
Frequent issue detection | Removed | ||
Anomaly detection for classic AWS services | Replaced by cloud health alerts | ||
Anomaly detection for VMware | Replaced by infrastructure anomaly detection | Adjust the sensitivity of anomaly detection for infrastructure | |
| High GC activity detection | Removed | |
Database anomaly detection | Removed |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Processing | Replaced by OpenPipeline | ||
Log events | Removed | ||
Log metrics | Replaced by OpenPipeline | ||
Log custom attributes | Removed | ||
Log Security Context | Replaced by OpenPipeline | ||
Log buckets | Replaced by Grail bucket assignment |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Business event bucket assignment | Replaced by OpenPipeline | Business event processing, Ingest sources configuration (bizevents) schema table | |
Business event metric extraction | Replaced by OpenPipeline | Business event processing, Ingest sources configuration (bizevents) schema table | |
Business event processing | Replaced by OpenPipeline | Business event processing, Ingest sources configuration (bizevents) schema table | |
Business event security context | Replaced by OpenPipeline | Business event processing, Ingest sources configuration (bizevents) schema table | |
DQL processing | Replaced by OpenPipeline | Business event processing, Ingest sources configuration (bizevents) schema table |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Anomaly detection for custom applications | Replaced by Davis anomaly detectors | ||
Crash rate increase settings for custom applications | Replaced by frontend health alerts | ||
Usability analytics | |||
User session custom metrics | Replaced by OpenPipeline | ||
User action custom metrics | Replaced by OpenPipeline | ||
Resource URL cleanup rules | Replaced by OpenPipeline |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Service detection rules for External Web Requests | Removed | ||
Service detection rules for External Web Services | Removed | ||
| Service naming rules | Removed | |
| Host naming | Replaced by | |
| Process group naming | Replaced by | |
| Calculated service metrics | Replaced by calculated service metrics | |
Key requests | Replaced by enhanced endpoints for SDv1 |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Management zones | Data filtering replaced by segments; access management now handled through IAM policies | Upgrade from management zones to segments, Manage IAM policies | |
Automatically applied tags | Removed | ||
| Manually applied tags | Removed | |
Generic relationships | Replaced by Extensions topology | ||
Generic types | Replaced by Extensions topology | ||
Grail security context for monitored entities | Removed |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Assign synthetic monitor to web applications | Removed | ||
Monitor name | Removed | ||
Endpoint metrics | Removed |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Service-level objective definitions | Replaced by | ||
Service-level objective setup | Removed |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Log audit events | Replaced by Grail audit logs |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
| AWS | Replaced by AWS integration | |
Cloud Foundry | Replaced by Cloud Foundry integration | ||
VMware | Replaced by VMware extension | ||
Classic Windows services monitoring | Replaced by OS services monitoring | ||
Remote environments | Removed | ||
| Cloud Automation instances | Removed | |
Configuration for ActiveGate authentication method | Removed |
These schemas collectively controlled which OpenTelemetry span and resource attribute values are stored in classic storage and who can see them. In the Grail-based platform, this functionality moves to two layers: OpenPipeline for at-ingest filtering and transformation, and Grail field-level security (fieldsets) for display masking.
| Schema ID | Full name | Status | More info | What to do |
|---|---|---|---|---|
Attributes preferences | Replaced by OpenPipeline | Processing in OpenPipeline, Set up Grail permissions for Distributed Tracing | Use OpenPipeline span pipelines to drop or transform specific attributes at ingest. | |
Allowed attributes | Replaced by OpenPipeline | Configure an OpenPipeline span pipeline to explicitly keep or remove attribute keys at ingest. | ||
Blocked attributes | Replaced by OpenPipeline | Add attribute removal or masking processors in an OpenPipeline span pipeline. | ||
Attribute data masking | Replaced by OpenPipeline masking/dropping and Grail field-level security | To mask or drop selected attributes at ingest, use OpenPipeline masking/dropping. To restrict who can view stored sensitive attributes, define custom fieldsets in Grail field-level security, marking sensitive attribute keys as restricted. |
| Schema ID | Full name | Status | More info |
|---|---|---|---|
Histogram metrics | Replaced by Grail | ||
Security context settings | Removed | ||
Settings for classic tokens | Removed |