Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

When you configure a webhook service but do not provide a custom template, BloxOne uses the following default template to generate payload for your notifications. For information about how to configure webhook services, see Configuring Webhook Service.

{

   "id":"{{ .id}}",

   "type":"{{ .type}}",

   "subtype":"{{ .subtype}}",

   "account_id":"{{ .account_id}}",

   "occurred_time": "{{ .occurred_time}}",

   "generated_time": "{{ .generated_time}}",

   "severity": "{{ .severity}}",

   "short_subject": "{{ .short_subject}}",

   "message": "{{ .message}}",

   "url": "{{ .url}}",

   "preferences_url": "https://{{ .csphost}}/{{.userPreferencesPath}}"

}

The following table describes the supported fields in the default webhook template:

Supported FieldsDescription
idAn auto-generated ID for the event
typeEvent type such as "ACCOUNT"
subtypeEvent sub type such as "license_expiration" for event type "ACCOUNT"
account_idThe account ID
severitySeverity of the generated event:  Low, Medium, and High
metadataMetadata associated with the event
occurred_timeThe timestamp when the event occurred
generated_timeThe timestamp when the notification was generated
short_subjectA brief description of the event. Example: "Host Memory Usage Limit Exceeded"
messageThe message of the event. Example: "Internal error occurred. For more details see log for request 1a94821f-0f7a-48ab-b1cf-b137d628afd4"
urlThe URL to which you want to send webhook notifications
preferences_urlA link to the "View all notifications” page on the Cloud Services Portal 

actionable_redirect_action

The actionable redirect URL. This must appear in the webhook context in order for the template to pick up.
actionable_redirect_labelThis is optional. This is the text for the actionable redirect URL link. If this is missing, the system uses the actionable redirect URL.

Other Supported Fields

Apart from the fields in the default webhook template, the following fields are supported:

Supported FieldsDescription
range_id

ID for the range.

For e.g /ipam/range/fa42b963-6d2d-11ee-89f6-aa8883d81554

range_name

Name of the range

range_start

Start address for the range

range_end

End address for the range

range_space_nameName of the IP space.
range_high_threshold

High threshold for DHCP utilization (%)

range_low_threshold

Low threshold for DHCP utilization (%)

range_utilization

Current DHCP utilization %

  • No labels