Event Logs allow you to search, view, and trace logs for all events that occur in your Paragon project. Event Logs contain relevant information that helps you build a complete picture of data moving from your app and your user’s integrations into your Paragon project. We are launching Event Logs starting with a focus on workflow trigger events such as (custom) webhooks, scheduler triggers, request triggers,and app events. For example, if you’d like to see how an incoming webhook event from an integration was processed, you can filter by integration and trace the resulting workflow execution.
Event Logs is currently in a public beta. We are currently adding support for more events.Event Log schemas and the log retention policy are subject to change.
You can find you project’s Event Logs by navigating to the global Task History tab in the left sidebar and selecting the Logs tab.
Event Logs contain the following top-level properties:
  • Timestamp: The date and time the event occurred.
  • Type: The Paragon feature emitting the event.
  • Message: The message associated with the event.

​
Log Details

By expanding a log, you can view the full event object including the payload, associated Trace IDs, User IDs, and more.
PropertyDescription
projectIdUnique identifier for the Paragon project under which the trigger or workflow runs.
personaIdID representing the persona (or agent) responsible for executing the trigger.
typeIndicating the type of trigger or event.
endUserIdIdentifier for the end user associated with the event or workflow.
connectCredentialIdID of the credential used to connect to an integration.
connectCredentialConfigIdID for the specific configuration of the credential in use.
workflowIdIdentifier for the workflow that is being triggered or executed.
traceId 🔸Identifier used to group logs from the same trigger execution for traceability.
integrationId 🔸ID of the integration involved, especially for integration or webhook triggers.
webhookId 🔸Identifier for the webhook associated with a trigger (when applicable).
eventId 🔸ID for the specific App Event received.
eventName 🔸Name of the App Event being triggered.
error 🔸Error object included in failure logs to describe the problem.
status 🔸Indicates the result of the operation, such as EVENT_STATUS.SUCCEEDED or FAILED.
🔸 Indicates an optional property

​
Filtering and Searching

You can filter the Event Logs view using these filter dropdowns:
  • Level: The severity of the event.
  • Type: The Paragon feature emitting the event.
  • User ID: The Paragon user ID who triggered the event.
  • Integration ID: The integration associated with the triggered event.
  • Trace ID: The trace ID of the event.
  • Timestamp: The date and time the event occurred.
Additionally, you can search for specific payload properties by entering a search query in the search bar. For example, if you’d like to search for all logs that contain a particular record ID, you can enter the record ID in the search bar and the table will filter Log Events where the payload contains that record ID.

​
Supported Events

Here are the following event types that can appear in your Event Logs:

​
Unsupported Events

The following events are not currently supported in Event Logs:
  • Task executions and their individual outbound API requests
  • Workflow execution events
  • Requests made to or received by Resources.
  • Connected User events
Have a request for other events you’d like to send from your Paragon project? Reach out to your account manager or let us know.

​
Connecting with Event Destinations

An integration with Event Destinations is coming soon.
Send Event Logs to your logging, analytics, and APM services by configuring Event Destinations. All Event Logs can be forwarded to your observability tools for increased retention and analysis via Event Destinations.