Destinations

Destinations are the final endpoints where your processed telemetry data is sent for storage, analysis, or visualization. This section provides documentation for all supported destination platforms and systems.

What are Destinations?

Destinations receive and store your telemetry data for:

• Observability: Monitoring, alerting, and visualization

• Security: Threat detection and compliance monitoring

• Analytics: Data analysis and business intelligence

• Storage: Long-term data retention and archival

• Integration: Connecting with other tools and platforms

Destination Categories

Observability Platforms

• APM & Monitoring: Datadog, New Relic, Splunk Observability Cloud, ClickHouse/ClickStack

• Log Management: Elasticsearch, Splunk, Logz.io, Coralogix, ClickHouse/ClickStack

• Metrics & Monitoring: Prometheus, Grafana Cloud, Victoria Metrics, ClickHouse/ClickStack

• Distributed Tracing: Jaeger, Zipkin, Honeycomb.io, ClickHouse/ClickStack

Cloud Services

• AWS: CloudWatch, S3, Managed Prometheus

• Google Cloud: Cloud Logging, Cloud Monitoring, Cloud Storage

• Azure: Monitor, Blob Storage, Sentinel

• Multi-Cloud: Cross-platform observability solutions

Security & Compliance

• SIEM Platforms: Splunk, QRadar, Microsoft Sentinel

• Security Operations: Google SecOps, Chronicle

• Compliance: Audit logging and regulatory compliance

• Threat Detection: Security monitoring and alerting

Storage & Analytics

• Databases: ClickHouse, InfluxDB, Snowflake

• Data Lakes: S3, Azure Blob Storage, Google Cloud Storage

• Message Queues: Kafka, RabbitMQ

• Custom Endpoints: HTTP webhooks, OTLP endpoints

Supported Telemetry Types

Each destination supports one or more telemetry types:

• Logs: Text-based data for debugging and analysis

• Metrics: Numerical data for monitoring and alerting

• Traces: Distributed tracing data for performance analysis

Available Destinations

Observability Platforms

Cloud Services

Security & Compliance

Storage & Analytics

Distributed Tracing

Custom & Development

Getting Started

Choose Your Destinations

1. Identify Your Use Cases: Determine what you want to achieve with your data

2. Select Appropriate Destinations: Choose destinations that match your needs

3. Plan Data Flow: Consider how data will flow through your pipeline

4. Configure Destinations: Set up destination configurations in Bindplane

Best Practices

• Start Simple: Begin with basic destinations and add complexity gradually

• Use Multiple Destinations: Send different data types to appropriate destinations

• Monitor Performance: Watch for data flow and destination performance

• Test Configurations: Use live preview to test destination configurations

• Plan for Scale: Consider data volume and destination capacity

• Security First: Use secure authentication and encryption for sensitive data

• Backup Strategy: Consider multiple destinations for redundancy

Destination Features

Persistent Queuing

Many destinations support persistent queuing, which allows data to be buffered locally when the destination is unavailable, ensuring no data loss during network issues or destination downtime.

Proxy Support

Some destinations support proxy configurations for environments that require traffic to go through corporate proxies or firewalls.

Retry Mechanisms

All destinations include configurable retry mechanisms to handle temporary failures and ensure reliable data delivery.

Authentication

Destinations support various authentication methods including:

• API Keys and Tokens

• OAuth 2.0

• Service Account credentials

• Certificate-based authentication

Next Steps

• Browse all available destinations to find what you need

• Learn about sources for data collection

• Explore processors for data transformation

• Understand destination configuration best practices

• Set up your first destination