Skip to main content

​
Integration Guides

Step-by-step tutorials for adding runtime monitoring to your deployments.

​
Vercel

Add Gluon runtime monitoring to Vercel serverless functions and Next.js apps.

​
1. Update Your Start Command

In your package.json, wrap your start script: 
{
  "scripts": {
    "start": "npx @dotsetlabs/gluon run -- node dist/index.js"
  }
}

​
2. View Telemetry

After deployment, view local telemetry with: 
gln status

​
GitHub Actions

Monitor your test runs and builds for security issues in CI.

​
1. Update Your Workflow

Modify your .github/workflows/*.yml: 
- name: Run tests with monitoring
  run: npx @dotsetlabs/gluon run -- npm test

- name: Check for security events
  run: npx @dotsetlabs/gluon status --severity warning

​
2. Fail on Critical Events

Add a check to fail the build if secrets are exposed: 
- name: Check for secret exposure
  run: |
    if npx @dotsetlabs/gluon status --type secret_exposure --severity critical | grep -q "secret_exposure"; then
      echo "Critical: Secrets detected in output!"
      exit 1
    fi

​
Docker

Add runtime monitoring to Docker containers for production visibility.

​
1. Update Your Dockerfile

Install Gluon and wrap your entrypoint: 
FROM node:20-alpine
# ...
RUN npm install -g @dotsetlabs/gluon
RUN gln init
CMD ["gln", "run", "--", "node", "dist/index.js"]

​
2. Docker Compose

Mount the telemetry directory: 
services:
  app:
    command: gln run -- node dist/index.js
    volumes:
      - ./telemetry:/app/.dotset/gluon/telemetry

​
Axion Integration

Combine Axion secrets with Gluon runtime monitoring for end-to-end protection.

​
1. Run with Combined Protection

Nest Gluon inside Axion: 
axn run -- gln run -- npm start
Axion injects encrypted secrets → Gluon monitors for accidental exposure in stdout/stderr.