Automation and Integrations
This section is for teams that already have the basics in place and now want to automate more of the work, tighten governance, or connect StatiBeat to the rest of their tooling.
If you are still setting up your first page, start with Getting Started and Admin Quickstart first.
Come here when you want to
- automate incidents, maintenance, or page management
- manage configuration as code
- connect AI clients through Hosted MCP
- review the complete Hosted MCP and page MCP feature surface
- add Slack-driven or AI-assisted operator workflows
- roll out proactive Beats monitoring
- tighten access, auditing, and configuration readiness
A good order for the deeper setup
- Get the manual workflow working first.
- Add one advanced surface at a time.
- Use narrow page-scoped tokens and auditable workflows.
- Add governance only after the team agrees which settings are code-owned.
Choose the area that matches what you are doing
API and internal tools
Start with API Quickstart when you want simple scripts, CI jobs, or internal tools. Continue with:
Terraform and configuration ownership
Start with Terraform Workspace and Export if you already configured a page in the UI and want a bridge into config as code.
Start with Terraform Provider Overview if you want provider-first ownership from day one.
Slack and synthetic monitoring
Use these guides when you want operator workflows to stay close to incident response:
AI clients and Hosted MCP
Use Hosted MCP when you want the customer-facing integration path with OAuth and hosted connectivity. Use MCP Reference when you need to compare the hosted connector with the page-scoped stdio MCP server, including current resources, prompts, tools, scopes, and write limits.
Helpful companion docs
- Auditing helps you confirm who changed what after automation and integrations are live.
- SSO and Access and Organization Admin matter when the automation boundary crosses page and tenant ownership.