Log Forwarding to Your Log Collection Platform

2Ring Dashboards & Wallboards can forward your application logs in real time to your own log collection platform. Logs are scoped strictly to your deployment. No data from other customers is ever included.

What Gets Forwarded

All logs generated within your tenant namespace are streamed to your endpoint. They arrive pre-processed: multiline entries are stitched together, structured labels are extracted (severity, component, service), and timestamps are normalized.

Supported Protocols

Protocol	Use case
Loki push API	Grafana Cloud (hosted Loki), self-hosted Loki, Grafana Enterprise Logs, and Mimir
OTLP/HTTP	Elastic, Splunk, Datadog, New Relic, Microsoft Sentinel, AWS CloudWatch, and other OTLP-capable backends
OTLP/gRPC	Same as OTLP/HTTP, for backends that prefer gRPC transport

Authentication

HTTP Basic Auth or Bearer token. Unauthenticated connections are also supported for endpoints secured by mTLS or IP allowlisting.

TLS

All connections are made over HTTPS/TLS. Custom CA certificates are supported for endpoints using private PKI.

Credential Management

Credentials are stored securely as a Kubernetes Secret within our cluster and are never exposed in configuration files or logs.

Configuration

To enable log forwarding, contact 2Ring Support and provide the following:

1. The push endpoint URL.

2. The protocol (Loki, OTLP/HTTP, or OTLP/gRPC).

3. Authentication credentials (Bearer token or username and password).

4. A CA certificate bundle, if your endpoint uses a private certificate authority.