Skip to main content

Installation overview

This section helps you run Praxis collectors in your environment: on single hosts (Linux, Windows, or macOS), in Kubernetes (using the collector supervisor and the OpenTelemetry Operator to run collector workloads), and optionally as a Praxis Gateway when you want a single aggregation and export tier. Pipelines, credentials, and organization policies are still defined in Praxis; these guides focus on where software runs and how it connects safely.

Choose your path​

GuideWhen to use it
Linux: Praxis collectorInstall the collector on a Linux server or VM with the script or package pattern your Praxis environment provides. OpAMP to Praxis, runs as a system service.
Windows: Praxis collectorInstall with the MSI / msiexec flow Praxis or your team provides, run as a Windows service, for Event Log and other Windows-native sources.
macOS: Praxis collectorInstall on Mac (including Apple Silicon or Intel) for workstations or small-scale hosts; same OpAMP model as Linux.
Kubernetes: InstallYou install the collector supervisor as a Deployment in a cluster, using the install script, OpAMP to Praxis, and generated collector CRs.
Kubernetes: UninstallRemove supervisor resources and optional host-path data from a cluster you previously installed.
Praxis Gateway collectorYou need one (or a few) central hosts to aggregate telemetry, share export credentials, and apply shared processors before data leaves your network. Read the overview first, then configuration and TLS and certificates as needed.

How these pieces fit together​

  • Praxis (management plane) — You define pipelines, destinations, and insights here. All collectors use OpAMP to Praxis to receive the right configuration (on Kubernetes, the supervisor coordinates child collectors; on Linux, Windows, and macOS, the collector registers directly with Praxis).
  • Child collectors (Kubernetes only) — The OpenTelemetry Operator runs OpenTelemetryCollector custom resources the supervisor creates; they execute your pipeline graph.
  • Host collectors (Linux, Windows, macOS) — The same praxis-collector stack runs as a system service (or Windows service) with a package or install script. See Linux, Windows, and macOS.
  • Praxis Gateway (optional) — A collector installation that also acts as a concentration point for OTLP, syslog, TCP, and UDP, then forwards to your export destinations. Not every installation needs it; the Praxis Gateway overview lists common drivers.

Before you start​

  • Prerequisites — For Kubernetes: cert-manager, the OpenTelemetry Operator, and kubectl. For Linux, Windows, or macOS: credentials and an artifact URL from Praxis (or your private registry), plus host-level permissions for your sources.
  • Network — Outbound access from collectors to your destinations (and to Praxis for control and, where used, for sign-in) must follow your security policy. The Gateway and TLS pages explain how to use mTLS and private endpoints for collector-to-Praxis-Gateway traffic.