Sensor pack upgrades during Migration
If the "JMS Receive Entry Point" is change to include the methods needed to monitor MQ. During the upgrade do we over write what was added or leave the methods alone for out the box sensor groups.
Thanks
Hi Ed,
when upgrading the defaults of the new version are used and previous changes to built-in sensor packs are not carried over. The current recommended way to handle such changes is to apply the changes again after upgrading. This is documented under point 2.3 here:
Migration Verification and Final Checks
Although the old built-in sensor packs are not migrated, they are however backed up in the migration archive.
Another approach, depending on the type of changes could be to create a custom sensor pack with those includes and import that into each (new) version when it comes out. More information on this is found for instance here: Building FastPacks Pre-existing examples here: FastPacks and Plugins
Best regards,
Thomas
Hi Thomas,
Can FastPacks be used for "Knowledge Sensor Packs" -- the ones that do a little more behind the scenes than normal instrumentation (for instance JMS Receive Entry Point)?
Thanks Thomas -
1) sensor packs created by the client -do they get migrated. Sensor groups do get migrated.
2) Is there away to change the "add agent tier wizard" to included Sensor packs created by the client -for example JMS Receive Entry Point needs client sensors added, as per dynatrace documentation. If sensors are dropped from delivered Sensor packs then we need a fail proof method to add sensors. Also to enable the wizard to work if we create a custom sensor pack. Your thoughts please.
