• 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 N. · Sep 18, 2012 at 12:18 AM ·

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.

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.

2 Replies

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

Answer by Guenter H. · Sep 18, 2012 at 05:53 PM

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.

Comment

People who like this

0 Show 4 · 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. · Sep 18, 2012 at 08:13 PM 0
Share

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.

avatar image David N. Guenter H. · Sep 18, 2012 at 10:20 PM 0
Share

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?

avatar image Guenter H. David N. · Sep 19, 2012 at 04:15 PM 0
Share

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.

avatar image David N. Guenter H. · Sep 19, 2012 at 10:30 PM 0
Share

Awesome, that makes sense. We should be able to convert our rules to this.

avatar image

Answer by Andreas G. · Sep 18, 2012 at 12:22 AM

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

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 David N. · Sep 18, 2012 at 12:28 AM 0
Share

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.

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

2 People are following this question.

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