Quickstart for DevOps Engineers

This guide helps DevOps engineers use Sire to automate scheduled tasks, monitoring pipelines, and incident response workflows.

Step 1: Set Up Your Account

1. Sign up at sire.run with your work email.
2. Create an API key under Settings > API Keys for programmatic access.
3. Store credentials for your monitoring and infrastructure tools under Settings > Credentials (e.g., Datadog API key, PagerDuty token, cloud provider credentials).

Step 2: Create a Scheduled Workflow

DevOps workflows often run on a recurring schedule. Sire supports cron-based scheduling.

Example: Daily Infrastructure Health Check

1. Open the Prompt Panel in Mission Control.
2. Enter: "Every day at 6am UTC, check the health of our production API endpoints, query the database for slow queries in the last 24 hours, and send a summary to the #ops Slack channel."
3. Click Generate to create the workflow DAG.
4. Review the steps and adjust any endpoint URLs or thresholds.
5. Click Deploy and set the cron schedule: 0 6 * * *.

Managing Schedules via API

# Set a schedule on an existing workflow
curl -X PUT https://sire.run/api/v1/workflows/{workflow_id}/schedule \
  -H "Authorization: Bearer $SIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"cron": "0 6 * * *", "timezone": "UTC"}'

# Remove a schedule
curl -X DELETE https://sire.run/api/v1/workflows/{workflow_id}/schedule \
  -H "Authorization: Bearer $SIRE_API_KEY"

Step 3: Build a Monitoring Pipeline

Combine multiple data sources into a single monitoring workflow.

Example: Multi-Source Infrastructure Monitor

Create a workflow that:

1. Queries your monitoring API (Datadog, Grafana, Prometheus) for key metrics.
2. Checks your cloud provider for resource utilization and cost anomalies.
3. Queries your database for error rates and slow query counts.
4. Compares all metrics against defined thresholds.
5. Sends an alert if any threshold is breached.

Use Sire's parallel execution to query all sources simultaneously, reducing total check time.

Step 4: Set Up Alert Workflows

Trigger Sire workflows from external alerts using webhooks.

Webhook Trigger

Configure your monitoring tool to send a webhook to Sire when an alert fires:

POST https://sire.run/api/v1/workflows/{workflow_id}/trigger

Example: Incident Response Automation

When PagerDuty fires an alert:

1. Sire receives the webhook payload with incident details.
2. The workflow gathers context: recent deployments, error logs, affected services.
3. Creates an incident ticket in your project tracker.
4. Notifies the on-call team with a structured briefing.
5. Opens a war room channel with pre-loaded context.

This cuts incident response time by assembling context before engineers even look at the alert.

Step 5: Post-Deployment Verification

Automate verification after every deployment.

CI/CD Integration

# GitHub Actions example
deploy:
  steps:
    - name: Deploy to production
      run: kubectl apply -f deploy/

    - name: Trigger post-deploy verification
      run: |
        curl -X POST https://sire.run/api/v1/workflows/$VERIFY_WORKFLOW_ID/execute \
          -H "Authorization: Bearer ${{ secrets.SIRE_API_KEY }}" \
          -d '{"inputs": {"environment": "production", "version": "${{ github.sha }}"}}'

Your verification workflow can run smoke tests, check health endpoints, verify database migrations, and roll back if any check fails.

Step 6: Monitor Your Workflows

Use Mission Control to monitor the health of your automation itself.

• Execution History: See all past runs with status, duration, and error details.
• Failure Alerts: Configure notifications for workflow failures so you know when your automations need attention.
• Usage Dashboard: Track execution counts and resource consumption.
• Audit Trail: Every execution is logged with timestamps, inputs, outputs, and the user or trigger that initiated it.

Common DevOps Patterns

Next Steps

• Read about Human-in-the-Loop for workflows that need manual approval before destructive actions.
• Explore the Use Case Gallery for more automation patterns.
• See the API Reference for the complete endpoint catalog.