Interface Monitoring - Pidgeon Health

One command to start watching. Every new message file picked up from a watched source is parsed and validated against your vendor profile, with metrics tracked per interface.

Creating interfaces

The CLI pidgeon loft watch runs an ad-hoc watch and validates .hl7 files as they land. To create a persistent interface that survives restarts and appears in the desktop app’s Sources panel, POST to the local Bridge. This is the canonical create example; the Loft Interfaces API reference documents every field.

pidgeon loft watch --path /var/mirth/outbound/er --profile epic_er

curl -X POST http://localhost:5100/api/loft/interfaces \
  -H "Content-Type: application/json" \
  -d '{
    "name": "ER Interface",
    "directoryPath": "/var/mirth/outbound/er",
    "profileName": "epic_er",
    "filePattern": "*.hl7"
  }'

Interface metrics

Each interface tracks:

Metric	What it measures
Total messages processed	Messages parsed from the source
Total successes	Messages that passed validation
Total errors	Messages that failed validation
Error rate	Failed messages as a fraction of the total
Hourly breakdown	Per-hour processed, errors, and successes

curl "http://localhost:5100/api/loft/interfaces/{id}/metrics?sinceHours=24"

The response also carries lastMessageAt, startedAt, and uptimeSeconds. See the Loft Interfaces API reference for the full shape.

Managing interfaces

# List all interfaces
curl http://localhost:5100/api/loft/interfaces

# Update an interface
curl -X PUT http://localhost:5100/api/loft/interfaces/{id} \
  -H "Content-Type: application/json" \
  -d '{"enabled": false}'

# Delete an interface
curl -X DELETE http://localhost:5100/api/loft/interfaces/{id}

Status overview

# CLI
pidgeon loft status

# API
curl http://localhost:5100/api/loft/status