| Compatibility : | 3.3.0 |
| Editions : |    |
| Platforms : |          |
This property is used to configure the body of alert emails.
Like several of the event emails properties, it can be defined:
-
Globally for all events: wrapper.event.default.email.body property, or
-
For a specific event: wrapper.event.<event_name>.email.body property.
The "<event_name>" component of the property name can be
either the keyword "default",
or one of the Event Types.
By setting the default property,
all Event Types which are not set explicitly will take on that value.
It is possible to reference any of the Wrapper's
default environment variables,
or event handler variables
from anyplace within the text.
The .email.body property is a bit special,
in that its value allows you to define a multiline message body.
The end of a line (line break) is indicated with the text "\n".
If you wish to place a single backslash "\" in the text, use a double backslash "\\" instead.
Any other character following a single backslash "\" is escaped and may change in the future.
The default value defines a simple, but useful message body:
| Example: |
Java Service Wrapper Event Notification\\n\\nHost: %WRAPPER_HOSTNAME%\\nApp Name: %WRAPPER_NAME%\\n %WRAPPER_DISPLAYNAME%\\n\\nEvent: %WRAPPER_EVENT_NAME%
|
When formatted in the message, this will result in a message body like the following:
| Example of Message View: |
Java Service Wrapper Event Notification
Host: myhost
App Name: myapp
MyApplication
Event: jvm_started
|
The following example will simply display the "host name", "application name", and "event name".
| Example: |
wrapper.event.default.email.body=Host: %WRAPPER_HOSTNAME%\\nApp Name: %WRAPPER_NAME%\\nEvent: %WRAPPER_EVENT_NAME%
|
Attach Log:
It is possible to attach or append recent log activity to an email using the
wrapper.event.<event_name>.email.attach_log
property.
Please see the overview of Event Mails.
|
