# Firetiger

> Firetiger is a REST API platform (JSON-over-POST, AIP conventions, Basic auth) for configuring autonomous agents that monitor software systems using telemetry data and connected tools.

- [Full documentation](https://docs.firetiger.com/llms-full.txt): all pages concatenated into a single file


## Concepts

- [Agents](https://docs.firetiger.com/concepts/agents.txt): How agents work: creation, triggers (webhook/scheduled/post-deploy), sessions, memory, and tools
- [Integrations](https://docs.firetiger.com/concepts/integrations.txt): How connections, ingest sources, and credentials work to give agents access to external systems
- [Telemetry](https://docs.firetiger.com/concepts/telemetry.txt): OpenTelemetry data ingestion, service-based organization, structured logs, and schema inference
- [Deployments](https://docs.firetiger.com/concepts/deployments.txt): Deployment tracking via GitHub webhooks or API, git ancestry matching, and post-deploy monitoring
- [Issues](https://docs.firetiger.com/concepts/issues.txt): Issue lifecycle: auto-creation by agents, triage, expert investigation, and notification routing
- [Knowledge](https://docs.firetiger.com/concepts/knowledge.txt): Knowledge resources: services, flows, customers, notes, known issues, and Firetiger.md

## Guides

- [OpenTelemetry Integration](https://docs.firetiger.com/guides/opentelemetry.txt): Configure OTLP export to Firetiger from OpenTelemetry collectors or application SDKs
- [MCP Server](https://docs.firetiger.com/guides/mcp-server.txt): Connect Claude Desktop, Cursor, or Claude Code to Firetiger via the MCP server endpoint
- [Agent Webhooks](https://docs.firetiger.com/guides/agent-webhooks.txt): How to invoke agents via HTTP webhook using a stable webhook URL
- [BigQuery Integration](https://docs.firetiger.com/guides/bigquery.txt): Query Firetiger Iceberg tables from BigQuery using BigLake on AWS deployments
- [incident.io Workflows](https://docs.firetiger.com/guides/incident-io-workflows.txt): Trigger Firetiger agents automatically from incident.io workflow webhooks
- [Monitoring your deploys](https://docs.firetiger.com/guides/deploy-monitoring.txt): Set up per-PR deploy monitoring with GitHub tagging, monitoring plans, and scheduled checks
- [Connect to a Private Database with Tailscale](https://docs.firetiger.com/guides/tailscale-private-network.txt)

## Deployment Options

- [SaaS](https://docs.firetiger.com/deploy/saas.txt): Firetiger SaaS: fully managed hosted deployment with no infrastructure to maintain
- [BYOC: AWS](https://docs.firetiger.com/deploy/aws.txt): BYOC AWS setup: cross-account IAM role via CloudFormation and Bedrock model access
- [BYOC: GCP](https://docs.firetiger.com/deploy/gcp.txt): BYOC GCP setup: project creation, billing, required APIs, and IAM for Firetiger service account

## Account Management

- [Google Workspace](https://docs.firetiger.com/sso/google-workspace.txt): Configure Google Workspace as a SAML identity provider for SSO login to Firetiger
- [API Keys](https://docs.firetiger.com/account-management/api_keys.txt): Create, use, and revoke API keys for programmatic HTTP Basic auth access to the Firetiger API

## Optional

## Integrations

- [PostgreSQL](https://docs.firetiger.com/integrations/databases/postgres.txt): Connect agents to PostgreSQL databases for read-only querying with SSL, role-based access, and read-only mode
- [MySQL](https://docs.firetiger.com/integrations/databases/mysql.txt): Connect agents to MySQL databases for read-only querying with SSL modes and session-level read-only enforcement
- [ClickHouse](https://docs.firetiger.com/integrations/databases/clickhouse.txt): Connect agents to ClickHouse analytical databases for read-only querying with TLS and native protocol
- [AWS](https://docs.firetiger.com/integrations/infrastructure/aws.txt): Connect to AWS via IAM role assumption (STS AssumeRole) with CloudFormation setup for cross-account access
- [GCP](https://docs.firetiger.com/integrations/infrastructure/gcp.txt): Connect to GCP via service account key authentication for access to Google Cloud Platform resources
- [AWS CloudWatch Logs](https://docs.firetiger.com/integrations/infrastructure/aws-cloudwatch.txt): Ingest AWS CloudWatch Logs into Firetiger via Terraform or CloudFormation Lambda deployment
- [AWS ECS Events](https://docs.firetiger.com/integrations/infrastructure/aws-ecs.txt): Ingest AWS ECS task lifecycle events including container failures and OOMKilled events
- [CloudFront Kinesis Integration](https://docs.firetiger.com/integrations/infrastructure/cloudfront-kinesis.txt): Stream CloudFront real-time logs to Firetiger via Kinesis Data Stream and Firehose with field mapping
- [Cloudflare Workers Integration](https://docs.firetiger.com/integrations/infrastructure/cloudflare-workers.txt): Export Cloudflare Workers traces and logs to Firetiger via built-in OpenTelemetry OTLP destinations
- [Cloudflare Logpush Integration](https://docs.firetiger.com/integrations/infrastructure/cloudflare-logpush.txt): Ingest Cloudflare HTTP request logs via Logpush direct HTTP destination
- [GitHub](https://docs.firetiger.com/integrations/developer-tools/github.txt): Install the Firetiger GitHub App for codebase search context during investigations and event ingestion
- [GitHub Webhooks](https://docs.firetiger.com/integrations/developer-tools/github-webhook.txt): Automatically ingest GitHub webhook events (pushes, PRs, workflow runs) into the github_events table
- [Incident.io](https://docs.firetiger.com/integrations/developer-tools/incident-io.txt): Connect agents to incident.io for creating, listing, and editing incidents via the HTTP connection type
- [Pylon](https://docs.firetiger.com/integrations/developer-tools/pylon.txt): Connect agents to Pylon for creating internal issues and looking up customer accounts
- [Slack](https://docs.firetiger.com/integrations/communications/slack.txt): Connect a Slack workspace so agents can send notifications and alerts to channels
- [SendGrid Event Webhooks](https://docs.firetiger.com/integrations/communications/sendgrid-webhook.txt): Ingest SendGrid email event webhooks into per-event-type tables for delivery, bounce, and engagement tracking
- [Google Postmaster Tools](https://docs.firetiger.com/integrations/communications/google-postmaster.txt): Connect agents to Google Postmaster Tools for email deliverability metrics, domain reputation, and spam rates
- [Vector](https://docs.firetiger.com/integrations/observability/vector.txt): Configure a Vector HTTP sink to send logs, metrics, or traces to Firetiger with basic auth
- [Datadog Agent](https://docs.firetiger.com/integrations/observability/datadog.txt): Forward APM traces and metrics from a Datadog Agent to Firetiger, with single-destination or dual-write modes
- [DataDog Log Forwarding](https://docs.firetiger.com/integrations/observability/datadog-forward.txt): Forward logs from Datadog to Firetiger via a custom log destination with severity and timestamp mapping
- [HTTP](https://docs.firetiger.com/integrations/custom/http.txt): Connect agents to any REST API via HTTP with configurable routes, authentication, and response limits
- [MCP Servers](https://docs.firetiger.com/integrations/custom/mcp.txt): Connect agents to external MCP servers (GitHub, Linear, Notion, Sentry, etc.) via OAuth for tool access
- [OpenAPI](https://docs.firetiger.com/integrations/custom/openapi.txt): Connect agents to any REST API with an OpenAPI specification for automatic endpoint discovery
- [AWS VPC Peering](https://docs.firetiger.com/integrations/networking/aws-vpc-peering.txt): Set up VPC peering between your AWS VPC and a Firetiger BYOC deployment for private network access
- [Tailscale](https://docs.firetiger.com/integrations/networking/tailscale.txt)

## API Reference

- [Agents](https://docs.firetiger.com/api-reference/agents.txt): CRUD agents and sessions, send and read messages, and retrieve artifacts via the AgentService API
- [Connections](https://docs.firetiger.com/api-reference/connections.txt): Read-only API to list and inspect configured connections and available connection types
- [Customers](https://docs.firetiger.com/api-reference/customers.txt): CRUD customer resources identified by external_id, with display names and associated runbooks
- [Deployments](https://docs.firetiger.com/api-reference/deployments.txt): Track deployment events and deployment monitor evaluations via the Deployments API
- [Investigations](https://docs.firetiger.com/api-reference/investigations.txt): Create and manage agent-driven investigation sessions that diagnose system issues
- [Issues](https://docs.firetiger.com/api-reference/issues.txt): Read agent-detected issues and configure notification policies for alert routing
- [Known Issues](https://docs.firetiger.com/api-reference/known-issues.txt): CRUD known issues to track recurring problems with active, resolved, and muted lifecycle states
- [Monitoring Plans](https://docs.firetiger.com/api-reference/monitoring-plans.txt): Read-only API for PR-based deployment monitoring plans and their per-environment run results
- [Notes](https://docs.firetiger.com/api-reference/notes.txt): CRUD free-form notes that capture observations, tool outputs, and investigation context
- [Tags](https://docs.firetiger.com/api-reference/tags.txt): CRUD tags for organizing and filtering agents
- [Runbooks](https://docs.firetiger.com/api-reference/runbooks.txt): CRUD runbooks with structured operating procedures, associated connections, and enabled tools
- [Triggers](https://docs.firetiger.com/api-reference/triggers.txt): CRUD and invoke triggers that start agent sessions on cron schedules, manual, or post-deploy events
- [Agent](https://docs.firetiger.com/api-reference/types/agent.txt): Agent resource type with name, title, system prompt, connections, state, and model configuration
- [Session](https://docs.firetiger.com/api-reference/types/session.txt): Session resource type with status, conclusion, artifacts, and SessionDescription summary fields
- [Connection](https://docs.firetiger.com/api-reference/types/connection.txt): Connection resource type with connection details, tool configurations, and all ConnectionType/Tool enums
- [Customer](https://docs.firetiger.com/api-reference/types/customer.txt): Customer resource type with external_id, display name, description, runbook, and workload summary
- [Deployment](https://docs.firetiger.com/api-reference/types/deployment.txt): Deployment resource type with source, status, labels, and related DeploymentMonitorEvaluation type
- [Investigation](https://docs.firetiger.com/api-reference/types/investigation.txt): Investigation resource type with display name, description, and status (executing or waiting)
- [Issue](https://docs.firetiger.com/api-reference/types/issue.txt): Issue and IssueNotificationPolicy types with states, severity, routing, and notification config
- [Known Issue](https://docs.firetiger.com/api-reference/types/known-issue.txt): KnownIssue resource type with title, context, human description, and lifecycle status fields
- [Monitoring Plan](https://docs.firetiger.com/api-reference/types/monitoring-plan.txt): MonitoringPlan type with PR origin, activation trigger, plan content, and per-environment outcomes
- [Note](https://docs.firetiger.com/api-reference/types/note.txt): Note resource type with display name, content, and optional tool name and arguments
- [Runbook](https://docs.firetiger.com/api-reference/types/runbook.txt): Runbook resource type with text instructions and connection references with enabled tool lists
- [Tag](https://docs.firetiger.com/api-reference/types/tag.txt): Tag resource type for organizing and filtering agents
- [Trigger](https://docs.firetiger.com/api-reference/types/trigger.txt): Trigger resource type with cron, manual, and post-deploy configurations and activation state
- [Activity](https://docs.firetiger.com/api-reference/types/activity.txt): Union type for agent session events: user messages, assistant messages, errors, and external inputs