# HealOps Documentation ## Docs - [DEVELOPMENT](https://docs.healops.ai/DEVELOPMENT.md) - [Local Agent Fleet](https://docs.healops.ai/agents.md): Slash-command surface for monitoring, coordinating, and exchanging context between local AI agents (Claude Code, Cursor, Aider, ...) - [Airflow](https://docs.healops.ai/airflow.md): Investigate DAG failures and extract execution context from Apache Airflow. - [Alertmanager](https://docs.healops.ai/alertmanager.md): Connect Alertmanager so HealOps can surface firing alerts and active silences during investigations - [Argo CD](https://docs.healops.ai/argocd.md): Connect Argo CD so HealOps can inspect GitOps application health, sync state, revisions, and drift during investigations - [AWS](https://docs.healops.ai/aws.md): Connect AWS so HealOps can map your infrastructure and investigate cloud-related alerts - [Azure Monitor](https://docs.healops.ai/azure-monitor.md): Connect Azure Monitor Log Analytics so HealOps can pull KQL log evidence during investigations - [Better Stack Telemetry](https://docs.healops.ai/betterstack.md): Connect Better Stack so HealOps can pull log evidence from your Telemetry sources during investigations - [Bitbucket](https://docs.healops.ai/bitbucket.md): Connect Bitbucket so HealOps can correlate recent commits and code changes with incidents - [CLI Integration Setup](https://docs.healops.ai/cli-integration-setup.md): Install the HealOps CLI, connect your integrations, and run your first investigation - [ClickHouse](https://docs.healops.ai/clickhouse.md): Connect ClickHouse so HealOps can inspect query activity and system health during investigations - [How to use Tracer with AWS CloudWatch](https://docs.healops.ai/comparisons/Tracer_vs_AWS_CloudWatch.md): Execution-level insight beneath cloud-native infrastructure monitoring - [How to use Tracer with Apache Airflow](https://docs.healops.ai/comparisons/Tracer_vs_Airflow.md): What DAGs does not show at runtime - [How to use Tracer with Dagster](https://docs.healops.ai/comparisons/Tracer_vs_Dagster.md): Execution insight beneath assets and jobs - [Tracer and Datadog](https://docs.healops.ai/comparisons/Tracer_vs_Datadog.md): Execution-aware insight beneath general-purpose observability - [How to use Tracer with Flyte](https://docs.healops.ai/comparisons/Tracer_vs_Flyte.md): Execution insight beneath tasks and workflows - [How to use Tracer with Grafana](https://docs.healops.ai/comparisons/Tracer_vs_Grafana.md): Execution-aware context beyond dashboards - [How to use Tracer with Prefect](https://docs.healops.ai/comparisons/Tracer_vs_Prefect.md): Runtime visibility beneath flow state - [How to use Tracer with Prometheus](https://docs.healops.ai/comparisons/Tracer_vs_Prometheus.md): Observed execution beneath scraped metrics - [How to use Tracer with Seqera](https://docs.healops.ai/comparisons/Tracer_vs_Seqera.md): Execution behavior inside Nextflow pipelines - [Cloud-native monitoring integrations](https://docs.healops.ai/comparisons/cloud-native-monitoring.md): How Tracer adds execution-level and host-observed insight beyond cloud service metrics - [Observability and telemetry tools](https://docs.healops.ai/comparisons/observability-tools.md): How Tracer adds execution-aware context to metrics, logs, and dashboards - [How Tracer fits in your stack](https://docs.healops.ai/comparisons/overview.md): Where Tracer fits in modern scientific and data platforms - [Workflow orchestration](https://docs.healops.ai/comparisons/workflow-orchestration.md): How Tracer adds execution-level visibility beneath schedulers and workflow engines - [Connect integrations](https://docs.healops.ai/connect-integrations.md): How to connect your tools to HealOps from the web app integration page - [Coralogix](https://docs.healops.ai/coralogix.md): Connect Coralogix so HealOps can query logs during investigations - [Daily Update — 2026-04-02](https://docs.healops.ai/daily-updates/2026-04-02.md): HealOps engineering daily update for 2026-04-02 (Europe/London) - [Daily Update — 2026-04-03](https://docs.healops.ai/daily-updates/2026-04-03.md): HealOps engineering daily update for 2026-04-03 (Europe/London) - [Daily Update — 2026-04-04](https://docs.healops.ai/daily-updates/2026-04-04.md): HealOps engineering daily update for 2026-04-04 (Europe/London) - [Daily Update — 2026-04-05](https://docs.healops.ai/daily-updates/2026-04-05.md): HealOps engineering daily update for 2026-04-05 (Europe/London) - [Daily Update — 2026-04-06](https://docs.healops.ai/daily-updates/2026-04-06.md): HealOps engineering daily update for 2026-04-06 (Europe/London) - [Daily Update — 2026-04-07](https://docs.healops.ai/daily-updates/2026-04-07.md): HealOps engineering daily update for 2026-04-07 (Europe/London) - [Daily Update — 2026-04-08](https://docs.healops.ai/daily-updates/2026-04-08.md): HealOps engineering daily update for 2026-04-08 (Europe/London) - [Daily Update — 2026-04-09](https://docs.healops.ai/daily-updates/2026-04-09.md): HealOps engineering daily update for 2026-04-09 (Europe/London) - [Daily Update — 2026-04-10](https://docs.healops.ai/daily-updates/2026-04-10.md): HealOps engineering daily update for 2026-04-10 (Europe/London) - [Daily Update — 2026-04-11](https://docs.healops.ai/daily-updates/2026-04-11.md): HealOps engineering daily update for 2026-04-11 (Europe/London) - [Daily Update — 2026-04-12](https://docs.healops.ai/daily-updates/2026-04-12.md): HealOps engineering daily update for 2026-04-12 (Europe/London) - [Daily Update — 2026-04-13](https://docs.healops.ai/daily-updates/2026-04-13.md): HealOps engineering daily update for 2026-04-13 (Europe/London) - [Daily Update — 2026-04-14](https://docs.healops.ai/daily-updates/2026-04-14.md): HealOps engineering daily update for 2026-04-14 (Europe/London) - [Daily Update — 2026-04-15](https://docs.healops.ai/daily-updates/2026-04-15.md): HealOps engineering daily update for 2026-04-15 (Europe/London) - [Daily Update — 2026-04-16](https://docs.healops.ai/daily-updates/2026-04-16.md): HealOps engineering daily update for 2026-04-16 (Europe/London) - [Daily Update — 2026-04-17](https://docs.healops.ai/daily-updates/2026-04-17.md): HealOps engineering daily update for 2026-04-17 (Europe/London) - [Daily Update — 2026-04-18](https://docs.healops.ai/daily-updates/2026-04-18.md): HealOps engineering daily update for 2026-04-18 (Europe/London) - [Daily Update — 2026-04-19](https://docs.healops.ai/daily-updates/2026-04-19.md): HealOps engineering daily update for 2026-04-19 (Europe/London) - [Daily Update — 2026-04-20](https://docs.healops.ai/daily-updates/2026-04-20.md): HealOps engineering daily update for 2026-04-20 (Europe/London) - [Daily Update — 2026-04-21](https://docs.healops.ai/daily-updates/2026-04-21.md): HealOps engineering daily update for 2026-04-21 (Europe/London) - [Daily Update — 2026-04-22](https://docs.healops.ai/daily-updates/2026-04-22.md): HealOps engineering daily update for 2026-04-22 (Europe/London) - [Daily Update — 2026-04-23](https://docs.healops.ai/daily-updates/2026-04-23.md): HealOps engineering daily update for 2026-04-23 (Europe/London) - [Daily Update — 2026-04-24](https://docs.healops.ai/daily-updates/2026-04-24.md): HealOps engineering daily update for 2026-04-24 (Europe/London) - [Daily Update — 2026-04-25](https://docs.healops.ai/daily-updates/2026-04-25.md): HealOps engineering daily update for 2026-04-25 (Europe/London) - [Daily Update — 2026-04-26](https://docs.healops.ai/daily-updates/2026-04-26.md): HealOps engineering daily update for 2026-04-26 (Europe/London) - [Daily Update — 2026-04-27](https://docs.healops.ai/daily-updates/2026-04-27.md): HealOps engineering daily update for 2026-04-27 (Europe/London) - [Daily Update — 2026-04-28](https://docs.healops.ai/daily-updates/2026-04-28.md): HealOps engineering daily update for 2026-04-28 (Europe/London) - [Daily Update — 2026-04-29](https://docs.healops.ai/daily-updates/2026-04-29.md): HealOps engineering daily update for 2026-04-29 (Europe/London) - [Daily Update — 2026-04-30](https://docs.healops.ai/daily-updates/2026-04-30.md): HealOps engineering daily update for 2026-04-30 (Europe/London) - [Daily Update — 2026-05-01](https://docs.healops.ai/daily-updates/2026-05-01.md): HealOps engineering daily update for 2026-05-01 (Europe/London) - [Daily Update — 2026-05-02](https://docs.healops.ai/daily-updates/2026-05-02.md): HealOps engineering daily update for 2026-05-02 (Europe/London) - [Daily Update — 2026-05-03](https://docs.healops.ai/daily-updates/2026-05-03.md): HealOps engineering daily update for 2026-05-03 (Europe/London) - [Daily Update — 2026-05-04](https://docs.healops.ai/daily-updates/2026-05-04.md): HealOps engineering daily update for 2026-05-04 (Europe/London) - [Daily Update — 2026-05-05](https://docs.healops.ai/daily-updates/2026-05-05.md): HealOps engineering daily update for 2026-05-05 (Europe/London) - [Weekly changelog — Week ending May 5, 2026](https://docs.healops.ai/daily-updates/2026-05-05-weekly.md): Product updates shipped between April 29 and May 5, 2026 - [Daily Updates](https://docs.healops.ai/daily-updates/overview.md): HealOps engineering daily updates from merged pull requests - [Datadog](https://docs.healops.ai/datadog.md) - [Deployment](https://docs.healops.ai/deployment.md): Deploy HealOps as a standard Python/FastAPI runtime - [AWS Batch](https://docs.healops.ai/environments/aws-batch.md): Install Tracer on AWS Batch (Multi-Node) under two minutes - [Our Demo Environment](https://docs.healops.ai/environments/codespaces.md): Run Tracer in our demo environment within minutes - [Docker](https://docs.healops.ai/environments/docker.md): Install Tracer within your Docker under two minutes - [Google Batch](https://docs.healops.ai/environments/google-batch.md): Install Tracer on Google Cloud Batch under two minutes - [Linux](https://docs.healops.ai/environments/linux-cloud.md): Install Tracer on your Linux cloud instances (AWS EC2, GCP, Azure, etc.) under two minutes - [Linux](https://docs.healops.ai/environments/linux-local.md): Install Tracer on your local Linux machine under two minutes - [macOS](https://docs.healops.ai/environments/macos.md): Install Tracer locally on your macOS under two minutes - [Environments](https://docs.healops.ai/environments/overview.md): Choose the right environment to run Tracer for your workflow - [Windows](https://docs.healops.ai/environments/windows-local.md): Run Tracer on Windows using WSL or GitHub Codespaces - [Code blocks](https://docs.healops.ai/essentials/code.md): Display inline code and code blocks - [Images and embeds](https://docs.healops.ai/essentials/images.md): Add image, video, and other HTML elements - [Markdown syntax](https://docs.healops.ai/essentials/markdown.md): Text, title, and styling in standard markdown - [Navigation](https://docs.healops.ai/essentials/navigation.md): The navigation field in docs.json defines the pages that go in the navigation menu - [Reusable snippets](https://docs.healops.ai/essentials/reusable-snippets.md): Reusable, custom snippets to keep content in sync - [Global Settings](https://docs.healops.ai/essentials/settings.md): Mintlify gives you complete control over the look and feel of your documentation using the docs.json file - [Eval terminal metrics runbook](https://docs.healops.ai/eval_terminal_metrics_runbook.md) - [FAQ](https://docs.healops.ai/faq.md): Frequently asked questions about HealOps - [Features](https://docs.healops.ai/features.md): What HealOps can do today - [GitHub](https://docs.healops.ai/github.md): Connect GitHub so HealOps can correlate recent commits and code changes with incidents - [GitLab](https://docs.healops.ai/gitlab.md) - [Google Docs](https://docs.healops.ai/google-docs.md): Connect Google Docs so HealOps can write investigation reports to your Google Drive - [Grafana](https://docs.healops.ai/grafana.md) - [Helm (CLI)](https://docs.healops.ai/helm.md): Connect Helm 3 so HealOps can list releases, inspect status and history, and read rendered values and manifests during Kubernetes investigations - [Hermes log monitoring](https://docs.healops.ai/hermes.md): Tail Hermes errors.log, classify incidents, alert on Telegram; run offline classifier regression tests, then try a local watch demo. - [Honeycomb](https://docs.healops.ai/honeycomb.md): Connect Honeycomb so HealOps can query traces during investigations - [incident.io](https://docs.healops.ai/incident_io.md): Connect incident.io so HealOps can read incident context, updates, and metadata during investigations - [HealOps](https://docs.healops.ai/index.md) - [Install HealOps](https://docs.healops.ai/install.md): Choose the right HealOps installation path for local or enterprise environments - [Enterprise setup](https://docs.healops.ai/install-enterprise.md): Set up HealOps for your organization in app.healops.ai - [Local and on-prem setup](https://docs.healops.ai/install-local.md): Run HealOps locally with the CLI binary and onboard integrations from your environment - [Integrations overview](https://docs.healops.ai/integrations-overview.md) - [AWS Integration](https://docs.healops.ai/integrations/aws.md): Using HealOps with AWS services - [Bash](https://docs.healops.ai/integrations/bash.md): Using Tracer with Bash scripts - [Integration Workflow](https://docs.healops.ai/integrations/integration-workflow.md): Choose the right framework integration for your workflow - [macOS](https://docs.healops.ai/integrations/macos.md): Using HealOps on macOS - [Nextflow](https://docs.healops.ai/integrations/nextflow.md): Monitor Nextflow pipelines with Tracer - [Slurm](https://docs.healops.ai/integrations/slurm.md): Monitor Slurm workloads with Tracer - [Snakemake](https://docs.healops.ai/integrations/snakemake.md): Monitor Snakemake workflows with Tracer - [Trello Integration](https://docs.healops.ai/integrations/trello.md): Set up the Trello integration for incident task tracking. - [WDL](https://docs.healops.ai/integrations/wdl.md): Using Tracer with WDL workflows - [Interactive Shell Privacy](https://docs.healops.ai/interactive-shell-privacy.md): How HealOps redacts secrets from your command history, and the controls you have over persistence - [Tracer Monitoring](https://docs.healops.ai/introduction-monitoring.md) - [Investigations overview](https://docs.healops.ai/investigation-overview.md) - [Jira](https://docs.healops.ai/jira.md): Connect Jira so HealOps can create and update incident tickets automatically - [Kafka](https://docs.healops.ai/kafka.md): Connect Kafka so HealOps can inspect topic health and consumer group lag during investigations - [LLM Providers](https://docs.healops.ai/llm-providers.md): Supported LLM APIs and CLIs, environment variables, and how to switch between them. - [Local Agent Mode](https://docs.healops.ai/local-agent.md): Run HealOps as a local monitoring service on your machine or in your infrastructure - [MariaDB](https://docs.healops.ai/mariadb.md): Connect MariaDB so HealOps can diagnose database issues during investigations - [Masking Sensitive Identifiers](https://docs.healops.ai/masking.md): Reversible masking of pod, cluster, and account identifiers before external LLM calls - [Discord](https://docs.healops.ai/messaging/discord.md): Trigger investigations and receive findings inside a Discord server. - [Messaging](https://docs.healops.ai/messaging/index.md): Deliver investigation findings and trigger investigations from Slack, Discord, or Telegram. - [Slack](https://docs.healops.ai/messaging/slack.md): Deliver investigation findings to a Slack channel via incoming webhook. - [Telegram](https://docs.healops.ai/messaging/telegram.md): Deliver investigation findings to a Telegram chat or channel. - [WhatsApp](https://docs.healops.ai/messaging/whatsapp.md): Deliver investigation findings to WhatsApp via Twilio. - [MongoDB](https://docs.healops.ai/mongodb.md): Connect MongoDB so HealOps can diagnose database issues during investigations - [Multi-instance integrations](https://docs.healops.ai/multi-instance-integrations.md): Configure multiple accounts, regions, or clusters per provider - [MySQL](https://docs.healops.ai/mysql.md): Connect MySQL so HealOps can diagnose database issues during investigations - [OpenClaw](https://docs.healops.ai/openclaw.md): Connect HealOps to OpenClaw for native context lookup and RCA write-back - [OpenSearch / Elasticsearch](https://docs.healops.ai/opensearch.md): Connect OpenSearch or Elasticsearch so HealOps can search application logs and analytics indices during investigations - [OpsGenie](https://docs.healops.ai/opsgenie.md): Connect OpsGenie so HealOps can read active alerts and incident context during investigations - [PagerDuty](https://docs.healops.ai/pagerduty.md): Connect PagerDuty so HealOps can surface active incidents and on-call context during investigations - [PostgreSQL](https://docs.healops.ai/postgresql.md): Connect PostgreSQL so HealOps can diagnose database issues during investigations - [Prefect](https://docs.healops.ai/prefect.md): Connect Prefect so HealOps can inspect flow runs, workers, and deployments during investigations - [Quality baseline](https://docs.healops.ai/quality-baseline.md) - [Quickstart](https://docs.healops.ai/quickstart.md) - [Quickstart](https://docs.healops.ai/quickstart-monitoring.md): Start monitoring your first pipelines in minutes - [RabbitMQ](https://docs.healops.ai/rabbitmq.md): Connect RabbitMQ so HealOps can diagnose queue backlogs, consumer issues, and broker health during investigations - [AWS RDS](https://docs.healops.ai/rds.md): Investigate AWS RDS instance health and recent events during incidents - [Remote Runtime Investigation](https://docs.healops.ai/remote-runtime-investigation.md): Start an RCA investigation for a deployed service by name - [Sentry](https://docs.healops.ai/sentry.md): Connect Sentry so HealOps can surface error trends and issue details during investigations - [Showcase](https://docs.healops.ai/showcase.md): Real-world HealOps projects from the community - [Signoz](https://docs.healops.ai/signoz.md) - [Splunk](https://docs.healops.ai/splunk.md): Connect Splunk so HealOps can search logs using SPL during investigations - [Capabilities and compatibility](https://docs.healops.ai/technology/capabilities-compatibility.md): What Tracer supports and guarantees - [Data model](https://docs.healops.ai/technology/data-model.md): How Tracer structures execution data - [eBPF and security](https://docs.healops.ai/technology/ebpf-security.md): How Tracer observes execution safely and securely - [How Tracer works, end to end](https://docs.healops.ai/technology/end-to-end.md): A shared execution signal for analysis and optimization - [How It Works](https://docs.healops.ai/technology/how-it-works.md): Technology overview - [Limits and privacy](https://docs.healops.ai/technology/limits-privacy.md): What Tracer does and does not collect - [Features](https://docs.healops.ai/technology/our-features.md): Explore the features that gives developers a direct view into how scientific and ML pipelines actually run on their systems. - [Product Benefits](https://docs.healops.ai/technology/product-benefits.md): Understanding the value and opportunity of Tracer - [Tracer Agent](https://docs.healops.ai/technology/tracer-agent.md): Learn about the Tracer Agent architecture and capabilities - [Tracer/collect](https://docs.healops.ai/technology/tracer-collect.md): The core data collection daemon that powers Tracer observability - [Tracer/sweep](https://docs.healops.ai/technology/tracer-sweep.md): Systemwide cloud waste detection based on real execution activity - [Tracer/tune](https://docs.healops.ai/technology/tracer-tune.md): Turn "working" pipelines into fast, efficient pipelines - [Why eBPF](https://docs.healops.ai/technology/why-ebpf.md): Understanding why Tracer uses eBPF for observability - [Tracer FAQ](https://docs.healops.ai/tracer-faq.md): Frequently asked questions about Tracer - [Debugging nf-core demo pipeline](https://docs.healops.ai/tutorials/fastquorum-debugging.md): Using Tracer to diagnose and optimize UMI-based consensus sequencing - [Investigating Task Failures](https://docs.healops.ai/tutorials/investigating-task-failures.md): Debug and resolve failures with Tracer powerful diagnostic tools - [Viewing Task Status](https://docs.healops.ai/tutorials/viewing-task-status.md): Learn how to monitor and view the status of your tasks in Tracer - [Cost Center Mapping](https://docs.healops.ai/use-cases/cost-center-mapping.md): Attribute cloud costs to projects, teams, and research groups - [Cost Optimization](https://docs.healops.ai/use-cases/cost-optimization.md): Tools for understanding and reducing compute costs - [Data Lake Integration](https://docs.healops.ai/use-cases/datalake.md): Export pipeline telemetry and metrics to your data lake for custom analysis - [Accessing Logs](https://docs.healops.ai/use-cases/logging.md): Comprehensive logging and observability for scientific pipelines - [Metrics](https://docs.healops.ai/use-cases/metrics.md): Track and analyze comprehensive pipeline metrics with Tracer - [Right Sizing](https://docs.healops.ai/use-cases/right-sizing.md): Optimize resource allocation based on actual usage patterns - [Vercel](https://docs.healops.ai/vercel.md): Connect Vercel so HealOps can check deployment status and runtime logs during investigations - [VictoriaLogs](https://docs.healops.ai/victoria_logs.md): Connect VictoriaLogs so HealOps can pull structured log evidence during investigations ## OpenAPI Specs - [openapi](https://docs.healops.ai/api-reference/openapi.json)