File contents Argo Events Setup Guide
When to Use This Skill
This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation.
Implementation
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
Deploy EventBus - Start with JetStream for productionConfigure EventSource - Connect your Pub/Sub topic or GitHub webhooksCreate 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
Check EventSource logs: kubectl logs -n argo-events -l eventsource-name=<name>
Verify Pub/Sub subscription exists in GCP console
Confirm service account has pubsub.subscriber role
Events Arriving But Not Triggering
Check Sensor logs: kubectl logs -n argo-events -l sensor-name=<name>
Verify filter conditions match event payload
Test with a simple sensor that logs all events
Events Lost During Restarts
Enable persistence on EventBus
Increase maxAge retention
Monitor EventBus storage usage
Related
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
Deploy EventBus - Start with JetStream for productionConfigure EventSource - Connect your Pub/Sub topic or GitHub webhooksCreate 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
Check EventSource logs: kubectl logs -n argo-events -l eventsource-name=<name>
Verify Pub/Sub subscription exists in GCP console
Confirm service account has pubsub.subscriber role
Events Arriving But Not Triggering
Check Sensor logs: kubectl logs -n argo-events -l sensor-name=<name>
Verify filter conditions match event payload
Test with a simple sensor that logs all events
Events Lost During Restarts
Enable persistence on EventBus
Increase maxAge retention
Monitor EventBus storage usage
Related
Troubleshooting
See troubleshooting.md for common issues and solutions.
Related Patterns
Argo Workflows Patterns
ConfigMap as Cache Pattern
Event-Driven Deployments
References
Converted and distributed by TomeVault — claim your Tome and manage your conversions.
1 --- 2 name: adaptive-enforcement-lab-claude-skills-argo-events-setup-gui 3 description: Argo Events Setup Guide 4 --- 5 6 # Argo Events Setup Guide 7 8 ## When to Use This Skill 9 10 This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation. 11 12 --- 13 14 15 ## Implementation 16 17 This guide covers EventSource, EventBus, and Sensor configuration for event-driven automation. 18 19 --- 20 21 ## Components 22 23 | Component | Purpose | Guide | 24 | ----------- | --------- | ------- | 25 | **EventSource** | Connect to external systems (Pub/Sub, webhooks) | [EventSource Configuration](event-sources.md) | 26 | **EventBus** | Message broker for event delivery | [EventBus Configuration](event-bus.md) | 27 | **Sensor** | Filter events and trigger workflows | [Sensor Configuration](sensors.md) | 28 29 --- 30 31 ## Quick Start 32 33 1. **Deploy EventBus** - Start with [JetStream for production](event-bus.md#jetstream_eventbus_production) 34 2. **Configure EventSource** - Connect your [Pub/Sub topic](event-sources.md#pubsub_eventsource) or [GitHub webhooks](event-sources.md#github_webhook_eventsource) 35 3. **Create Sensor** - Define [event filters and triggers](sensors.md#basic_sensor) 36 37 --- 38 39 > **EventBus First** 40 > 41 > Deploy the EventBus before creating EventSources or Sensors. Without a running EventBus, events have nowhere to go. 42 > 43 44 --- 45 46 ## Troubleshooting 47 48 ### Events Not Arriving 49 50 1. Check EventSource logs: `kubectl logs -n argo-events -l eventsource-name=<name>` 51 2. Verify Pub/Sub subscription exists in GCP console 52 3. Confirm service account has `pubsub.subscriber` role 53 54 ### Events Arriving But Not Triggering 55 56 1. Check Sensor logs: `kubectl logs -n argo-events -l sensor-name=<name>` 57 2. Verify filter conditions match event payload 58 3. Test with a simple sensor that logs all events 59 60 ### Events Lost During Restarts 61 62 1. Enable [persistence on EventBus](event-bus.md#nats_with_persistence) 63 2. Increase `maxAge` retention 64 3. Monitor EventBus storage usage 65 66 --- 67 68 ## Related 69 70 - [Argo Workflows Patterns](../../argo-workflows/index.md) - WorkflowTemplate design and error handling 71 - [ConfigMap as Cache Pattern](../../../patterns/efficiency/idempotency/caches.md) - Volume mounts for zero-API reads 72 - [Event-Driven Deployments](../../../blog/posts/2025-12-14-event-driven-deployments-argo.md) - The journey to zero-latency automation 73 74 ### Components 75 76 | Component | Purpose | Guide | 77 | ----------- | --------- | ------- | 78 | **EventSource** | Connect to external systems (Pub/Sub, webhooks) | [EventSource Configuration](event-sources.md) | 79 | **EventBus** | Message broker for event delivery | [EventBus Configuration](event-bus.md) | 80 | **Sensor** | Filter events and trigger workflows | [Sensor Configuration](sensors.md) | 81 82 --- 83 84 ### Quick Start 85 86 1. **Deploy EventBus** - Start with [JetStream for production](event-bus.md#jetstream_eventbus_production) 87 2. **Configure EventSource** - Connect your [Pub/Sub topic](event-sources.md#pubsub_eventsource) or [GitHub webhooks](event-sources.md#github_webhook_eventsource) 88 3. **Create Sensor** - Define [event filters and triggers](sensors.md#basic_sensor) 89 90 --- 91 92 > **EventBus First** 93 > 94 > Deploy the EventBus before creating EventSources or Sensors. Without a running EventBus, events have nowhere to go. 95 > 96 97 --- 98 99 ### Troubleshooting 100 101 ### Events Not Arriving 102 103 1. Check EventSource logs: `kubectl logs -n argo-events -l eventsource-name=<name>` 104 2. Verify Pub/Sub subscription exists in GCP console 105 3. Confirm service account has `pubsub.subscriber` role 106 107 ### Events Arriving But Not Triggering 108 109 1. Check Sensor logs: `kubectl logs -n argo-events -l sensor-name=<name>` 110 2. Verify filter conditions match event payload 111 3. Test with a simple sensor that logs all events 112 113 ### Events Lost During Restarts 114 115 1. Enable [persistence on EventBus](event-bus.md#nats_with_persistence) 116 2. Increase `maxAge` retention 117 3. Monitor EventBus storage usage 118 119 --- 120 121 ### Related 122 123 - [Argo Workflows Patterns](../../argo-workflows/index.md) - WorkflowTemplate design and error handling 124 - [ConfigMap as Cache Pattern](../../../patterns/efficiency/idempotency/caches.md) - Volume mounts for zero-API reads 125 - [Event-Driven Deployments](../../../blog/posts/2025-12-14-event-driven-deployments-argo.md) - The journey to zero-latency automation 126 127 128 ## Troubleshooting 129 130 See [troubleshooting.md](troubleshooting.md) for common issues and solutions. 131 132 133 ## Related Patterns 134 135 - Argo Workflows Patterns 136 - ConfigMap as Cache Pattern 137 - Event-Driven Deployments 138 139 ## References 140 141 - [Source Documentation](https://adaptive-enforcement-lab.com/patterns/argo-events/) 142 - [AEL Patterns](https://adaptive-enforcement-lab.com/patterns/) 143 144 --- 145 > Converted and distributed by [TomeVault](https://tomevault.io/claim/adaptive-enforcement-lab) — claim your Tome and manage your conversions. 146 <!-- tomevault:4.0:skill_md:2026-04-14 -->
commit ab3ec9dd41
Frequently asked questions How do I install the Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide skill? Run npx skillmds@latest add tomevault-io/adaptive-enforcement-lab-claude-skills-argo-events-setup-gui in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide skill do? Argo Events Setup Guide It is listed under Coding & Dev Tools on SkillMD.
Is Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Adaptive Enforcement Lab Claude Skills Argo Events Setup Guide? tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io