In most situations, you will have several sources of telemetry data that you want to send to multiple destinations, such as storage locations and observability tools. In turn, the data that you are sending needs to be optimized for its specific destination. If your data contains Personally Identifying Information (PII) for example, this data will need to be redacted or encrypted before reaching its destination.
While you could create a single telemetry pipeline for each source and destination, along with the required processors, this is impractical and would quickly result in overly-complex data management requirements. A better solution is to send all the data from multiple sources to multiple destinations through a single pipeline, and use a Route Processor to send specific data through specialized processing chains. This interactive demo illustrates how three diversely different types of data can be routed through pipeline branches to reach shared and specific destinations.
For more information on how you can build a version of this Pipette and experiment with your own source data, check out our tutorial Pipeline Module: Route at docs.mezmo.com.
Similar blog posts
