cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

This product reached the end of support date on March 31, 2021.

What are the roleKey and scheduleKey in a Dynatrace plugin?

derick_hewetson
Organizer

I am developing a custom plugin, but when I test it, I get the following error message in the log:

2016-01-06 09:19:21 WARNING [UserPluginManager@c9d69540-4244-4aa1-aba3-f74578df6c07] roleKey or scheduleKey of plugin is null. Can not log out in specified logfile for plugin
2016-02-27 17:18:30 INFO [autoInContactPlugin@bbc12f71-a4ea-410f-b6d1-9a01d44337c0] Incident: 'An incident solely created for testing purposes' triggered.
2016-02-27 17:18:30 WARNING [UserPluginManager@bbc12f71-a4ea-410f-b6d1-9a01d44337c0] roleKey or scheduleKey of plugin is null. Can not log out in specified logfile for plugin
2016-02-28 19:04:52 INFO [autoInContactPlugin@628a30c8-4313-4bb9-b041-8de0ef86f127] Incident: 'An incident solely created for testing purposes' triggered.
2016-02-28 19:04:52 WARNING [UserPluginManager@628a30c8-4313-4bb9-b041-8de0ef86f127] roleKey or scheduleKey of plugin is null. Can not log out in specified logfile for plugin

What is meant by the roleKey or scheduleKey of the plugin?

4 REPLIES 4

andreas_grabner
Dynatrace Guru
Dynatrace Guru

Hi Dereck

just got a confirmation about this from engineering. This warning is not a problem in your case as your plugin still operates normally. The warning however will be addressed in the next dynatrace version as team is already aware of an internal issue that causes this warning message. No harm to your plugins though

Andi

bhavins
Guide

Hi Andi,

Can you please update status of issue. Even we are getting same warning in our custom plugin. We are using Dynatrace version 6.2.8.1019.

Regards,

Bhavin Shah

Hi Bhavin, I can't comment on the original question, but you are aware that support for v6.2 runs out at the end of December 2016? See our support and end-of-life policies. I'd highly recommend updating to the latest version - 6.5. In addition, you're on update 8 of 6.2 and there are 20 updates so you're significantly behind even 6.2 latest.

It is likely that this issue has been addressed since then.

I also wanted to suggest the same as Adam. Please make sure to Upgrade. Derek posted his question earlier this year - probably with 6.2 - but since then we released several new versions of Dynatrace. 6.5.5 is the most current one that you should upgrade to