Debug dashboard for activitylog service and NATS/JetStream event processing.
| UID | activitylog-debug |
| Datasource | Loki |
| Refresh | auto |
- Activity feed not showing events
- Debugging activitylog service issues
- Investigating NATS/JetStream problems
- Tracking upstream issues (e.g., opencloud#2089)
Note: This is a debug dashboard for development and issue tracking, not daily operations.
Start from: Logs for general log analysis, filter by component=activitylog
{container="opencloud-opencloud-1"} |= `"service":"activitylog"`
{container="opencloud-opencloud-1"} |= `"service":"nats"`
Note: Container name
opencloud-opencloud-1is deployment-specific. Adjust if your Docker Compose project has a different name.
| Label | Description |
|---|---|
container |
Docker container name |
| Field | Description |
|---|---|
service |
Service name (activitylog, nats) |
level |
Log level (error, warn, info) |
message |
Log message |
| Panel | Shows | Thresholds |
|---|---|---|
| NATS Errors (24h) | Error count from NATS service | green=0, red≥1 |
| NATS Warnings (24h) | Warning count from NATS | green=0, yellow≥1, orange≥10 |
| NATS Config Warnings (24h) | Configuration-related warnings | green=0, yellow≥1 |
| Filestore Warnings (24h) | JetStream filestore warnings | green=0, yellow≥1 |
NATS Service Logs: Error and warning logs from NATS service.
| Panel | Shows | Thresholds |
|---|---|---|
| Activitylog Errors (24h) | Total errors | green=0, yellow≥1, red≥10 |
| Event Processing Errors | "could not process event" errors | green=0, red≥1 |
| Store Errors | Activity store errors | green=0, red≥1 |
| Unknown Events | "event not registered" warnings | green=0, yellow≥1 |
Error Rate Over Time: Errors and warnings over time.
All Activitylog Errors: Full error log stream.
could not process event
Event received but failed during processing. Check:
- Event format
- Required fields present
- Storage accessible
error.*store
error.*activities
Failed to read/write activity data. Check:
- Disk space
- File permissions
- Storage path configuration
event not registered
Received event type not handled by activitylog. Usually:
- New event type not yet supported
- Version mismatch
nats configuration
Filestore
JetStream storage or configuration problems. Check:
- NATS data directory
- Disk space for JetStream
- NATS configuration
- Check Activitylog Errors (24h) for any errors
- Check Event Processing Errors specifically
- Review All Activitylog Errors log panel
- Check NATS Errors for event delivery issues
- → For broader context: Logs with component=activitylog
- Check all NATS panels in top row
- Review NATS Service Logs for details
- Look for Filestore warnings (disk issues)
- Check NATS configuration warnings
- Monitor error patterns over time
- Capture specific error messages
- Correlate with OpenCloud versions
- Document for upstream issue reports
- Events may not be reaching activitylog
- Check NATS service is running
- Verify event publishing from other services
- → Check Overview for Event Queues
- JetStream storage issues
- Check disk space in NATS data directory
- May need to clean old streams
- New event types from updated OpenCloud
- Usually informational, not critical
- May indicate version mismatch
- Check specific error messages in logs
- May indicate storage issues
- Review activitylog service configuration
If queries show no data, check your container name:
docker ps --format "{{.Names}}" | grep opencloudUpdate the queries if your container is named differently.
| Dashboard | Datasource | Use for |
|---|---|---|
| Logs | Loki | General log analysis (component=activitylog) |
| Overview | Prometheus | Event Queues, system health |
- opencloud#2089 - Activities app issues