Configurations that are exportable/applicable via REST API

MaciejNeumann — Tue, 14 Feb 2023 09:01:35 GMT

Do you have a complete list of which configurations are exportable/applicable via our REST API vs. which are not (and need to be migrated manually)?

Re: Configurations that are exportable/applicable via REST API

Radoslaw_Szulgo — Tue, 14 Feb 2023 09:57:55 GMT

We recommend using Configuration-as-code to automate the process of configuration migration. This tool is based on available REST APIs in Dynatrace.

Updated: February 14, 2023, 10:00 UTC.

Supported configurations

Most of the configuration is already covered by Configuration-as-code. Find the list below for reference:

application-mobile
application-web
builtin:alerting.profile
builtin:anomaly-detection.databases
builtin:anomaly-detection.frequent-issues
builtin:anomaly-detection.infrastructure-aws
builtin:anomaly-detection.infrastructure-disks
builtin:anomaly-detection.infrastructure-hosts
builtin:anomaly-detection.infrastructure-vmware
builtin:anomaly-detection.metric-events
builtin:anomaly-detection.rum-mobile
builtin:anomaly-detection.rum-mobile-crash-rate-increase
builtin:anomaly-detection.rum-web
builtin:anomaly-detection.services
builtin:audit-log
builtin:availability.process-group-alerting
builtin:cloud.cloudfoundry
builtin:cloud.kubernetes
builtin:container.built-in-monitoring-rule
builtin:container.technology
builtin:deployment.activegate.updates
builtin:deployment.management.update-windows
builtin:deployment.oneagent.updates
builtin:disk.options
builtin:eec.local
builtin:elasticsearch.user-session-export-settings-v2
builtin:eula-settings
builtin:example.modification-policy-schema
builtin:example.non-deletable-singleton
builtin:failure-detection.service.general-parameters
builtin:failure-detection.service.http-parameters
builtin:host.process-groups.monitoring-state
builtin:logmonitoring.log-storage-settings
builtin:logmonitoring.timestamp-configuration
builtin:mainframe.mqfilters
builtin:mainframe.txmonitoring
builtin:mainframe.txstartfilters
builtin:management-zones
builtin:metric.metadata
builtin:monitored-technologies.apache
builtin:monitored-technologies.dotnet
builtin:monitored-technologies.go
builtin:monitored-technologies.iis
builtin:monitored-technologies.java
builtin:monitored-technologies.nginx
builtin:monitored-technologies.nodejs
builtin:monitored-technologies.open-tracing-native
builtin:monitored-technologies.php
builtin:monitored-technologies.varnish
builtin:monitored-technologies.wsmb
builtin:monitoredentities.generic.relation
builtin:monitoredentities.generic.type
builtin:oneagent.features
builtin:os-services-monitoring
builtin:preferences.privacy
builtin:problem.notifications
builtin:process-group.cloud-application-workload-detection
builtin:process-group.detection-flags
builtin:process-group.monitoring.state
builtin:process.built-in-process-monitoring-rule
builtin:process.process-monitoring
builtin:remote.environment
builtin:resource-attribute
builtin:rum.custom.enablement
builtin:rum.custom.name
builtin:rum.host-headers
builtin:rum.ip-determination
builtin:rum.mobile.beacon-endpoint
builtin:rum.mobile.enablement
builtin:rum.mobile.key-performance-metrics
builtin:rum.mobile.name
builtin:rum.mobile.privacy
builtin:rum.user-experience-score
builtin:rum.web.app-detection
builtin:rum.web.browser-exclusion
builtin:rum.web.custom-errors
builtin:rum.web.custom-rum-javascript-version
builtin:rum.web.enablement
builtin:rum.web.ipaddress-exclusion
builtin:rum.web.key-performance-metric-custom-actions
builtin:rum.web.key-performance-metric-load-actions
builtin:rum.web.key-performance-metric-xhr-actions
builtin:rum.web.name
builtin:rum.web.request-errors
builtin:rum.web.rum-javascript-updates
builtin:sessionreplay.web.privacy-preferences
builtin:sessionreplay.web.resource-capturing
builtin:settings.subscriptions.service
builtin:span-attribute
builtin:span-entry-points
builtin:span-event-attribute
builtin:span-failure-detection-config
builtin:span-service-detection-config
builtin:synthetic.browser.assigned-applications
builtin:synthetic.browser.kpms
builtin:synthetic.browser.name
builtin:synthetic.browser.outage-handling
builtin:synthetic.browser.performance-thresholds
builtin:synthetic.browser.scheduling
builtin:synthetic.http.assigned-applications
builtin:synthetic.http.cookies
builtin:synthetic.http.name
builtin:synthetic.http.outage-handling
builtin:synthetic.http.performance-thresholds
builtin:synthetic.http.scheduling
builtin:tags.auto-tagging
builtin:tokens.token-settings
builtin:usability-analytics
calculated-metrics-application-web
custom-service-java
dashboard
extension-elasticsearch
reports
service-resource-naming
synthetic-location
synthetic-monitor

Unsupported configurations

Some configurations are supported to be deployed but are not supported to be downloaded. To migrate them, you need to create them manually. These configurations are:

aws-credentials
azure-credentials
credential-vault
extension
kubernetes-credentials

Re: Configurations that are exportable/applicable via REST API

erh_inetum — Wed, 20 Mar 2024 05:51:08 GMT

Hi,

Monaco (Configuration-as-code) is on version 2.11. So these are the supported configuration now:
https://docs.dynatrace.com/docs/manage/configuration-as-code/monaco/reference/supported-configuration

You can find here the elements that require a manual migration according to the documentation: https://docs.dynatrace.com/managed/upgrade/up-execute-upgrade/up-migrate-cfg#settings-that-require-manual-migration

But on my experience with monaco 2.11, the configurations that Radoslaw has detailed in his post (Problem Notification Integrations, Dashboards sharing settings, Web application usability analytics - rage clicks, Process groups custom names and descriptions and Custome Service Rules) and also RUM user action and session properties can be migrated automatically using Monaco.

On the other hand, these configurations must be migrate manually:
- Account managment
- Conversion goals
- MDAs
- Manually tags
- Key web requests
- Key user actions (RUM web and mobile key user actions)
- GCP monitoring
- VMWare platform monitoring
- Tokens
- Metrics not linked to instances
- JavaScript Errors
- Mobile symbolication
- Request naming and detection rule order
- Merged service
And the unsupported configurations commented by Radoslaw said in his post.

In case of conversion goals, if an application has conversion goals, monaco returns an error saying that the API is not supported. And as a result, the application and all its configurations will not migrated.

To migrate the unsupported configurations you can use API calls in most cases.

Regards,
Elena.

topic Configurations that are exportable/applicable via REST API in Upgrade to SaaS

Configurations that are exportable/applicable via REST API

Re: Configurations that are exportable/applicable via REST API

Supported configurations

Unsupported configurations

Re: Configurations that are exportable/applicable via REST API