OpenTelemetry plugin for AppScan 360°

A central telemetry gateway that automatically collects logs and metrics from all application services and routes each signal to the right monitoring backend.

All application services send their telemetry data (logs and metrics) to a single OpenTelemetry Collector. The collector acts as an intelligent router; it receives everything in one place and automatically forwards each type of data to the appropriate monitoring tool.

Components

Component Function Version
OpenTelemetry Operator Manages the lifecycle of collector instances inside Kubernetes. 0.120.0
OpenTelemetry Collector The actual gateway that receives and routes telemetry data. 0.165.0

Data management

  • Logs

    Routed to Elasticsearch (ECK). Automatically organized into named data streams based on log type and environment.

  • Metrics

    Sent to Prometheus and Elastic APM Server for dashboards and alerting.

  • Log routing example

    A service tagging logs with log.type=audit and environment=staging will land in the logs-asoc-audit-staging data stream automatically.

Connecting services

Instrumented services point their telemetry exporter at the collector using the gRPC endpoint below. No extra configuration is needed — the collector handles the rest.
opentelemetry-collector.opentelemetry-collector.svc.cluster.local:4317
For logs to be routed correctly, services should also set two attributes:
  • log.type
    For example:
    • audit
    • app
  • deployment.environment
    For example:
    • staging
    • production

Installation

Both components — the Operator and the Collector — can be installed using the official Helm charts from the OpenTelemetry project, or any other installation method your team prefers (Argo CD, Flux, plain manifests, and so on).

Charts are available at open-telemetry.github.io/opentelemetry-helm-charts.

Additional information