Skip to main content
Aiven provides integrations with popular monitoring and logging platforms, enabling you to include your Aiven service data in your existing observability infrastructure. You can send both metrics and logs to external services for analysis, alerting, and long-term storage.

​
Available integrations

AWS CloudWatch

Send metrics and logs to Amazon CloudWatch for monitoring and analysis

Datadog

Integrate with Datadog for comprehensive monitoring and alerting

Prometheus

Export system metrics to Prometheus for monitoring and visualization

Rsyslog

Forward logs to external syslog servers and logging platforms

Elasticsearch

Store and analyze service logs in external Elasticsearch clusters

​
Metrics vs logs

​
Metrics integrations

Metrics provide quantitative data about your service performance and resource usage:
  • AWS CloudWatch Metrics - Send service metrics to CloudWatch with customizable namespaces
  • Datadog Metrics - Export metrics with custom tags for enhanced filtering and analysis
  • Prometheus - Expose system-level metrics including CPU, memory, disk, and network usage

​
Logs integrations

Logs capture detailed event information and operational data from your services:
  • AWS CloudWatch Logs - Stream service logs to CloudWatch log groups
  • Datadog Logs (via Rsyslog) - Forward logs to Datadog for correlation with metrics
  • Rsyslog - Send logs to any rsyslog-compatible destination
  • Elasticsearch - Store logs in external Elasticsearch for search and analysis

​
Integration workflow

All Aiven integrations follow a similar setup process:
1

Create integration endpoint

Configure the external service connection in your Aiven project. This endpoint can be reused across multiple services.
2

Enable integration on service

Link the integration endpoint to your Aiven service to start sending data.
3

Verify data flow

Check your external monitoring or logging platform to confirm data is being received.
You can manage integrations through the Aiven Console or using the Aiven CLI.

​
Security considerations

  • TLS encryption - Most integrations support or require TLS encryption for secure data transmission
  • Authentication - Use API keys, access keys, or certificates to authenticate with external services
  • Access control - Ensure external service credentials have appropriate permissions
  • Data privacy - Logs may contain sensitive information; use secure transport and storage
When configuring log integrations, ensure that TLS is enabled if the remote server supports it, as logs may contain sensitive information.

​
Next steps

Build docs developers (and LLMs) love

Get started for freeTalk to us