Kloudmate

Send logs, metrics, and traces to Kloudmate using OTLP over HTTP.

Supported Telemetry Types

Logs
Metrics
Traces

Prerequisites

  • A Kloudmate account with an API key

  • Network connectivity from the collector to otel.kloudmate.com on port 4318

Basic Configuration

The Kloudmate destination requires only your API key for basic setup.

Parameter
Type
Required
Default
Description

Choose Telemetry Type

telemetrySelector

No

Logs, Metrics, Traces

Select which types of telemetry to export

API Key

string

Yes

-

Kloudmate API key used for authentication

Advanced Configuration

General Settings

Parameter
Type
Required
Default
Description

Compression

enum

No

gzip

Compression algorithm (none, gzip)

Drop Raw Copy

bool

No

true

Drop the raw log copy stored in log.record.original

TLS Configuration

Parameter
Type
Required
Default
Description

Enable TLS

bool

No

false

Configure advanced TLS settings

Skip TLS Certificate Verification

bool

No

false

Skip TLS certificate verification

TLS Certificate Authority File

string

No

-

Certificate authority for TLS validation

Retry on Failure

Parameter
Type
Required
Default
Description

Enable Retry on Failure

bool

No

true

Retry sending failed telemetry data

Initial Interval

int

No

5

Seconds to wait after first failure

Max Interval

int

No

30

Upper bound on backoff in seconds

Max Elapsed Time

int

No

300

Maximum retry duration in seconds

Sending Queue

Parameter
Type
Required
Default
Description

Enable Sending Queue

bool

No

true

Buffer telemetry data before sending

Number of Consumers

int

No

10

Number of consumers that dequeue batches

Queue Size

int

No

5000

Maximum batches kept in memory

Enable Persistent Queuing

bool

No

true

Buffer telemetry data to disk

Persistent Queue Storage

extension

Yes (if persistent queue enabled)

file_storage

Storage for the persistent queue

Configuration Tips

API Key Management

  • Store your Kloudmate API key securely; avoid hardcoding it in configuration files

  • Rotate API keys periodically through the Kloudmate dashboard

Data Volume Optimization

  • Keep gzip compression enabled (default) to reduce bandwidth usage

  • Enable "Drop Raw Copy" to reduce log payload size when the original log body is not needed

Troubleshooting

Authentication Failures

  • Verify your API key is correct and has not been revoked in the Kloudmate dashboard

  • Ensure the API key is entered without extra whitespace or quotes

Connection Issues

  • Confirm outbound HTTPS traffic to otel.kloudmate.com:4318 is allowed by your firewall

  • Check collector logs for TLS handshake errors if using custom CA certificates

Data Not Appearing in Kloudmate

  • Verify the correct telemetry types are selected in the destination configuration

  • Check that your Kloudmate account has sufficient data ingestion quota

Last updated

Was this helpful?