Destination fields
Here are the fields used in specifying destinations.
All destinations
Field | Required? | Description |
---|---|---|
Destination name | Yes | A unique, short identifier for the destination. The name of a destination cannot be changed after the ADD DESTINATION dialog is saved. |
Destination description | No | Text to describe the destination. |
Destination type | Yes | The type to create. |
Tags | No | A list of arbitrary terms to associate with the destination. |
The contents of the Custom body template field replaces the contents
of a rule's Message field. However, templates
are supported, so you can include a rule's Message field with the {{{rule.message}}}
template.
Field | Required? | Description |
---|---|---|
Send email to | Yes | One email address. You can use templates in this field. |
Custom subject template | No | Text for the subject line of the email message. If no content is specified in this field, Zenoss uses a default that is appropriate for the matching trigger. You can use templates in this field. |
Custom body template | No | Text for the body of the email message. If no content is specified in this field, Zenoss uses a default that is appropriate for the matching trigger. You can use templates in this field. |
Zenoss event service
Field | Required? | Description |
---|---|---|
Event name | Yes | A name for the event. The field is populated with a template, which you can change. |
Event type | Yes | A context-free label to classify the event. The field is populated with a suggested value, which you can change. |
Event summary | Yes | A brief description of the event. The field is populated with a template, which you can change. The maximum size is 100 characters (including template delimiter characters). |
Severity | Yes | The event severity, one of the following:
|
Event body | No | A longer description of the event. You can include templates. |
Microsoft Teams
Destination configurations
Field | Required? | Description |
---|---|---|
Webhook URL | Yes | The URL of a Microsoft Teams incoming webhook for the target channel. |
Message | Yes | The text to send to the channel associated with the specified webhook URL. The contents of this field replace the contents of a rule's message field. However,
templates are supported, so you
can include a rule's message with the |
Custom facts
You can specify up to 20 name-value pairs (facts) to replace the default connector card that the action service sends to a Microsoft Teams chat.
In the Name field, enter any string. In the Value field, enter any message template or string (or both). Use the buttons to add or remove facts.
PagerDuty
Field | Required? | Description |
---|---|---|
Routing key | Yes | A PagerDuty Integration Key. The key is used to send an Alert Event to PagerDuty. |
ServiceNow IT Operations Management
Basic authorization
Field | Required? | Description |
---|---|---|
Authorization type | Yes | The authorization type to use (Basic). |
Username | Yes | The name of a user account in your ServiceNow IT Operations Management instance. |
Password | Yes | The password of a user account in your ServiceNow IT Operations Management instance. |
Base URL | Yes | The URL of your ServiceNow IT Operations Management instance. |
Short description | No | Text to include in all notifications sent to this destination. The contents of this field replace the contents of a rule's message field. However,
templates are supported, so you
can include a rule's message by using the |
OAuth authorization
Field | Required? | Description |
---|---|---|
Authorization type | Yes | The authorization type to use (OAuth). |
Username | No | A ServiceNow account to authorize a refresh token request. |
Password | No | The password of a ServiceNow account to authorize a refresh token request. |
Client id | Yes | The ServiceNow ID for your integration with Zenoss Cloud. |
Client secret | Yes | The ServiceNow secret for your integration with Zenoss Cloud. |
Instance url | Yes | The URL of your ServiceNow IT Operations Management instance. When you enter the URL, Zenoss Cloud populates the Token url and Auth url fields automatically. |
Token url | Yes | The URL for updating a ServiceNow refresh token. |
Auth url | Yes | The URL for obtaining a ServiceNow refresh token. |
Token | Yes | A ServiceNow refresh token. To get a token, click the GET TOKEN control at the right of the field. |
Slack
Field | Required? | Description |
---|---|---|
Token | Yes | A Slack bot token for the Zenoss Slack app. For more information, see Get a Slack bot token. |
Channel name | Yes | The name of a public channel in your Slack workspace. Channel names that start with the number sign character are not accepted. |
Notification color | No | The color to use in messages sent to the channel. The color is applied to a vertical bar accompanying the message block. |
Webhook
Field | Required? | Description |
---|---|---|
URL | Yes | The URL of a webhook receiver. Zenoss Cloud uses POST to send a JSON message to the receiver. |