Quick Start¶
Get CloudEvent Player up and running in 5 minutes.
Step 1: Start the Application¶
Choose your preferred method to run CloudEvent Player:
Pull the pre-built image from GitHub Container Registry:
# Pull the latest image
docker pull ghcr.io/bvandewe/events-player:latest
# Run the container
docker run -d \
--name event-player \
-p 8884:8080 \
ghcr.io/bvandewe/events-player:latest
# Verify it's running
curl http://localhost:8884/health
Using Docker Compose:
Create a docker-compose.yml
file:
services:
event-player:
image: ghcr.io/bvandewe/events-player:latest
ports:
- "8884:8080"
restart: unless-stopped
Then start it:
Expected output:
{
"status": "healthy",
"timestamp": "2025-10-16T00:00:00Z",
"active_tasks": 0,
"active_clients": 0,
"version": "0.1.17"
}
Step 2: Open the Web Interface¶
Open your browser to:
You should see the CloudEvent Player web interface with:
- An empty event stream
- A "Generate Events" button in the top-left
- A search bar
Step 3: Generate Your First Event¶
-
Click the "Generate Events" button (top-left corner)
-
The generator panel will open with default values:
-
Event Gateway:
http://localhost:8884/events/pub
- Event Source:
cloudevent-player
- Event Type:
com.cloudevent.player.generated.v1
- Event Subject:
test-event
- Event Data:
{"foo": "bar"}
- Iterations:
1
-
Delay:
1000
-
Click the "Generate" button at the bottom of the panel
-
Watch your event appear in the stream!
Step 4: Inspect the Event¶
Click on the event card to expand it and view:
{
"specversion": "1.0",
"id": "a1b2c3d4-5678-90ab-cdef-123456789abc",
"time": "2025-10-16T12:34:56.789012",
"datacontenttype": "application/json",
"type": "com.cloudevent.player.generated.v1",
"source": "cloudevent-player",
"subject": "test-event",
"data": {
"foo": "bar"
}
}
Step 5: Generate Multiple Events¶
Try generating multiple events:
- Open the generator again
- Change Iterations to
5
- Change Delay to
500
(milliseconds) - Click "Generate"
Watch as 5 events are generated with a half-second delay between each!
Step 6: Customize Your Event¶
Create a custom event:
- Open the generator
- Modify the Event Data field:
{
"message": "My first custom event",
"timestamp": "2025-10-16T00:00:00Z",
"count": 42,
"active": true,
"tags": ["demo", "quickstart"]
}
- Change the Event Type to:
com.myapp.custom.event
- Click "Generate"
Your custom event appears with the new data!
Step 7: Send Events from External Systems¶
Test the subscriber endpoint using curl:
curl -X POST http://localhost:8884/events/pub \
-H "Content-Type: application/cloudevents+json" \
-d '{
"specversion": "1.0",
"id": "external-test-123",
"time": "2025-10-16T00:00:00Z",
"type": "com.external.test",
"source": "curl-command",
"subject": "external-test",
"datacontenttype": "application/json",
"data": {
"message": "Event from external system",
"origin": "command-line"
}
}'
The event appears in your browser in real-time!
Common Use Cases¶
Testing a Microservice¶
Point the gateway to your service:
Generate events to test your service's event handling.
Load Testing¶
Generate high-volume event streams:
This generates 100 events with 100ms between each.
Debugging Event Structure¶
Use CloudEvent Player as a subscriber to inspect events from your system:
- Configure your system to send events to:
http://localhost:8884/events/pub
- Watch events appear in real-time
- Inspect the structure and data
- Verify CloudEvents compliance
Exploring the API¶
Swagger UI¶
Visit the interactive API documentation:
Try out API endpoints directly from your browser!
Health Check¶
Monitor application health:
List Active Tasks¶
See what event generation tasks are running:
Next Steps¶
You're ready to explore more features:
- Usage Guide - Detailed usage instructions
- API Reference - Complete API documentation
- Configuration - Customize your setup
- Deployment - Deploy to production
Troubleshooting¶
Port Already in Use¶
If port 8884 is already in use, change it in docker-compose.yml
:
Then access: http://localhost:9000
Container Won't Start¶
Check the logs:
Events Don't Appear¶
- Check the browser console for errors
- Verify the SSE connection is active
- Try refreshing the page
- Check that the gateway URL is correct
Cannot Connect to External Service¶
If testing with an external service:
- Verify the service is running
- Check network connectivity
- Ensure the service accepts CloudEvents
- Check firewall rules
Development Mode¶
For hot-reload during development:
# Use debug compose file
docker-compose -f docker-compose.debug.yml up -d
# Changes to code will auto-reload
# Access logs:
docker-compose -f docker-compose.debug.yml logs -f
Stopping the Application¶
Summary¶
You now know how to:
✅ Start CloudEvent Player with Docker
✅ Generate CloudEvents via the web UI
✅ Inspect event structure and data
✅ Send events from external systems
✅ Access API documentation
✅ Monitor application health
Ready to learn more? Check out the Usage Guide for advanced features!