> ## Documentation Index
> Fetch the complete documentation index at: https://www.qovery.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Observe

> Monitor your applications with built-in observability

Qovery provides integrated observability to help you monitor the health, performance, and behavior of your services directly within the Qovery Console. Your observability data stays within your infrastructure with zero maintenance required.

<img src="https://mintcdn.com/qovery/kTQizHnnz6yZZ5Tx/images/observability/overview.png?fit=max&auto=format&n=kTQizHnnz6yZZ5Tx&q=85&s=e2fc7577c2f302e7d3f043354c95fb10" alt="Qovery Observability Overview" width="2784" height="1820" data-path="images/observability/overview.png" />

<Note>
  Supports Applications, Containers, and Managed Databases (MySQL and PostgreSQL on AWS only). Jobs support coming soon.
</Note>

<Info>
  Qovery Observe is not yet self-service. Contact Qovery via Slack or email to get access.
</Info>

## What You Get

<CardGroup cols={2}>
  <Card title="Service Health" icon="heart-pulse">
    Real-time service health and performance tracking
  </Card>

  <Card title="Metrics" icon="chart-line">
    CPU, memory, network, request latency, error rates, and database performance metrics
  </Card>

  <Card title="Logs" icon="file-lines">
    12 weeks log retention with automatic error detection
  </Card>

  <Card title="Events" icon="clock">
    Qovery and Kubernetes events (deployments, scaling, failures)
  </Card>

  <Card title="Alerts" icon="bell">
    Proactive monitoring with customizable alerts and notifications
  </Card>
</CardGroup>

## Key Benefits

* **Data stays in your infrastructure**: All observability data remains within your cloud
* **Zero maintenance**: No configuration or management required
* **Correlated data**: Metrics and logs automatically linked for faster troubleshooting

## Getting Started

Access the **Monitoring** section at the service level to view real-time and historical data (Dashboard tab), create alerts (Alerts tab), or use the **Logs** tab for log analysis.

The navigation menu also includes a dedicated **Alerting** section where you can manage notification channels, view all alert rules, and monitor active issues across your services.

For detailed documentation on features, configuration, and best practices, see the [Qovery Observe documentation](/configuration/integrations/observability/qovery-observe).

## Next Steps

<CardGroup cols={2}>
  <Card title="Qovery Observe" icon="chart-line" href="/configuration/integrations/observability/qovery-observe">
    Full observability documentation
  </Card>

  <Card title="Slack Notifications" icon="slack" href="/configuration/integrations/slack">
    Set up Slack for alerts and notifications
  </Card>

  <Card title="Email Notifications" icon="envelope" href="/configuration/integrations/email">
    Set up email for alerts and notifications
  </Card>

  <Card title="Optimize" icon="gauge-high" href="/getting-started/guides/qovery-101/optimize">
    Optimize resources and reduce costs
  </Card>

  <Card title="Secure" icon="shield" href="/getting-started/guides/qovery-101/secure">
    Implement security best practices
  </Card>

  <Card title="Deployment Logs" icon="file-lines" href="/configuration/deployment/logs">
    View deployment and service logs
  </Card>
</CardGroup>