Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene/Andreas,

Strange issue found after importing the plugin, Schedule reports email are delivered twice. As you mention earlier, this plugin is an action plugin and isused for incidents ,can it affects schedule report deilvery.
I tried deleting existing schedule and creating new one but still the issue persist.This is happening for all the reports.
Any advice.
Best Regards,
Mangesh

Anonymous (login to see details)

extended email action plugin sample email body is as below
Was 7208.78 ms but should be higher than ? ms.

the default email plugin message body for same incident rule is as below
10% of all requests are observing response times higher than 7s 208ms. During the last 7d these requests could be served in 3s 148ms

How can we configured extended plugin message body similar to that of default email plugin.

Anonymous (login to see details)

Hi Mangesh,

Could you please set debugging level for the extended e-mail action plugin to FINER and send me log file? Could you please provide detailed information about configuration of the extended e-mail action plugin? I’ll update you after analyzing this information.

Anonymous (login to see details)

Hi Mangesh,

I'm following up on your post. Any updates on gathering log file with log level set to FINER for the plugin? Please provide it.

Please use value of the ${MESSAGE} variable to get message which triggered an incident. Additional information is captured in violation messages. Violation consists of violation header and violation message. Plugin captures up to 5 violations:

Anonymous (login to see details)

Anonymous (login to see details)

Hey Eugene,

Does this mean that we can't send emails to groups as defined within Dynatrace? i.e. emails can't be sent to users assigned to the "Incident Email Group"? This would be a useful feature as it would centralize the management of incident emails instead of editing each incident individually to add/remove users.

Anonymous (login to see details)

Anonymous (login to see details)

Is there a way this plug-in could be extended to allow the Profile Description text to be included in the email message? We're looking at a way of hacking the profile information model to support profile-wide attributes (name/value pairs) in support of notification processes. As a stop-gap we could do this by substituting in the profile description into the message, if the profile description contains machine-parseable name:value pairs.

Anonymous (login to see details)

Hi Jim,

Plugin maintains the ${SYSTEM_PROFILE} variable which is a name of the profile where incident was triggered. This variable can be used anywhere in the e-mail message. At the moment there is no access to the description field of the profile.

Anonymous (login to see details)

Hi Jim,

${VIOLATION_MESSAGE_1} through ${VIOLATION_MESSAGE_5} variables contain violation message or messages. Plugin maintains up to 5 top violation messages. Plugin does not maintain ${VIOLATION_MESSAGE} variable. In the plugin's jar file there is BodyExample.html page which could be used to display values of all maintained by the plugin variables.

It is good point about ${END_TIME} or any other time related variable when dynaTrace engine sends "Wed Dec 31 18:59.59 EST 1969" timestamp. We'll investigate possibility of making "Wed Dec 31 18:59.59 EST 1969" as a no value, i.e. "-".

In terms of a value of the ${AGENT_GROUP_NAME} variable: please see section 2 Filtering of the plugin documentation Extended Mail Action Plugin. Figure 3 on page 9 contains example when ${AGENT_GROUP_NAME} variable is getting populated by the plugin.

Anonymous (login to see details)

Anonymous (login to see details)

When filtering by host, agent, or agent groups, can I use a regex? For instance, if I had agent name "AgentX" and "AgentY", could I use a filter of "Agent*", or something comparible. I'm running into instances on the OOTB alerts where I don't have agent group as a potential filter.

Anonymous (login to see details)

Hi Shaun,

I've enhanced plugin and added support of regular expressions for filtering. For example, you can use regular expression "Agent[XY]" to add filter for AgentX and AgentY. Please see more about different regular expression constructs here.

In terms of OOTB incidents. Please note that there are some OOTB incidents which are not passing information about source of the incident to the plugin. As a result plugin cannot filter these incidents. We are working with the Lab to enhance interface between dynaTrace engine and plugins for all OOTB incidents. Until this is done, please test if plugin can filter OOTB incidents. Please see Note in the Filtering section on page 9 of the plugin's document.

Anonymous (login to see details)

Hi Jim,

Please download the latest version of the plugin's jar file which I've just updated, set the log level to FINER and re-run the test. Please send me stack trace and plugin's log file if you get exception again.

Anonymous (login to see details)

Anonymous (login to see details)

Sorry this is not a question, it's just what I am experiencing. For 5.0, right after installation this plugin works like a charm, however for 5.5 it doesn't work until we restart the dT server. Thought it would be good to leave a notes here in case people run into similar situation.

Anonymous (login to see details)

Hi Flora,

Thank you for sharing your experience with us. What you described is different from our experience. Could you please document steps you are following up and provide us with the matching plugin's log file which has logging level set to FINER?

Anonymous (login to see details)

Eugene, can we add a flag that turns off HTML formatting and sets the mime-type to plain ASCII? We're looking at leveraging this mechanism for an internal workflow for our ServiceManager integration, and HTML is causing the message to be broken up into multi-part messages, and then the formatting gets really screwing.

Our model is putting text in the prefix and text in the suffix, and nothing in the body, if that helps.

Anonymous (login to see details)

Hi Jim,

Use of plain ASCII text formatting in the e-mail is one of the things that we put on hold due to time constraints. However, now we will add it to the list of the enhancements and will implement it shortly.

Anonymous (login to see details)

We're testing this out with the Host CPU Unhealthy incident, and are testing out the incident begin/incident end and the GUID key to represent the incident. However, the email being generated by the plug-in for this incident always says 'ended'. I'm generating an email using the normal model, and it shows just a start time, as does the normal Incidents dashlet.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Jim,

Could you please check Incident settings and in Action tab please send me its screenshot or settings for the "Evaluation Timeframe" and "Period (seconds) to suppress further incidents after Incident End"? These values may affect premature action on dynaTrace engine side that incident has ended.

Could you please set logging level to FINER for the plugin and send me generated log file?

Anonymous (login to see details)

Anonymous (login to see details)

Hi Zoaib,

I've received your log file. Thank you. I also have analyzed it. Problem you are having is in the smtp mail server settings. Please check with LAN administrator exact setting of your smtp server. I'm sending you more details via e-mail.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Zohaib,

This tells me that you need to check if SMTP port provided in the plugin settings (i.e. in your case it is port 587) is correct. The Email Report Action plugin has a bug which causes for the default smtp port to be always used no matter which smtp port you have provided in the plugin settings.

Anonymous (login to see details)

Anonymous (login to see details)

We're comparing this plug-in to the default email plug-in, to understand how to get the best of both worlds. We are using the 'Host CPU Unhealthy' incident as the baseline.

Question: how do you get a list of all of the agents associated with an incident in the new Extended Email plugin? The ${ALL_AGENT_NAMES} attribute comes up blank, but we see a list of names in the normal email plugin:

Anonymous (login to see details)

Hi Jim,

This is a known deficiency of the dynaTrace implementation of the plugin interface. At the moment there are OOTB incidents which do not provide complete information about source of the incident to the plugin. For example, in your case we can get from dynaTrace engine only server name where incident has occurred but do not have information about affected agents. So, plugin is populating only SERVER_NAME variable and leaving AGENT_NAME/AGENT_HOST variables blank. There is no work around right now that plugin can get agent names to populate predefined variables.

We have mentioned about this deficiency two weeks ago in the reply to Shaun Gautz post on Aug 16, 2013. Please let us know your timeframe that we can prioritize work with the Lab to fix it.

Anonymous (login to see details)

RFE: Make the plug-in properties 'dynaTrace Server' and 'dynaTrace Server REST Port' available as substitution arguments. This will simplify the alert maintenance for hyperlinks back to the server for dashboards and reports. For example, I can build out my incidents in non-prod and simply copy them to my production server and it will work out of the box. Currently, I'd have to go in and hand-edit every incident body text to include the right dynaTrace server reference.

RFE: If dashboard names are specified, for PDF attachments, it might be nice to have the option to include hyperlinks generated for those dashboards, perhaps via a set of substitution variables: DASHBOARD_1, DASHBOARD_2, ALL_DASHBOARDS, etc. If HTML was disabled, then don't include the <a> references, but do include the http:// parts, comma-separated.

Anonymous (login to see details)

Hi Jim,

These are good points and we will adjust plugin to include them. We will add reference to the property file for the plugin which will contain key=value pairs instead of explicit parameters. In terms of dashboards: we definitely will add hyperlink variables. We also have upcoming enhancement which allows to get HTML, XLS, etc. types of reports beside PDF format.

Anonymous (login to see details)

Super! In terms of timing, we're looking to be able to roll this plug-in out for integration with our Incident Management and Workflow orchestration system as soon as possible; alerting is the last mile we need to close for dynaTrace to become more integral with our production operations teams.

In terms of priorities, here's our selfish perspective: the flag to turn off HTML, since HTML tags cause hiccups to our incident management HTML-based viewer. Then substitutors for the dynaTrace Server/Port Number since these values could show up in hundreds of individual incident definitions, and then the dashboards references, which can come much later.

Anonymous (login to see details)

Anonymous (login to see details)

Jim,

Requested enhancements will be ready by the end of this week, earlier next week. Ability to send notification e-mails in the non-HTML format (i.e. text/plain ASCII content) has been already implemented and tested.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Scott,

Unfortunately, because of the limitations of the dynaTrace plugin interface, plugin has no ability to get name of the Business Transaction which was involved in the incident. Plugin only marks if violated measure was part of business transaction in the body of the e-mail.

Anonymous (login to see details)

Thanks Eugene. The emails from the default Incident setup for 'Failure rate too high' and 'Response time degraded' list the business transaction on the email... so I was hoping we could use that in the Extended Email Action Plugin as well.

Anonymous (login to see details)

Eugene,

I'm trying to attach dynamic dashboards to alerts and when using ${APPLICATION} in the dashboard name, it is throwing a 500 error in the log, which leads me to believe its not translating the dynamic values.

Anonymous (login to see details)

Hi Scott,

The Extended EMail Action plugin does not support substitution of the predefined variables in the dashboard names which are passed as a "Dashboard Names" parameter to the plugin. However, it is easy to add this functionality to the plugin. This will allow use of ${variable-name} predefined variables in the dashboard names. I'll put your request in our pipe.

Could you please add Body Header Example.html as a "Body Header" parameter of the Extended EMail Action plugin? The ${DASHBOARD_URL_1} - ${DASHBOARD_URL_5} variables will show us dashboard names which were used by the dynaTrace engine when incident was triggered. This information will help us to answer on your question why 500 error was thrown in the log. Also please set logging level of the plugin to FINER and send me generated log file.

is explicit: the 500 response code is due to the dashboard not found on the server. Of course this error was thrown because ${APPLICATION} variable was not translated. You have identified it correctly.

To answer on your question about 5 dashboard URLs. Current version of the plugin allows to attach to a single e-mail multiple dashboards from the list of dashboards provided by the "Dashboard Names" parameter. There are no restrictions on the number of attached dashboards. For convenience, plugin also provides user with top 5 dashboards' URLs that he/she can use them in the body of the e-mail. Of course, user can construct links to the dashboards himself in the body of the e-mail. How to do it is shown in the plugin's examples. Again, 5 dashboards' URLs are provided for convenience. Let me know if it is a limitation for you. We will remove this limitation as well.

Anonymous (login to see details)

Hi There,

Thanks for this plugin it's really a big improvement on the standard e-mail plugin.

Just one question, I am unable to to use the Filter by AgentGroups feature in the plugin, I tried the following on an incident for "Disk Storage Utilization", by using the Case sensitive name of one of the agent groups:

Anonymous (login to see details)

Hi Richard,

Please make sure that the "calculate only for selected agent groups" option is selected with the list of the agent groups, e.g. see Figure 3 "Measure configuration for agent groups" on page 10 of the plugin's documentation here. Please let me know if you still have problems.

Anonymous (login to see details)

Hi Tanapon,

Here are answers:

Example of the customized e-mail body from the plugin's documentation contains footer already. Plugin adds default footer to the e-mail if the Body Footer parameter is empty. So, if you set the Body Footer parameter to something like "<table></table>" then double links at the end of the message will disappear.Please also use the following BodyExample.html file as body of your e-mail. It is slightly modified version of the example presented in the plugin's documentation.

The ${IMAGE_WARNING_OK} variable contains link to the red or green icons depending on if incident is open (red icon) or closed (green icon). If you need to put in the e-mail image of the red icon, please use the following link "res/notification_email_warning.png". For the green icon link is "res/notification_email_ok.png". These icons are in the "res" directory of the jar file.

The ${INCIDENT_STARTED_ENDED} variable has two following values: started/ended depending on status of the incident. Incident status is shown in the ${IS_OPEN} and ${IS_CLOSED} boolean variables.

For the built-in OOTB incidents ${MESSAGE} variable contains violation message. Please use it in your customized notification e-mails for the built-in OOTB incidents. Please see example of the e-mail for an OOTB incident with ${MESSAGE} variable containing violation message here. Example of the e-mail for a non-OOTB incidents which contains violation message in the ${VIOLATION_MESSAGE_1} variable is here.

Anonymous (login to see details)

Hi Eugene,

thanks for developing this plugin!

I have found a big problem: I want to send some Incident Mails in HTML Mail Format, but the Plugin only executes the teardown method instead of sending a mail before the teardown mehtod. Plain Text Mails were sent successfully. Is this a known issue?I use the latest plugin version and dynaTrace 5.6.5713.

Anonymous (login to see details)

Hi Eugene,

i rechecked the Plugin configuration and used your example Emailtemplate. Now everything works fine.I thought the header of the incident mail have to start with a Doctype and <html> tags etc like this:

Anonymous (login to see details)

Anonymous (login to see details)

Hi Zohaib,

The com.dynatrace.diagnostics.plugins.extendedmailreport.domain.ActionRecord class contains the "sources" field which implements java.util.Map. The "sources" field contains all agent names which contributed in the incident.

Anonymous (login to see details)

Hi,

We use the extended email action plugin without any problem for incidents based on business transactions. When we want to use the plugin to send mails based on measures done by the websphere mq monitor, the mails are not send when an incident occurs.

Anonymous (login to see details)

Hi Joachim,

Plugin should work with incidents which are based on measures created by WebSphere MQ Monitor. Please deploy the latest version of the plugin, setup plugin's log level to FINER, reproduce this issue, and send me plugin's log file.

2014-02-17 09:50:58 FINER [ActionHelper@com.dynatrace.diagnostics.plugins.extendedmailreport.action] addSource method: add host to the ALL_HOSTS variable of the SourceType Server is not defined yet because sourceReference object is null

2014-02-17 09:50:58 FINER [ActionHelper@com.dynatrace.diagnostics.plugins.extendedmailreport.action] addSource method: add host to the ALL_HOSTS variable of the SourceType Server is not defined yet because sourceReference object is null

Anonymous (login to see details)

The error appeared to be the exact same. Version of the plugin is 0.9.7. We are going to try the new version:

2014-04-14 09:02:36 SEVERE [Action@com.dynatrace.diagnostics.plugins.extendedmailreport.action] execute method: java.lang.IndexOutOfBoundsException exception occurred. Message = 'Index: 1, Size: 1'; Stacktrace is 'java.lang.IndexOutOfBoundsException: Index: 1, Size: 1 at java.util.ArrayList.RangeCheck(ArrayList.java:547) at java.util.ArrayList.get(ArrayList.java:322) at com.dynatrace.diagnostics.plugin.actionhelper.ActionHelper.populateSubstituterMap(ActionHelper.java:719) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.execute(MailExecutor.java:179) at com.dynatrace.diagnostics.plugins.extendedmailreport.ExtendedMailAction.execute(ExtendedMailAction.java:66) at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:745) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:32) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:14) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:192) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:415) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:339) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241) at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

Anonymous (login to see details)

Anonymous (login to see details)

We have upgraded to the latest release and now are seeing the following error when trying to send an HTML email notification:

2014-05-08 14:26:22 SEVERE [MailExecutor@com.dynatrace.diagnostics.plugins.extendedmailreport.action] execute method: java.lang.NullPointerException exception occurred. Message = '-'; Stacktrace is 'java.lang.NullPointerException at org.apache.commons.io.FileUtils.copyURLToFile(FileUtils.java:1460) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.getFile(MailExecutor.java:1011) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.setEmailBody(MailExecutor.java:973) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.sendMailAction(MailExecutor.java:641) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.processIncident(MailExecutor.java:589) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.sendMail(MailExecutor.java:209) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.execute(MailExecutor.java:181) at com.dynatrace.diagnostics.plugins.extendedmailreport.ExtendedMailAction.execute(ExtendedMailAction.java:76) at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:745) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:32) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:14) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:192) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:415) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:339) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241) at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)

FYI - I set the logging level to FINER and there were no further details.

Anonymous (login to see details)

Anonymous (login to see details)

Hi PTC Support,

This is exactly right. Missing file is 'res/notification_email_excl.png'. I saw yesterday that problem was in the missing image files. So, new logging level helped to find exact names of the files which are missing in the "res" directory.

Anonymous (login to see details)

I've been testing the filters. I have a problem with the way it works if you use two filters at the same time. I tried using both an agent name filter and a host name filter. It appears to be matching if it fits either filter. I need it to match if it fits both filters. Is this working by design?

Anonymous (login to see details)

Anonymous (login to see details)

Hi Shaun,

This behavior is by design. Filters are applying to one category of incident's sources, i.e. agents, agent groups, monitors, collectors, and servers. Result will be concatenation of different categories of sources.

Anonymous (login to see details)

Hi Eugene,

I have been testing your plugin a bit further and came across a problem with the filtering criteria.

We have different teams administering different applications and I am trying to send alerts based on the built in incident "Response Time Degraded" so that it will only trigger an alert for that application to the relevant team. The group I am testing this on is called "DCS" so I have the plugin configured to filter on the DCS agentgroup.

The applications response time is based on a business transaction that is splitting by URI by application.

On our application dashboard this is showing perfectly but when the response time threshold is breached it is not triggering the alert?

Below you will see the relevant plugin logfile extract for this occurance:

Anonymous (login to see details)

Hi Gert,

Have you tried Agent based monitoring when the target host has at least one active and connected Agent? Please see Agent based monitoring page for details.

If your incident rule is based on the Agent less measures and not on the Agent based measures, you will not be able to get agent group names. Example of Agent less measures are measures provided by Windows Performance Monitor and Unix Monitor plugins.

Anonymous (login to see details)

Hi Anton,

Please do not specify agent name os123@dhvvvvfan01 in the list of agent names in the plugin's agent names filter field (i.e. plugin's parameter field is "Agents"). If you are using Java regular expressions, make sure that they will not allow the agent name os123@dhvvvvfan01 to be selected.

Anonymous (login to see details)

Hi Eugene

I want to specify that the Alert should be sent out if ANY agent has an incident raised EXCEPT this one. I have over 2000 agents I am monitoring and cannot specify them all. I have read the Java expression doc and examples, but I do not understand how to syntax for this specific field in the Plugin works.

Do I specify it as "^dhvvvvfan01" or [^dhvvvvfan01]? I think I have tried every way I can think of...

Anonymous (login to see details)

Hi Eugene,

I tried the regular expression which you suggested in the above post. Even when the agent name contains the string CHDD-ES0, I am receiving an email. Should I include "" in the regex for it to work? Below is part of my filter.xml file.

Anonymous (login to see details)

Hi Anton,

There are few ways of doing it. First (and it is the recommended way) is to use regular steps of dynaTrace client to setup default value of the parameter in question through the multiline parameter menu and paste or import content from the file there.

Second way is to use dynaTrace PDE and paste content for the parameter in question through the PDE menu. PDE will embed default content directly to the plugin.xml file. The first way is preferable because it applies only to the specific plugin deployment while the second way applies to every plugin deployment. As far as I know you can paste very large files there (>1MB).

Please note that you cannot edit default value of the parameter in the plugin.xml file with an editor unless you encode data of the default value.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene,

Would the filtering work for the out of the box incidents (e.g. Application Process Unavailable), because you are not able to select "Create a Measure for Each Agent" or select agent groups for these incidents.

Anonymous (login to see details)

Hi Wayne,

Yes, filtering based on agent names should work for this specific out of the box incident. I have attached an example of the e-mail from one of the tests that we are performing on the Extended Mail Action plugin. This e-mail shows list of the predefined variables which were populated by the "Application Process Unavailable (unexpected)" incident. Please note that the ${AGENT_NAME_1} or ${AGENT_NAME} were populated with the name of the agent where incident occurred. So, you can filter e-mails from the Extended Mail Action plugin by agent names.

There is a known deficiency in the dynaTrace plugin interface which does not allow to get source of the incident on the plugin side. In order to check if the incident in question is affected by this deficiency please do the following:

Cut and paste the following body header to the Body Header parameter of the Extended Mail Action plugin;

Trigger the incident in question;

Check if predefined variables are populated.

If they are populated, you can use filtering for this specific out of the box incident.

If they are not populated, then this is a dynaTrace plugin interface deficiency.

Anonymous (login to see details)

Hi John,

Most likely "Agents" filter prevents you from receiving e-mail notifications. Could you please send me configuration settings screenshot of the plugin that I can check "Agents" filter settings? You also can export the system profile and send me xml file. Please set plugin log level to FINER and send me gathered log file. Please send all files to my e-mail eugene.turetsky@dynatrace.com.

One more thing: could you please set the Email Notification plugin and send me its notification e-mail?

Anonymous (login to see details)

Hi Zohaib,

The Extended Mail Action plugin sends attachments in Dynatrace 6.0. I've just re-checked it and was able to get attachment as a PDF file. Please set plugin's log level to FINER and watch for the following line:

Anonymous (login to see details)

I have an incident that fires off based on 2 different measures:

Time of Foo andInvocation of Bar

I'm trying to setup the body of my email to only show the measurement of the time value. Using VIOLATED_MEASURE_VALUE it always returns the invocation value (NaN), it doesn't matter the order they are specified in the conditions. VIOLATED_MEASURE_VALUE_ALL shows both so that doesn't work. I was also playing with measureNamePatterns to see if I could filter what values are displayed based on the measure name. I used "Time of Foo" for the pattern. I tried that with both VALUE and VALUE_ALL and it didn't do what I was hoping for either. Is there any way to display just the one measure value?

Anonymous (login to see details)

Hi Pat,

Could you forward me e-mail that you are receiving from the Extended Mail Action plugin? My e-mail address is eugene.turetsky@dynatrace.com. Please cut and paste content of the following link BodyHeaderExample.html into the Body Header parameter of the plugin before triggering your incidents.

Anonymous (login to see details)

Thanks Eugene,

After adding all of the measures to the header it worked! So from there I found that if we just include VIOLATED_MEASURE_NAME_ALL in the email body it also works. We don't want it displayed in the email so I just hid it with an HTML comment.

Anonymous (login to see details)

Anonymous (login to see details)

In the Email-Filters Dependency File XML , is it possible to identify agent groups based on regex? I have multiple agent groups that all start with the same three letters and it would be convenient to pair the email recipients to any agent group that has this specific three letter pattern in the beginning of the agent name. If not regex, then I will need to update the XML to include additional agent groups that may be added to the incident n the future.

Anonymous (login to see details)

Anonymous (login to see details)

I am having difficulty splitting email alerts that are triggered from host measures. If there is a high CPU alert(from a custom incident) I want to email certain teams depending upon the name of the host which has high CPU/Memory/Disk. When I create host measures, they are created for all hosts, and the alerts for every host are sent to all emails regardless of which team they are. Currently, it seems that the Dependency file can only filter on Agent name, and not on the host name of the host measure.

Is it possible to filter on host names from host measures in the dependency file?

Anonymous (login to see details)

Hi Eric,

Yes, it is possible to filter incidents by host names if dynaTrace engine passes to the plugin through the plugin interface host names of the incidents which you are using. Plugin can filter incidents by agent's host name, monitor's host name, collector's host name, or incident server name. To check it please cut and paste into the Body Header parameter of the plugin, using your favorite editor, the following html file located here. Remove all filters, trigger the incident in question and send me notification e-mail that was sent by the plugin. My e-mail address is eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Hey Eugene,

First off, great work on this plugin! It has helped me at multiple client sites to expand past the functionality of the embedded email action.

Secondly, is it possible to pass in PurePath detail data such as exception messages or log messages into the email? My current guess is that this is not possible since this data is stored within the PW while the details are stored within the session storage. The only way I think this may be possible is so attach a dashboard with the applicable filters to the email, showing the detailed data. What are your thoughts?

Anonymous (login to see details)

Hi Joshua,

Out of the box the Extended Mail Action plugin works with data which it receives from the Dynatrace engine, i.e. instances which implement the the com.dynatrace.diagnostics.pdk.Instance interface, the com.dynatrace.diagnostics.pdk.Violation interface, etc. These objects contain detailed information about the incident, e.g. for the measure based violations these are values which triggered violation, violated thresholds, message of the incident, etc.

In your case, violations are event based, so, the quickest way is to create a custom action plugin which will do the work you are looking for. It is easy but I do need more details about what you are trying to accomplish in order to provide you a plugin which satisfies your requirements. So, please feel free to send me details directly at eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Hi Eugene,

Regarding Josh's post, I am also looking to add the exception messages which trigger the incident into the email body. Are there any variables in the plugin that would allow the message of the exception to be displayed in the email without using a report?

Anonymous (login to see details)

Hi Eugene,

This plugin works great. Thanks for creating it.

I have the emails and filters coupled working, but the email alert does not seem to work as I need it to when I have smart alerting turned on. Specific hosts' metrics are assigned to an email group. I would like to have smart alerting turned on, in order to not flood inboxes. It seems that the once the alert is triggered for one host and the email s sent, no other emails are sent when other different hosts violate the metric threshold. Is this possible to achieve without creating multiple incidents for each host group?

Anonymous (login to see details)

Hi Eric,

The smart alerting requires manual confirmation of triggered incidents. Until this is done no new incidents will be triggered. Please look into the setting up the Evaluation Timeframe, Period (seconds) to suppress further Incidents, after Incident End, and Aggregation from the Edit Incident Rule screen to avoid flood of e-mails.

Anonymous (login to see details)

Hello Eugene,

Thank you for help in setting up the MQ plugin and extended email plugin. I am still working on it and have couple of questions.

I am having issues setting up the filters for sendOnlyPatterns. I want the email to be sent if the pattern matches ".*BACKOUT.*" for the Queue. But not getting any email. If I take out this pattern I am getting the emails for all the Queues. Basically I am trying to create an Incident/email for BACKOUT only Queues and other for rest of the Queues.

Anonymous (login to see details)

Hi Madhu,

Could you please send me screenshot of the plugin's configuration parameters? I'm particular interested in the sendOnlyPatterns parameter. Also, could you please let me know which version of the Email Action plugin are you using? Please feel free to send me e-mail directly to eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Is there an easy way to send test e-mails through the plugin? I have not been able to figure one out and am trying to work through the initial setup to just get the plugin working however having to wait between errors can be frustrating. I suppose I could set an incident on some random measure that happens all the time but it would be nice if there was just a send test e-mail feature.

Anonymous (login to see details)

Hi Jared,

If you use the Dynatrace PDE, you will be able to emulate an incident and trigger a notification e-mail. Please see this link about the Dynatrace PDE. Note, that PDE does not emulate a real incident, so, you may not have all runtime environment variables which you are interested in populated by the PDE.

because there is no the dynatrace_logo.png file in the res directory in the jar file. Please change this line to <img style="margin-top: 20px;" src="dtbundleresource:res/logo.png"> if you are using the latest plugin release 0.9.9.21. Please also see the first bullet in this post to avoid duplication of the e-mail's Footer page.

An example of the body of the Extended Mail Action plugin which is referenced on the plugin's wiki page by the following link is slightly outdated and needs to be synchronized with the most recent plugin releases.

Anonymous (login to see details)

This and this are the formats I am currently trying. I am getting the e-mails to send and they are appending a portion of the body, however, it seems that pieces after line 7/9 respectively are not working. Are <html> and <body> requirements for formatting? I notice in the old documentation none of the screenshots have the html check box and some examples don't have the body tag. I have mostly copied and then updated the format from examples already given in the documentation.

I have finer logging turned on and the e-mail sends. I know it displays correctly using an html editor so I think I just have it improperly formatted for this plugin. Here is all the log shows(e-mail and server info removed for privacy).

Anonymous (login to see details)

Hi Jared,

The plugin adds <html>, <head>, and <body> tags itself, so, you don't need to add them into the customized body of the e-mail. Please see this screenshot for details.

I also added into the release 0.9.9.22 additional FINER level log messages to get the HTML body as it is composed by the plugin. Please deploy it, set the FINER level logging for the plugin, trigger the incident and send me the plugin's log file to eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Actually I was looking at the source code and realized that the data is there. It seems to be an issue with the way outlook 2010 is formatting the e-mail. If I choose to view in browser, or send it to my gmail the e-mail displays correctly, but in outlook everything below the main description appears to be gone. My outlook is set to display e-mail in HTML so I will see what I can do.

Anonymous (login to see details)

Hi Jared,

I don't see FINER log messages with the content of the HTML file in the plugin's log file from your post above. I have made slight changes in the level of logging and rebuild the 0.9.9.22 jar file. Please deploy it from here, trigger the incident and post the log file here. I'd like you to get an HTML file of the e-mail body as it is generated by the plugin. This will help you to address the issue possibly to MS team.

Anonymous (login to see details)

i do have the plugin setup with the latest version and loglevel is set to finer(at least at the plugin screen). Is there anywhere else I need to set log level outside of server>plugins>select extendedmailactionplugin>properties>loglevel?

All logs that I am currently seeing all have the same info as the previously posted one here.

Anonymous (login to see details)

I know the host info is showing blank but that is intended for this specific alert from testing and the errors are not host specific.

The only other thing I am noticing is that the Initial .png for the alert(the red !) is not appearing in the browser view of e-mails and in gmail it is shown as an attachment where the others are built into the e-mail.

Further I want to add, incidence once begun stops only when incidence has been ended. The action tab is capable only to send email on begin and/or on end of incidence.

We faced many situations when a sub-system failed and all of sudden too many depended transactions start failing. In such case only two incidence alerts were being sent on indicating beginning and ending of failure. In between there were no alert. Hence Our production support teams have no ways to know if incidence is being continued and how many fails occurred in last 2 minutes during system crash(in between start and ending).

How about a 'task' tab, just like an action tab? In case of bulk failure, task would be scheduled for particular time period indicating failures which in turn would fill the gap. Task would stop as soon as incidence is ended.

Anonymous (login to see details)

Hey Eugene,

Great work on the plugin! Just wondering if it was possible to embed a chart within the alert. In other words, would it be possible to run a HTML report and then embed that report instead of attaching it? With this method, my thinking is that you could create a dashboard with only one chart in it and simply embed that chart using your plugin into the email alert, eliminating the need for attachments all while providing a nice visual view of the issue.

Anonymous (login to see details)

Hi Joshua,

We have customers asking about this feature as well. We definitely can do that. I'll put this request in my pipe to implement. Please let me know if you have any deadline when you need this feature to be implemented. Otherwise I'll implement it in next few weeks.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene,

My customer's Outlook keeps flagging messages sent with this plugin as phishing messages and blocking all images and links. Outlook does not flag standard Dynatrace emails, and both types of emails are sent from the same email address. I have customized the email body though. Is this something you have run into before, or is this something particular to my customer's email filters that I'll have to take up with them?

Anonymous (login to see details)

Yeah, they are using Outlook 2010 as well, but I was just wondering if there was a way to prevent the flagging in the first place; I would rather not require every single alert recipient to have to add Dynatrace emails to their safe sender list if I can help it. Thanks though, if I can't figure that out it's still a decent option.

Anonymous (login to see details)

An exchange administrator can set group policy for a safe sender list. If they do that already, they can add that address for all users if it is a very large amount of people. You can also try looking at the properties of each e-mail by opening the plugin e-mail and default one and doing file>properties and looking at the header info to make sure it matches. If you have them sending from different places I could see that causing an issue.

Anonymous (login to see details)

I have a measure that is calculated for all applications, and can be split by application, but the ${application} variable returns "-" for some applications and names for others. When I have an incident that has both applications occur and I use ${APPLICATION_ALL} it shows -, Application X. Do I need to create separate measures for each application I want this for and have them alert separately then manually set the e-mail with the application name?

EDIT: In a dashboard the application shows up asApplication Y but e-mail shows "-" when it should also show Application Y.

The measure I am doing is a custom measure for Throwable class: System.TimeoutException.

I tried the following variable formats and both returned "-". For Application Y it won't show application name, it just says" Custom - Timeout Exception:" but Application X shows "Custom - Timeout Exception application X:"

<tr>

<td style="vertical-align: top; width: 180px;">

<div style="font-size: 0.8em;">Application:

</div>

</td>

<td>

<div style="font-size: 0.8em;">${APPLICATION}</div>

</td>

</tr>

and also

<tr>

<td style="vertical-align: top; width: 180px;">

<div style="font-size: 0.8em;">Application(all):

</div>

</td>

<td>

<div style="font-size: 0.8em;">${APPLICATION_ALL}</div>

</td>

</tr>

<tr>

EDIT: Now that I look at details of measurements on dashboards, Application Y lists itself as Agent group or Monitor: <all-agents> where Application X shows the correct name under agent group/monitor. Both are manually created applications and not automatically detected.

Anonymous (login to see details)

Could you please provide version of the Dynatrace product and version of the Extended EMail Action plugin that you are using?

Could you please perform the following steps?

Cut and paste the following body header into the Body Header parameter of the Extended EMail Action plugin;

Trigger each incident that you are using;

Send me notification e-mails that you will be receiving from the Extended EMail Action plugin.

Provide details of your incidents, i.e. screenshot of the Configuration and Details tabs of each incident rule. I'm specifically interested in settings in the Applications section of the Details tab (see here).

Anonymous (login to see details)

Anonymous (login to see details)

Hi Rick,

We left for the user to choose exact content of the "Incident Rule Name" parameter hence giving him/her flexibility to add some flavors into the name. In terms of documentation, please look into the Release Notes of the 0.9.9.8 - 0.9.12 versions of the plugin at the top of this page. You should find the following explanation:

Anonymous (login to see details)

Anonymous (login to see details)

Hi Rajesh,

The up to date list of supported by the plugin runtime variables is in the sub-bullet 3 of the 'Usage' section at the top of this page. An example of the Body Header which includes all these variables as a HTML table please find here.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Keerti,

The "Quiet Time From" and "Quiet Time To" parameters are like a schedule - they do not have timezone. Please note that the Dynatrace scheduler also has no timezone parameter. The timezone for the "Quiet Time From" and "Quiet Time To" is a timezone used by the Dynatrace server JVM.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Beth,

The "Host Name to IP Address Translation" parameter is list of the <server-name>=<ip-address> pairs. This parameter is used by our customers when they need to know servers' IP addresses instead of or in conjunction with their DNS names in the following cases:

DNS names cannot be translated into IP addresses from the Dynatrace server box;

server has multiple NIC interfaces.

If you'd like to use file to import data for the "Host Name to IP Address Translation" parameter then every record of this file should have only one <server-name>=<ip-address> pair. There are no limits on number of records in the file.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Beth,

As I said in my previous post every record of the text input for the "Host Name to IP Address Translation" parameter should have only one<server-name>=<ip-address> pair. Please see the following screenshot as an example of the "Host Name to IP Address Translation" parameter settings.

In terms of the XML files: please see the following screenshot of the Release notes for the version 0.9.9.8 - 0.9.9.12 which are located at the top of this page:

Highlighted in yellow statement contains link to the XSD schema for the the Email-Filters Dependency file. The next statement in the screenshot contains link that you can use to validate correctness of your XML document. Please also see "Java utility which verifies correctness of the Email-Filters Dependency File" section at the top of this page.

For the Thresholds XML file please read the Release notes for the version 0.9.9.18 of the plugin at the top of this page:

Highlighted in yellow link is the link to the XSD schema for the Thresholds XML file.

Anonymous (login to see details)

Hi Beth,

Could you please clarify what do you mean by "using a standard metric" in the first statement of your post above? Could you please provide details of your incident rule that the Extended Mail Action plugin is associated with?

Please note that the "ThresholdsFile" parameter and hence thresholds described in this file are working with the Dynatrace dynamic measures (see Release notes for version 0.9.9.18 of the plugin at the top of this page).

Anonymous (login to see details)

Anonymous (login to see details)

Hi,

To be clear, I understand the process of adding the Extended Email action to an Incident and the specification of a Threshold file. I'd like just 1 example threshold setting based on any metric used by any out-of-the-box Incident.

Anonymous (login to see details)

Hi Beth,

The out of the box incidents are incidents which are built-in in the product. They are usually event based incidents. In your post above did you mean built-in in the product incidents? If yes, then the "ThresholdsFile" parameter of the plugin is not applicable there because as I mentioned in my reply on your original post above that the "ThresholdsFile" parameter and hence thresholds described in its file are working with the Dynatrace dynamic measures.

Also I would like to re-iterate my request for you to provide details of your incident rule that the Extended Mail Action plugin is associated with. It is a prerequisite for this discussion.

Example of setting up the "ThresholdsFile" parameter explained in the Release notes for version 0.9.9.18 of the plugin at the top of this page. Below highlighted in yellow are links to the screenshots and file examples that you are looking for. You could deploy this "HelloWorld" like plugin which was built on 01/06/2015 for testing of the "ThresholdsFile" feature in the Release 0.9.9.18 of the plugin. Please use this plugin in conjunction with the files which are highlighted in yellow below.

Is there anything I can enable to see further info on the logs? The event is not even being triggered (it should with the "1" value threshold)

Which of these "identificators" does the XML expect?

com.dynatrace.diagnostics.core.realtime.measures.MeasureReference@2b2e2c82[displayName=Client side current connections [Virtual Server->CB_BUSCA_HTTP] (Viprion Big IP@viprion)keyId=Client side current connectionsparentKeyId=Client side current connections revision=c8988f6f-a662-4f3f-ab9d-202a6180c848]

Anonymous (login to see details)

Hi David,

Please download and deploy version 0.9.10.0 of the Extended Mail Action plugin from here and re-run your test. No need to change log level of the plugin. It will produce log file with the default log level.

Please gather plugin's log file and send it directly to me. You may need to zip it before sending.

Anonymous (login to see details)

Hi Eugene,

The URL Monitor and the Log File Scraper are not sending out emails with the Extended Email Plugin, but the emails are being for the same incident with the default Email Plugin. Can you please help us find the issue?

Anonymous (login to see details)

Is the Extended Mail Action plugin configured with using filters in both of your cases? If yes, could you please do the following steps:

Pick up one of two incident rules which you have issue with, e.g. an incident rule which is based on the URL Monitor.

Attach screenshots of filters which you setup for this incident or an XML file if you use it for filtering;

Disable filters;

Cut and paste the following body header to the Body Header parameter of the Extended Mail Action plugin;

Set plugin's log level to FINER;

Trigger the incident;

Attach the log file of the plugin to this post.

If filters are not used in the Extended Mail Action plugin then please check settings related to your mail server. They should be identical to the settings used in the Dynatrace server. In this case, please set plugin log level to FINER, trigger the incident and attach to your post the plugin's FINER log file. Attach also screenshot with the parameters related to the mail server.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Renato,

As of now, plugin will not embed dashboard into the body of the e-mail. You can only attach them to the e-mail. However, there are requests from other customers, e.g. see this post, which are asking for this feature. Let me see if I can add it to the plugin.

Anonymous (login to see details)

Hi Eugene,

Extened Email Plugin has not been working since the Dynatrace upgrade to 6.2. I followed your suggestion of upgrading the version of extended email plugin in 6.1 to 9.10 and then doing an automated migration. Can you please help me fix the issue? It is a little urgent since all our email alerts use the plugin.

Anonymous (login to see details)

What errors you are getting in logs? Have you tried removing or replace the old plugin (after migration) with newer one?

We upgraded from 6.0 to 6.1 and I remember we had to remove old plugin and imported new one. That also caused us to remove the Email Action in each incident and add newer version of email action. I hope you don't have to go through this.

Anonymous (login to see details)

Hi Rajesh,

Have you looked into this article when migrating from one release of Dynatrace server to another? It should help you to avoid recreating actions in the new release. The dtmigration script did not migrate plugins which have four digit versions.

Anonymous (login to see details)

Hi Keerti,

Please provide details about the issue, e.g. was plugin version 0.9.10 migrated to a new Dynatrace server? If not, please open support ticket to investigate it further. If plugin was migrated successfully but notification e-mails are not sent, please set plugin's log level to FINER and post log file here.

Anonymous (login to see details)

Anonymous (login to see details)

We'd went back and upgraded the plugin to the 0.9.10 version so the migration process would work (3 digit, not 4).

FINER logging for the plugin didn't reveal the issue as the error only showed up (with normal logging) in the Server log.

What I found was that the migration hadn't moved over one of the plugin's dependent libraries/jars. Once I copied that library/jar manually into the plugin's lib directory, the issue was resolved. That library/jar also had a 4 digit version number.

Anonymous (login to see details)

Hi Beth,

Thank you for providing details. From your previous post I can see that plugin wasn't migrated successfully to the new Dynatrace server using the dtmigration script. Please note that there are no any restrictions on the naming convention of jar files which are used internally by the plugin. So, it is not clear right now what was the issue during plugin migration in your environment. Could you please open support ticket to investigate it further because issue you are describing is related to the dtmigration script.

Anonymous (login to see details)

Anonymous (login to see details)

Hey Eugene,

I am trying to send the OOTB agent specific incidents to app owners with the XML filtering option. Even though it seems to correctly filter on the right emails, the logs report that the emails are never sent. See below:

Anonymous (login to see details)

Hi Eric,

The "Incident(s) were raised but notification e-mail was not sent" message means that notification e-mails were not sent for some incidents. Could you please send me FINER log file with this message at eugene.turetsky@dynatrace.com?

The "roleKey or scheduleKey of plugin is null. Can not log out in specified logfile for plugin" is a harmless message which should be ignored. It is coming from the product code, i.e. from the com.dynatrace.diagnostics.sdk.UserPluginManager class. You can see this message for every executed plugin. It will be fixed by the Dynatrace development team in the next available fixpack.

Anonymous (login to see details)

Messages that you are referring to are not error messages. They are FINER and WARNING level messages. There are no exceptions or errors thrown by the plugin in the excerpt that you have posted above.

The log message "2015-09-30 18:39:18 WARNING [MailExecutor@com.dynatrace.diagnostics.plugins.extendedmailreport.action] execute method: Incident(s) were raised but notification e-mail was not sent." is telling that incident(s) were raised but they did not match any of the filtering conditions, hence notification e-mails were not sent.

The "2015-09-30 18:39:18 WARNING [UserPluginManager@com.dynatrace.diagnostics.plugins.extendedmailreport.action] roleKey or scheduleKey of plugin is null. Can not log out in specified logfile for plugin" warning message is harmless and should be ignored. This message appears for all plugins. There is a bug in the DT 6.2 engine code which produces this message. More specifically, the warning is coming from the com.dynatrace.diagnostics.sdk.UserPluginManager class. Again, it is harmless. Please ignore it. It will be fixed in the next available fixpack.

Anonymous (login to see details)

Hi Keerti,

Yes, the following message "2015-09-30 18:35:40 FINER [ActionHelper@com.dynatrace.diagnostics.plugins.extendedmailreport.action] translateHostNameToIpAddress method: UnknownHostException exception for the DNS name 'keerti-es01', message is 'keerti-es01'" is telling that provided DNS name 'keerti-es01' cannot be translated to the IP address from the Dynatrace server. Hence the appropriate variable from the list of the following variables AGENT_HOST_IP_ADDRESS..., MONITOR_HOST_IP_ADDRESS..., COLLECTOR_HOST_IP_ADDRESS..., AND SERVER_HOST_IP_ADDRESS... will have "-"(dash) value. Hence, it is internal FINER level message.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene,

I am getting the below error and not receiving emails for Log monitor plugin. Can you please help me find the issue?

2015-10-01 17:04:33 FINER [HelperUtils@com.dynatrace.diagnostics.plugins.extendedmailreport.action] Entering getExceptionAsString method2015-10-01 17:04:33 FINER [HelperUtils@com.dynatrace.diagnostics.plugins.extendedmailreport.action] Entering getStackTraceAsString method2015-10-01 17:04:33 SEVERE [MailExecutor@com.dynatrace.diagnostics.plugins.extendedmailreport.action] setEmailBody method: java.lang.NullPointerException exception occurred. Message = '-'; Stacktrace is 'java.lang.NullPointerException at org.apache.commons.io.FileUtils.copyURLToFile(FileUtils.java:1460) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.getFile(MailExecutor.java:1711) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.setEmailBody(MailExecutor.java:1673) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.sendMailAction(MailExecutor.java:1317) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.processIncident(MailExecutor.java:1265) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.sendMail(MailExecutor.java:602) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.processEmails(MailExecutor.java:570) at com.dynatrace.diagnostics.plugins.extendedmailreport.MailExecutor.execute(MailExecutor.java:462) at com.dynatrace.diagnostics.plugins.extendedmailreport.ExtendedMailAction.execute(ExtendedMailAction.java:77) at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:812) at com.dynatrace.diagnostics.sdk.UserPluginManager.b(SourceFile:494) at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:347) at com.dynatrace.diagnostics.sdk.UserPluginManager.a(SourceFile:329) at com.dynatrace.diagnostics.sdk.UserPluginManager.executePlugin(SourceFile:281) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:31) at com.dynatrace.diagnostics.sdk.ActionPluginExecutor.execute(SourceFile:13) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:190) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.a(SourceFile:413) at com.dynatrace.diagnostics.scheduling.impl.ServerJobCenterRegistry.execute(SourceFile:337) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.a(SourceFile:101) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.work(SourceFile:92) at com.dynatrace.diagnostics.scheduling.impl.SchedulerJob.executeJobInfo(SourceFile:241) at com.dynatrace.diagnostics.scheduling.impl.QuartzJob.execute(SourceFile:45) at org.quartz.core.JobRunShell.run(JobRunShell.java:202) at com.dynatrace.diagnostics.scheduling.impl.QuartzThreadPool$WorkerThread.run(SourceFile:788)'

Anonymous (login to see details)

Hi Eugene,

We want to receive the incidents in the incidents dashlet but suppress the extended email plugin from sending emails during downtime. I want to set one downtime for weekdays and a different downtime for weekends. How do I set two downtimes in the plugin for each alert?

Anonymous (login to see details)

Hi Keerti,

Plugin does not have suppression intervals for weekdays and weekends. It has only one type of suppression intervals which works for all days in the week.You can use these suppression intervals for weekdays.

Anonymous (login to see details)

How does the plugin handle multiple conditions on an incident? I'm only seeing one option for VIOLATED_MEASURE_VALUE and THRESHOLD. I tested it and it looks like the multiple HEADER and MESSAGE parameters work, but the VIOLATED_MEASURE is sometimes the first condition, and sometimes the second.

Here is my scenario. I want to display the current value of both conditions in the email. The HEADER and MESSAGE parameters include that value, but also include a bunch of other text.

Anonymous (login to see details)

That works for the thresholds, but I'm looking to display the current value of each condition. For example, response time is 6 sec and count is 10. This would be similar to DCRUM alerting where you can display an auxiliary metric.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene,

I want to change the "Open in browser" and "Open in Dynatrace" links in the footer such that they take me to the dashboard related to the alert. Could you please provide me the current footer code so I could modify it to include my own URLs.

Anonymous (login to see details)

Hi Keerti,

There is no current footer code separated from the plugin. There is a way to provide your own header, body, and footer of a notification e-mail. Examples are in the Configuration section at the top of this page. Also, please see this post for more details about having your own footer.

Anonymous (login to see details)

Hi Jonathan,

The measure based incident's thresholds are evaluated every 10 seconds. Action plugins are executed on the following events:

on incident begin;

on incident end;

on incident begin and end.

As a result, the Extended Mail Action plugin, which is an action, is invoked only on one of the above events. We have developed custom monitor plugins which can send e-mail notifications between 'on incident begin' event and 'on incident end' event but they are customer specific.

Anonymous (login to see details)

Hi Eugene,

I want the output of the ${MESSAGE} parameter to appear in multi-line format (as per the script I run). But the output is being shown in a single line. I tried the ASCII format like you suggested. It is giving a multi-line output but since it is ASCII format, the email formatting is very plain and doesn't look nice. Is it possible to add the feature of multi-line output to HTML format? It would be really useful.

Anonymous (login to see details)

In order to accomplish what you described in your post, you need to perform the following steps:

You need to have ability to detect the "User error ID: XXXXX" error message in the application log.

Let's assume that you have a script which will return the "User error ID: XXXXX" message in the stderr stream every time when new error message appears in the application log.

Setup the Generic Execution plugin to execute this script and use the "Trigger Incident" parameter of the Generic Execution plugin to trigger incident which ${MESSAGE} parameter will contain the "User error ID: XXXXX" message.

When incident described in step #3 will be triggered the ${MESSAGE} variable will have content "User error ID: XXXXX".

Anonymous (login to see details)

Hi Maciek,

Now I see what you are referring to. Unfortunately, as things are right now, there is no out of the box exception message(s) passed to the incident rule when it is triggered. As a result, only thing that you could use is what I have described in my original reply on your post here.

Anonymous (login to see details)

Hi Maciek,

I'm checking with the Dynatrace product management team if there are plans to extend the plugin interface to allow getting detailed exceptions for the incident rules in question. I'll update this post as soon as I hear from them.

Anonymous (login to see details)

Anonymous (login to see details)

Hi,

I'm not able to getting the plugin to work.

I configured the mail settings and no filter. Afterwards I fired an incident, but no mail was sent.

Further I can't find any logs of the plugin. Where should they be located? I was looking in System Information -> Connected Systems -> Server -> Log Files. THere are log files of other plugins but not the Extended Mail Plugin.

Anonymous (login to see details)

Hi Gerald,

Please go to System Information -> your Dynatrace server -> Support Information -> Log Files and search for the 'com.dynatrace.diagnostics.plugins.extendedmailreport.action.0.0.log' file. Before doing it, please set log level of the plugin in question to FINER.

If you still have issues, please send me e-mail to eugene.turetsky@dynatrace.com and provide your availability for the webex. I am busy today but will be able to work with you tomorrow. I am in the EST time zone.

Anonymous (login to see details)

Hi Gerald,

Please use valid e-mail addresses including email group addresses in the From, To, CC, and BCC parameters that are supported in your organization. The "group[Incident Email Group]" is a placeholder and should be replaced by the valid e-mail address. E-mail addresses should be in the RFC822 format.

Also, please unset the 'ThresholdsFile' parameter of the plugin and follow instructions depicted in this post to configure your notification e-mail. Trigger an incident and forward me a notification e-mail from your test case.

Anonymous (login to see details)

Hi Eric,

Are you referencing your own XSD schema in the Agent Filters XML file? If yes, then remove it because plugin comes with the filters.xsd schema located in the 'res' sub-directory of the plugin's jar file. Plugin always uses this schema when parsing the Agent Filter XML file.

Anonymous (login to see details)

Hi Eric,

Could you please make sure that owner of the DT server process has read/write access to the "D:\dynaTrace\dynaTrace-6.2.0\Alerting\" directory? If you still have issues, please send me plugin's FINER log file and provide version of the plugin. You can send this info to eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Anonymous (login to see details)

Would it be possible to improve the plugin in a way that configuring filters for agentGroups, Monitors and Applications would work on internal ID's for these items (assuming there are such) instead of just plain strings?

In other words: I don't like the fact that one has to provide the names as arbitrary strings which have to be known beforehand and which are static in the sense that as as soon as any such config item is renamed in the system profile it will potentially break any existing filters which relied on the old name...

Not sure if this would be technically possible, but ideally in the Rule Action Editor there would be selectable filtering parameters (i.e. check boxes) for each existing config item instance. For example if my system profile contained 3 agent groups there would be 3 separate agentGroup filtering parameters and if selected the plugin would use their internal ID's to refer to the corresponding instances for the filtering, hence not relying on their "display" name.

Anonymous (login to see details)

Anonymous (login to see details)

Hi Eugene,

I would be a bit surprised if this affects the Incident Rule UI. Why do you think this is the case?

I'm not familiar with the plugin API but the only requirement I can see is that the plugin may internally refer to agent groups, monitors and applications by way of some unique/static ID's (and derive their "user friendly" names from them) instead of just arbitrary name strings which may change at any time. But again, this assumes that there are such internal IDs because after all the renaming of agent groups (as an example) works without breaking dashboard filters that use them suggesting there is a way to keep relationships intact across rename operations.

Furthermore in the Rule Action Editor (where the plugin parameters are set) the number of available filtering options would depend on the number of agent groups, monitors and applications currently defined for the system profile. Not sure if it's possible to have such a "dynamic" list of parameters which depends on what's currently configured in the system profile...

Apologies if the description of my idea was not clear - I guess it's not entirely trivial...

Anonymous (login to see details)

Hi Enrico,

Action plugins by itself are not coupled with system profiles. They become associated with system profiles when they become actions during Incident Rule(s) configuration. As I understand from your posts you'd like to make this configuration easier in a way that customer will see available resources (agents, agent groups, monitors, servers, collectors, etc.) for given system profile. This require UI enhancement. That is why I'm recommending you to open RFE.

Anonymous (login to see details)

My main intentions for the suggested improvements are to make the filter configuration easier, less error prone and more robust against name changes in the system profile.

However, I'm not quite sure how I would have to go about generalizing the requirements in order to suggest an RFE for the Incident Rule UI as a whole (since you pointed out that's what's going to be affected). Perhaps you can provide some hints?

Anonymous (login to see details)

Hi Andre,

Please check Section 2 Filtering on Page 9 of the plugin documentation here. There is a note there which says that this message describes a case when incident(s) were raised but they did not match any of the filtering conditions. Please check your filtering conditions to make sure that they are set correctly.

Anonymous (login to see details)

Hi See,

Yes, the restart of the Dynatrace server is required. Please open a ticket with our support team. This issue is not related to the plugin itself but rather to the Dynatrace engine when it upgrades plugin to a new version. Please provide ticket number for me. Email me at eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Hello Eugene,

I've found an old backup of this plugin (0.9.9.4) and managed to make it work with my Dynatrace installation. While the new version seemed to work (The logs are listing down all actions until teardown just fine), but ultimately the email wasn't sent out. Perhaps the new code for 0.10.x doesn't work anymore on Dynatrace 5.5.

Anonymous (login to see details)

Anonymous (login to see details)

Anonymous (login to see details)

Hello,

My apologies if this is a dumb question, I am a rookie at this plugin and had a quick question. I am creating an email body and have been asked to change the wording of the VIOLATION_MESSAGE a bit. I was going to use the VIOLATED_TRIGGER_VALUE, however, it is displaying a value of 4.754098415374756, where as the VIOLATION_MESSAGE would display it rounded to 4.75.

Is there anyway to round the VIOLATED_TRIGGER_VALUE, or is there another variable that I overlooked that already contains just the rounded value?

Anonymous (login to see details)

Anonymous (login to see details)

Thanks for the response Eugene, I'm not very strong in javascript, but I could give it a try. Not sure where I would add the javascript though. I was just curious, since the "VIOLATION_MESSAGE" contains the already rounded value of the "VIOLATED_TRIGGER_VALUE", how is it doing the rounding? Is it some already created javascript within the plugin?

Perhaps, I'm thinking of this incorrectly, Are these variables created in the Plugin, are is the Plugin using these variables that exist in DT? Sorry, just trying to figure it out. : )

Anonymous (login to see details)

Hi Tom,

You are correct, plugin provides standard out of the box ${VIOLATION_MESSAGE} which contains rounded ${VIOLATED_TRIGGER_VALUE}. However, you can fully customize body of the e-mail. Please see this link for an example of customization described at the top of this page.

Anonymous (login to see details)

That is terrific, Thanks for the details. I will for sure take this route. Of course, I keep bugging you. For some reason, when I use the html that is on this forum (Modified it a little bit - Moved "My Violations" above "My Details", changed some variables, and added the <html> and <body>). My resulting emails are just the html code. I am using Lotus Notes, maybe that has something to do with it. Below is what I am using and what the emails look like:

Anonymous (login to see details)

Anonymous (login to see details)

Hi Shirish,

There are no verification e-mails sent by the plugin. Just set plugin's parameters in your test environment, trigger an incident and if you did not receive notification e-mail, check plugin's log file for 'SEVERE' messages.

Anonymous (login to see details)

Anonymous (login to see details)

I am not JAVA programmer , also very little knowledge on the programming.

I am configured this plugin for the alerting the email for the MQ plugin.

I want to trigger the email to three different groups based on the MQ Q name.

is it possible to add filter based on the captured values e.g. this is the value I see in the FINER log on extended email plugin 145: key 'VIOLATED_MEASURE_SPLITTINGS_ALL' value 'ABCDDRN1.CHL2|10.16.21.200' now if I want to trigger the email to the ABC@mycomp.com when the captured value is "ABCDDRN1.CHL2" and when the captured value is "XYZDRN1.CHL2" send email to "XYZ@mycomp.com " . Is it possible to do?

Anonymous (login to see details)

Hi,

We are using Dynatrace 6.1.0.8324 and we are using Extended Email Action Plugin to send alerts.

We have created Regular Expression to capture the message in Splitting and we send that Message in Alerts. But Sometimes we have analyzed that Dynatrace is sending alerts with Message "-" but if we drill down to purepaths of that incident then we are able to find the return value. Also we checked that the applied regular expression is properly working for same incident.

Anonymous (login to see details)

Hi Hitesh,

Could you please cut and paste content of the following file into the Body Header field of the plugin and check the HTML Mail Format? Then set log level of the plugin to FINER, trigger the incident, and forward me notification e-mail along with the plugin's FINER log file. Please send this information to eugene.turetsky@dynatrace.com.

Anonymous (login to see details)

Anonymous (login to see details)

hi all,

I'm having some trouble getting the email to send at all. I've tried two different SMTP servers that also work with sending emails with the Mail Report Task/Action Plugin. For some reason it is not sending with this plugin however. After looking in the logs the only thing useful I could find was the below error, but no indication on why the email was not sent.

Anonymous (login to see details)

Hello,The plugin (latest version 0.10.5) would not send any HTML email notifications (checkbox "HTML Mail Format" ticked and example HTML email as per plugin description). There seems to be an image file missing as indicated in the AppMon server log file:

I have manually checkout out the plugin, added a file compuware_logo.png and recompiled the plugin. Next, I ran into the following error already addressed in another comment here

After an AppMon server restart, the plugin would send HTML emails. Can this be fixed in a future release? The file compuware_logo.png would need to be added in folder res.