Skip to content

Argo Events Setup Guide

This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation.

Components

Component Purpose Guide
EventSource Connect to external systems (Pub/Sub, webhooks) EventSource Configuration
EventBus Message broker for event delivery EventBus Configuration
Sensor Filter events and trigger workflows Sensor Configuration

Quick Start

  1. Deploy EventBus - Start with JetStream for production
  2. Configure EventSource - Connect your Pub/Sub topic or GitHub webhooks
  3. Create Sensor - Define event filters and triggers

EventBus First

Deploy the EventBus before creating EventSources or Sensors. Without a running EventBus, events have nowhere to go.

Troubleshooting

Events Not Arriving

  1. Check EventSource logs: kubectl logs -n argo-events -l eventsource-name=<name>
  2. Verify Pub/Sub subscription exists in GCP console
  3. Confirm service account has pubsub.subscriber role

Events Arriving But Not Triggering

  1. Check Sensor logs: kubectl logs -n argo-events -l sensor-name=<name>
  2. Verify filter conditions match event payload
  3. Test with a simple sensor that logs all events

Events Lost During Restarts

  1. Enable persistence on EventBus
  2. Increase maxAge retention
  3. Monitor EventBus storage usage

Comments