We have just upgraded our CAPC instance from v2.7 to v2.8. This was our very first upgrade since we have CAPC.
We are very surprised (and unhappy) to see now a gap in the graphs, that is 20 minutes long.
What is causing that gap and how can we prevent it to occur in the future upgrade.
To be clear: we had no gap before the upgrade, and there are no more gaps after the upgrade. But it seems that Data Collector stopped collecting data during 20 minutes at the time of the upgrade. Why so long ? Why does it stop at all ?
During the upgrade the data collector stops both activemq and the dc ( java process) and this means we dont collect any data from the devices during this time and thats most likely the reason why you are not seing any data during the upgrade time.
Why does it stop for so long ?
If you look at the install log it will show you all the upgrade tasks being carried out.
It definetely depends on the resources available.
Yes, the upgrade took less than one minute. Why does the data collection stop for more than 1 minute then ?
You can also check the DC install log and see when the installation started and when it ended.
Installed Feature(s) Application, Help of CA Performance Management Data Collector
Install Begin: OCTOBER 7, 2016 10:41:58 AM EDTInstall End: OCTOBER 7, 2016 10:44:38 AM EDT
You can attach the Latest install log for all the components during the upgrade
Install Begin: OCTOBER 11, 2016 8:29:19 AM CEST
Install End: OCTOBER 11, 2016 8:30:07 AM CEST
So, why do we have a 20 minute gap in the data ?
I understand that you have already open a support ticket 00529954 . Please attach the CARE output from DA,DA,CAPC we will take a look and come back to you.