Introducing Lawrence OSS

Today, we’re excited to announce Lawrence OSS.

An open-source platform for managing OpenTelemetry agents with a built-in observability backend and a web UI.

Lawrence OSS manages OpenTelemetry collectors via OpAMP protocol and stores their telemetry data for analysis. It runs as a single Go binary or Docker container with embedded storage.

You can try the early version here.

We’d love your feedback and ideas for improvement.

What does Lawrence OSS do?

• Manages OpenTelemetry collector agents remotely via OpAMP
• Ingests telemetry (traces, metrics, logs) via OTLP
• Stores agent configurations and telemetry data
• Provides a web UI for visualization and management

What does Lawrence OSS aim to help with?

• Keeping track at scale: see all your collectors in one place and know they’re status.
• Track versions: track and update the collector’s version and its effective config.
• View each collector’s internal telemetry, health, and workload at a glance.
• Update and apply configurations to groups of collectors from one UI.
• Understand pipelines with a clear, visual view instead of reading YAML.

In sum, Lawrence OSS centralizes remote configuration and status, so platform and observability teams can manage collectors like a fleet, not one-offs.

Star and contribute (pretty please): github.com/getlawrence/lawrence-oss

We’d love to chat

As we’re building Lawrence to enable teams with tools to automatically install, maintain, and troubleshoot OpenTelemetry at scale, we want to hear from you about your OpenTelemetry challenges (and hopefully help you solve them).

We’re currently in private beta, so if you’re migrating to OpenTelemetry, need to manage a fleet of OTel agents, need advice on OpenTelemetry (we know our stuff), or need a hug, request access here and we'll reach out.