Exporting or Migrating Naming Rules

[DanielS]

We were making the "Naming Rules" for an application in QA Enviroment of which 100 were generated (the allowed by Dynatrace), but we have the question of whether it is possible to migrate or copy in some way these "naming rules" to the same application but in production enviroment?

[skrystosik]

You should check Configuration API for such case:

https://www.dynatrace.com/support/help/extend-dynatrace/dynatrace-api/configuration-api/web-applicat...

There is option for exporting full application Configuration into json. Than you can use this payload on different environment.

Sebastian

[Julius_Loman]

Unfortunately, user action naming rules are not (yet) part of ten configuration API.

First I'd recommend analysing if the number of rules cannot be lowered (use of extraction rules, use Dynatrace JS API in the application, etc..). Otherwise, you have to sync the configuration manually in the UI or by simulating the UI requests, which is tricky and error-prone.

[skrystosik]

I agree that lowering should be case here, but user action naming rules are in API:

https://www.dynatrace.com/support/help/shortlink/api-config-web-app#applicationswebid-get-response-u...

Look here 🙂

Sebastian

[Julius_Loman]

I agree it's in the docs, but it is probably not implemented yet. Did you try that?

In any environment I have access to the userActionNamingSettings are not present in the GET /api/config/v1/applications/web/<application> (v174) or are set to null (v172) even if there are rules defined in the application configuration.

Does this work for you?

[skrystosik]

Ok you're right. I have on managed and SaaS missing it too, but despite documentation online, default swagger responses as well has this model implemented. Missing in responses is mistake I suppose or this will come really soon.

[Julius_Loman]

I guess the export will contain the export from the new user action naming engine and will probably skip the current one.

[skrystosik]

You may be right. This is first situation I've faced differences between documentation and reality in Dynatrace 😉