Each event received by Webhook listeners in FlexDeploy will be saved as an Event Message. This provides a way to track all the events that occur and debug as needed. Messages can be viewd by navigationg to Administration → Integrations → Events and clicking the view messages button.
Viewing Messages
The table on the left side of the screen shows all events received within the last week. Messages are purged automatically after 7 days.
Field | Description |
|---|---|
Message Id | The id given to message |
Status | The status of the message. Can be SUCCESS, PENDING, or FAILED |
Event Type | The event type corresponding to the event. |
Message | A message containing more detail on the execution. This message can be set in a function script by using the LOG.setMessage function. If any errors occur during execution, the message will be overwritten |
Created By | User who created the event |
Created On | Date and time of event message creation |
Viewing Message Details
Click on any event message row in the table to view more details about an individual message. THis will show more detail about the execution, including any FlexDeploy functions which were executed from this trigger and their statuses, as well as more context about the incoming event.
Click the view payload button to view the entire payload received by the event listener. More information on the execution can be viewed by clicking the view logs button. This will show any log messages printed in the function scripts using the LOG methods. You can also submit an event message to be executed again with the Resubmit button. This is only meant to be used for debuggin purposes. There is a global permission defined on groups to control who is allowed to resubmit event messages.
Log Messages
Logs are printed by using the LOG methods in the function scripts. By default, the logging level will be based on the global FlexDeploy logging level. This can be modified specifically for event logs by setting the logging level forflexagon.fd.services.groovy.functions.LogFunctions in Admin → Admin Operations.
Some internal logs are printed automatically during execution. These logs will be at FINEST level.
