n8n Incident Reporting and Database Logging Workflow

This n8n workflow demonstrates a robust system for managing incident reporting by integrating an AMQP message queue with PagerDuty for alerting and CrateDB for persistent logging. It provides a flexible framework for processing incident-related messages, creating alerts, and storing incident data.

What it does

This workflow automates the following steps:

1. Listens for Incident Messages: It starts by listening for incoming messages on an AMQP queue, which are expected to contain incident details.
2. Processes Incoming Data: A Function node processes the raw AMQP message, extracting relevant incident information and transforming it into a structured format suitable for subsequent actions.
3. Determines Incident Type: An If node evaluates the processed incident data to determine if it's a "critical" incident.
4. Handles Critical Incidents:
   • If the incident is deemed critical, it creates an incident in PagerDuty, ensuring that on-call teams are immediately alerted.
   • It then logs the critical incident details into a CrateDB database for historical record-keeping and analysis.
5. Handles Non-Critical Incidents:
   • If the incident is not critical, it proceeds to log the incident details directly into a CrateDB database without generating a PagerDuty alert.
6. Prepares Data for CrateDB: A Set node ensures the data is in the correct format before being inserted into CrateDB, regardless of whether it was a critical or non-critical incident.

Prerequisites/Requirements

To use this workflow, you will need:

• n8n Instance: A running n8n instance.
• AMQP Broker: Access to an AMQP message broker (e.g., RabbitMQ) with a configured queue for incident messages.
• PagerDuty Account: A PagerDuty account with an Integration Key for creating incidents.
• CrateDB Instance: Access to a CrateDB database instance where incident data will be stored.
• n8n Credentials: Configured n8n credentials for AMQP, PagerDuty, and CrateDB.

Setup/Usage

1. Import the Workflow:
   • Download the provided JSON file.
   • In your n8n instance, go to "Workflows" and click "New".
   • Click the three dots in the top right corner and select "Import from JSON".
   • Paste the workflow JSON or upload the file.
2. Configure Credentials:
   • Locate the "AMQP Trigger" node and configure your AMQP credentials (e.g., hostname, port, username, password, queue name).
   • Locate the "PagerDuty" node and configure your PagerDuty credentials (API Key).
   • Locate the "CrateDB" node and configure your CrateDB credentials (e.g., host, port, username, password).
3. Customize Nodes (Optional):
   • Function Node (ID: 14): Review and adjust the JavaScript code to parse your specific AMQP message format and extract the necessary incident data.
   • If Node (ID: 20): Modify the conditions to define what constitutes a "critical" incident based on your business logic.
   • PagerDuty Node (ID: 310): Customize the incident details (e.g., summary, severity, routing key) as needed.
   • Set Node (ID: 38): Adjust the fields being set to match the schema of your CrateDB table.
   • CrateDB Node (ID: 347): Configure the table name and columns for inserting incident data.
4. Activate the Workflow: Once configured, activate the workflow to start processing incident messages.