Is Debug Mode possible for DT 4.2 OS X Client
Is Debug Mode possible for DT 4.2 OS X Client?
We are upgrading to 4.2 server and some of our alerts require sensitivities other than "Instant". Documentation says that you are able to modify the sensitivities if you start the client in Debug Mode.
Hi David
Debug Mode should not be used without assistance from our support or enablement team. Therefore I recommend getting in touch with either support or our enablment service team to discuss your changes.
Also - can you point me to the documentation where you found this information? I want to make sure we clarify this in the doc
Thanks
https://apmcommunity.compuware.com/community/display/DOCDT42/Incidents+and+Alerting
Sensitivity
The Sensitvity settings are only available for converted (pre dynaTrace 4) incident rules and via client's "Debug Mode".
Incident rules created with dynaTrace 4 internally use an *Instant" sensitivity.
Hey there, David,
yes, the debug mode is available on the Mac - as normal with modifiers Command-Shift instead of Control-Shift. I'm intentionally mum about the required key, because debug mode should only be used in collaboration with support - as you could shoot yourself in the foot with certain operations.
I went to the bottom of this Sensitivity settings issue and talked to the developer.
What I found out:
1) In the easyTravel System Profile there seem to be quite a number of Incident rules carried over from earlier (3.x?) versions, like "Agent Connected".
I can change Sensitivity in standard mode, so I guess this should apply for you too.
2) In eT "Agent Instrumentation Disabled" Sensitivity is disabled with a value of "Per violation".
According to the developer there is a small group of predefined Incidents where this can´t be changed.
Debug mode doesn´t make any difference.
3) Debug mode does make a difference if you Create a new Incident rule: Sensitivity popup visible or not!
If Sensitivity settings are allowed in 1) I conclude you can use it.
4) The Sensitivity popup was disabled / hidden for a reason in 4, so please check with us if your desired Incident rules can be accomplished with alternative settings.
5) I´ll change documentation and give feedback to product management from the result of our conversation here!
Thanks
G.
Upon closer inspection of the documentation:
'The Sensitvity settings are only available for converted (pre dynaTrace 4) incident rules and via client's "Debug Mode".'
The second part of the sentence seems to refer to Create rule (my point 3) where debug mode does make a difference, but you don´t need this for converted rules! (my point 1)
Misleading explanation!
Thx
G.
Our issue is creating new rules/alerts (not converted from a 3.X instance). Instant sensitivity is not appropriate for some of these in our situation. An example would be monitoring a AMQ queue and alerting only if the message count stays above a critical threshold for an extended period of time (not instantly). Is there a reason these were hidden in 4.X?
Hey there!
I try to give you an analog for your AMQ example:
Screenshot reads:
Alert if the avg of page fault count per sec is higher than the thresholds (see lower shot) over (extended) period of 5 minutes.
So this should give you the perfect reason why we disabled the Sensitivity setting. You can do any variant with the remaining means.
But I think we should have gone one step further in Edit Incident Rule, like we did in Create:
Not disable the Settings control, but not show it at all!
As soon as you see it you start thinking: How / When does this enable and what can I do with it that I can't do now?
Hope this helps! Please come back if the example leaves anything to be desired!
G.
Awesome, that makes sense. We should be able to convert our rules to this.
EMEA Community Member of the Month - November 2018
Announcing Dynatrace's EMEA Community Member of the Month for November 2018, Mathieu C.! Click here to read more! LATAM Community Member of the Month - November 2018
Announcing Dynatrace's LATAM Community Member of the Month for November 2018, Rene S.! Click here to read more! 
