Skip to main content
This page provides comprehensive examples of how to use the Checkly Pulumi provider to create various types of monitoring checks and configurations.

Basic API Checks

Simple GET Request

POST Request with JSON Body

Browser Checks

Basic Page Load Check

Login Flow Check

Check Groups

Alert Channels

Email Alert Channel

Slack Alert Channel

Advanced Configurations

Environment-Specific Configurations

Best Practices

Naming Conventions

Consistent Naming
  • Use descriptive names for resources
  • Include environment prefixes
  • Follow team naming conventions
  • Use consistent tagging strategies

Resource Organization

Logical Grouping
  • Group related checks together
  • Use check groups for organization
  • Separate environments with stacks
  • Maintain clear resource hierarchy

Security

Secure Configuration
  • Use environment variables for secrets
  • Never commit API keys to version control
  • Use Pulumi’s secret management
  • Implement least-privilege access

Monitoring Strategy

Effective Monitoring
  • Define clear success criteria
  • Use appropriate check frequencies
  • Implement proper alerting
  • Monitor from multiple locations
When creating multiple similar checks, consider using loops or functions to reduce code duplication and maintain consistency.
Always test your Pulumi configurations in a development environment before deploying to production. Use pulumi preview to review changes before applying them.