• 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 Jibi U. · Dec 12, 2014 at 05:23 AM ·

Alert email Incidents suppress period.

 

 

What could be the issue here? 

 

I am not getting the next email after 150 seconds. Smart alerting is disabled.

 

Jibi

 

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.

5 Replies

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

Answer by Jibi U. · Dec 13, 2014 at 03:43 AM

Thanks Tom. 

Comment

People who like this

0 Show 0 · 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

Answer by Thomas L. · Dec 13, 2014 at 03:18 AM

There is a way to generate additional emails but I would definitely be cautious when using this approach (as I've seen people get spammed with literally tens of thousands of emails). You can put your client into debug mode (Ctrl + Shift + F9 on Windows) and then edit the incident. You'll see an additional "Sensitivity" field which will get you what you want. Actually, this may help with your testing the Incident suppression. You could set your sensitivity to "Per Violation," meaning each transaction that breaks the threshold would immediately end. This would work in the way you initially thought from your first post I believe.

Again, use caution if you use this route since it can cause a large number of emails if set up incorrectly. 

Comment

People who like this

0 Show 0 · 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

Answer by Jibi U. · Dec 13, 2014 at 03:02 AM

Thanks Tom. I get it now. I had kept the threshold low in purpose to test this. 

 

Consider the case of a major incident on your site. We get the first email and the incident has not ended. Is there a way to generate another email say after a few minutes. I was just considering of the possibility of someone missing major incident emails.. One thing I can do is may be create another measure and incident and may be change the evaluation time frame etc????  

Comment

People who like this

0 Show 0 · 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

Answer by Thomas L. · Dec 12, 2014 at 07:37 AM

Hi Jibi,

The issue sounds like your incident is never actually ending. The 150 seconds applies from incident end. If your threshold is set too low, it will never actually end meaning the 150 seconds never gets applied. When you modify the threshold an email sends because technically it's a new incident. If you look at your incident dashlet you can visually see when the incident ends.

I would recommend setting a higher threshold so the incident gets triggered less often (for example every 10-20 seconds). Once the incident ends, you should not receive any new alerts for 150 seconds from the end time.

Tom 

Comment

People who like this

0 Show 0 · 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

Answer by Jibi U. · Dec 12, 2014 at 06:50 AM

To test this I changed the threshold to a very low value and so was expecting the first email and then the second after 150 seconds and then the third email etc.. Did not get any other than the first email (I get this first email each time I modify the threshold). Not a problem with email client as I had added a gmail id also to this to test... 

Comment

People who like this

0 Show 0 · 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.

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

1 Person is following this question.

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