You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
The dynatrace_web_application and dynatrace_key_user_action currently allows configuration of Key User Actions by name, via a set of strings, but KUAs also support configuring individual anomaly detection for each action, which is not currently supported by the provider.
Describe the solution you'd like
We would like to be able to provide anomaly detection configuration for these KUAs in the dynatrace_web_application resource.
Describe alternatives you've considered
The only alternative we are aware of is to configure this manually and reproduce the configuration on each environment, which is difficult to maintain.
Additional context
There was a similar issue logged by mattBaumBeneva in issue #326 but for the dynatrace_mobile_application resource. A similar approach is needed for dynatrace_web_application
The text was updated successfully, but these errors were encountered:
nmarchini
changed the title
Allow configuration of apdex and anomaly detection for Key User Actions of a dynatrace_web_application
Allow configuration of anomaly detection for Key User Actions of a dynatrace_web_application
Jan 14, 2025
Is your feature request related to a problem? Please describe.
The dynatrace_web_application and dynatrace_key_user_action currently allows configuration of Key User Actions by name, via a set of strings, but KUAs also support configuring individual anomaly detection for each action, which is not currently supported by the provider.
Describe the solution you'd like
We would like to be able to provide anomaly detection configuration for these KUAs in the dynatrace_web_application resource.
Describe alternatives you've considered
The only alternative we are aware of is to configure this manually and reproduce the configuration on each environment, which is difficult to maintain.
Additional context
There was a similar issue logged by mattBaumBeneva in issue #326 but for the dynatrace_mobile_application resource. A similar approach is needed for dynatrace_web_application
The text was updated successfully, but these errors were encountered: