Incidents configuration after migration from 5.5 to 6.1
Are incidents configuration in the dynatrace Self-Monitoring and custom system profiles (created by myself) suppose to be carried over with the migration.
I recently migrated from 5.5 to 6.1 and I noticed the Incidents I setup for "dynatrace Server Offline" has all the email configuration missing and this was present in 5.5.
I checked the xml file in the 5.5 directory and the email configuration was there
I am not sure if I had email configuration setup under my custom system profiles but I thought I did and now I don't see them.
Is it that the migration does migrate this information for custom system profiles but not for dynatrace self-monitoring system profile?
Or did something go wrong in the migration. The output of the migration showed all successful.
Hi David,
to the best of my knowledge:
The Self-Monitoring System Profile gets generated and is not carried over. Other SPs (and their settings) are migrated.
"dynaTrace Server Offline": Sadly our documentation (Incidents and Alerting > Built-in Incidents) does not say when this definition was removed (and I personally don´t remember), but it was purged. See the list. (Would be interesting how this incident got triggered, namely when the Server was down! <g>)
Hope this helps!
G.
Would we be able to merge the settings from our 5.5 environment into the 6.x Self-Monitoring profile directly in the XML file if we replaced the <incidentrule> tags in the 6.1 file with the same entries from our 5.5 system?
Alternatively, could Support or Dev potentially provide a script to do the migration?
Thanks,
Aaron
Aaron,
I tried to verify with engineering if there had been any structural changes to the incident rule definitions which would forbid XML copy / paste, but it´s very hard to nail this as there were several devs on it.
What I ask myself: Is it worth it to dig much deeper. How many rules do you need to migrate / define afresh?
I just saw a TD support case (ulimit), so I guess your inclination to tinker (copy the rules XML part) may be limited.
Anyway, I asked the engineer responsible for migration to get back to you here too.
Thanks
G.
Hi Aaron,
the Self-monitoring system profile is not migrated (currently) by design. The other custom profiles are migrated. Please be sure to check "2.3. Apply Customizations Not Covered By Automation" in Final Checks, which requires to redefine incidents.
I do not recommend merging these XML parts, as structure changes may occur between versions and as mentioned incidents may get removed. Please use the UI to redefine them in the new version.
Regarding automatization, please put in a "Request for enhancement" regarding this here. Once we have a script / automated process we will directly include it in Dynatrace or the migration tool and remove that step from the Migration Guide, however this improvement is currently unplanned.
Best regards,
Thomas
Follow up: Incident rules for custom system profiles should be migrated; only those for the Self-Monitoring Profile will not be migrated.
Guenter and Thomas,
Thanks for the clarification on this issue - we will assume that the Self-Monitoring Incidents need to be manually re-created after our production migration from 5.5 to 6.1.
I will look at doing an RFE for this, as it would be nice to have in any future upgrades, as we have customized the actions, etc. for several of the Incident definitions, and added a few of our own.
Regards,
Aaron
RFE submitted - Include Self-Monitoring System Profile in migration scripts during upgrade
Regards,
Aaron
Welcome the
Dynatrace Community Forums
Check out the Forum User Guide and Forum Guidelines to learn how to get started.Community Member of the Month
August 2017
Announcing Dynatrace's Community Member of the Month for August 2017, Rick B.! Click here to read more! 