Observability Pipelines

FlowPort
Observability Pipelines

Send the data you need to the tools that need it. Filter unnecessary records, add useful context and route logs, metrics and traces before they reach downstream platforms—all while keeping your existing collectors.

Collect · Process · Route · Deliver

Decide what moves downstream before you store and analyse it

Put parsing, filtering and routing between your sources and destinations. Manage the data path in one place, validate changes with samples and follow delivery through to its destination.

Bring existing sources together without replacing your collectors

Connect application and infrastructure telemetry through HTTP, OTLP, DataKit, Remote Write and other supported inputs. Configure the source, processing steps and destinations as one data flow.

Send data to Guance or other analysis and storage systems. Choose the input and output protocols that support the signals your team needs.
View documentation

Connect the data sources you already use

Choose inputs for telemetry, message queues and database changes. Explore a selection of native data sources below.

72Native source types 48Native destination types

Protocols & collectors

Messaging & event streams

Cloud logs

Database CDC

Object storage

Network & audit

Remove unnecessary data and add context before it reaches storage

Build parsing, conversion, filtering and tag enrichment in the visual editor or Platypus source view. Check the result against sample records before publishing the data flow.

Use Lookup to add service ownership, business priority or other context from synced reference data. Workers query a local snapshot, so processing does not need a remote lookup for every event.
View documentation

Route each data stream to the destinations that need it

Combine AND / OR conditions on processed tags to direct data by service, environment or priority. Rules are evaluated in order, with unmatched records sent to the configured default destination group.

Deliver the same data to multiple targets when needed. Each target has its own persistent delivery branch and retry state, so a failed target does not require successful deliveries to be sent again.
View documentation

See where delivery slows down—and which stage needs attention

Inspect received and delivered data, stage failures, queue backlog and diagnostics from the runtime overview. Export Prometheus metrics to track pipeline health in your existing monitoring tools.

Local persistent queues buffer data when a destination is temporarily unavailable, while independent branches retry with backoff. Configure queue capacity for your expected throughput and disk budget, and monitor backlog and eviction.
View documentation

Frequently asked questions

How does FlowPort work with existing collectors?

Collectors gather data from applications, hosts and services. FlowPort receives supported inputs from those collectors, applies processing and routing rules, and delivers the result to the destinations you configure.

Where can I deploy FlowPort?

FlowPort runs independently on Linux ARM64 or x86_64, with deb, rpm and tar packages available. The community edition supports one local Worker. Remote Workers and task assignment require a commercial distribution and an offline license.

What happens when one destination is unavailable?

Each destination has an independent persistent delivery branch and retry state. Other destinations can continue receiving data while the failed branch retries. Size local queues for your throughput and available disk space, and monitor capacity limits.

How do I send data to Guance?

Add a Guance destination with your DataWay address and workspace token. Select a source, configure Pipeline processing and routing, then publish the flow. Check Worker status and the data received downstream to verify delivery.

Take control of your telemetry