Getting started
These pages are written for teams using Praxis in their environments (operators, platform engineers, security staff, and developers automating against the product).
You use Praxis to move telemetry from where it is generated to where your team already works—SIEM, observability backends, object storage, and more—without rebuilding your stack around a new datastore. This documentation helps you choose integrations, install collectors close to your data, and automate with APIs when you are ready.
Most teams follow the same path: confirm the catalog supports your sources and destinations, design pipelines in the product, install collectors in your environment, then (optionally) drive changes from CI/CD or internal tools.
What to read first
| Topic | Why it matters for you |
|---|---|
| Overview, Pipelines, and Collectors | Where you spend time in the product: monitoring flow, designing graphs, and managing installed agents. |
| Integrations | What you can connect today—sources, processors, destinations—searchable by platform and signal type. |
| Installation overview | How to run collectors on Linux, Windows, macOS, Kubernetes, or behind a Praxis Gateway. |
| API overview | When and how to call Praxis over HTTP—auth, tenants, and where the full reference lives in this documentation. |
| Identity Management | Who can access what: orgs, tenants, users, invitations, API tokens, SSO. Identity Management maps to the idm RBAC app; pipeline features map to praxis—see the overview for how that shows up in APIs and tokens. |
A typical adoption path
- Discover — In Integrations, filter by your OS or platform and the signals you care about (logs, metrics, traces).
- Design — In the Praxis UI, build pipelines from those building blocks. Walk through every supported flow in Create a Pipeline. This documentation is the field-level reference for each integration; authoring still happens in the product.
- Install — Install collectors where your data lives, using the Installation overview so they enroll cleanly and receive published configuration.
- Automate (optional) — Use HTTP APIs for pipelines, collectors, and related objects when scripts or services should own change management.
Key terms (short)
- Management plane — Where you sign in, design pipelines, store credentials, and view operational summaries. It is not your long-term telemetry store; data lands in the destinations you pick per pipeline.
- Collector — Software that runs near your sources, receives pipeline configuration from Praxis, and forwards or processes telemetry using OpenTelemetry and other supported protocols.
- Pipeline — The path you define: sources → optional processors → destinations, executed on your collectors (and gateway tier, if you use one).
Next
Browse Integrations, or jump to the Installation overview if you already know what you want to connect.