• Forums
    • Public Forums
      • Community Connect
      • Dynatrace
        • Dynatrace Open Q&A
      • Application Monitoring & UEM
        • AppMon & UEM Open Q&A
      • Network Application Monitoring
        • NAM Open Q&A
  • Home /
  • Public Forums /
  • Application Monitoring & UEM /
  • AppMon & UEM Open Q&A /
avatar image
Question by David F. · Jan 09, 2015 at 07:29 AM ·

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.

Capture.PNG

 

 I checked the xml file in the 5.5 directory and the email configuration was there

 

Capture1.PNG

 

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.

Comment

People who like this

0 Show 0
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

5 Replies

  • Sort: 
  • Most voted
  • Newest
  • Oldest
avatar image

Answer by Aaron L. · Jan 14, 2015 at 12:19 AM

RFE submitted - Include Self-Monitoring System Profile in migration scripts during upgrade

Regards,
Aaron

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Aaron L. · Jan 14, 2015 at 12:05 AM

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

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image

Answer by Thomas K. · Jan 13, 2015 at 10:46 PM

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

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Thomas K. · Jan 13, 2015 at 11:11 PM 0
Share

Follow up: Incident rules for custom system profiles should be migrated; only those for the Self-Monitoring Profile will not be migrated.

avatar image

Answer by Aaron L. · Jan 10, 2015 at 01:00 AM

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

Comment

People who like this

0 Show 1 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

avatar image Guenter H. · Jan 13, 2015 at 09:16 PM 0
Share

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.

avatar image

Answer by Guenter H. · Jan 09, 2015 at 08:15 PM

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.

Comment

People who like this

0 Show 0 · Share
10 |2000000 characters needed characters left characters exceeded
  • Viewable by all users
  • Viewable by moderators
  • Viewable by moderators and the original poster
  • Advanced visibility
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

How to get started

First steps in the forum
Read Community User Guide
Best practices of using forum

NAM 2019 SP5 is available


Check the RHEL support added in the latest NAM service pack.

Learn more

LIVE WEBINAR

"Performance Clinic - Monitoring as a Self Service with Dynatrace"


JANUARY 15, 3:00 PM GMT / 10:00 AM ET

Register here

Follow this Question

Answers Answers and Comments

3 People are following this question.

avatar image avatar image avatar image

Forum Tags

dotnet mobile monitoring load iis 6.5 kubernetes mainframe rest api dashboard framework 7.0 appmon 7 health monitoring adk log monitoring services auto-detection uem webserver test automation license web performance monitoring ios nam probe collector migration mq web services knowledge sharing reports window java hybris javascript appmon sensors good to know extensions search 6.3+ server documentation easytravel web dashboard kibana system profile purelytics docker splunk 6.1 process groups account 7.2 rest dynatrace saas spa guardian appmon administration production user actions postgresql upgrade oneagent measures security Dynatrace Managed transactionflow technologies diagnostics user session monitoring unique users continuous delivery sharing configuration alerting NGINX splitting business transaction client 6.3 installation database scheduler apache mobileapp RUM php dashlet azure purepath agent 7.1 appmonsaas messagebroker nodejs 6.2 android sensor performance warehouse
  • Forums
  • Public Forums
    • Community Connect
    • Dynatrace
      • Dynatrace Open Q&A
    • Application Monitoring & UEM
      • AppMon & UEM Open Q&A
    • Network Application Monitoring
      • NAM Open Q&A