Final Lab: Production pipeline managed as code

What you will learn in this TP

• Deploy a gateway
• Export and version configurations
• Rebuild the environment with the CLI

Introduction #

What you will learn in this section

• Deploy a gateway
• Export and version configurations
• Rebuild the environment with the CLI

Context. Management wants a reproducible pipeline: everything built in the UI must be versioned and recreatable on a new server.

Prerequisites: Labs 1 to 4 completed, Git  ·  Estimated time: 60 min

A reproducible Bindplane pipeline.

Hands-on #

Guided steps, with their solution.

1. 1. Add a gateway

   Why? Edge collectors send to the gateway, the only one that knows the destinations.

   Start a bdot-gw collector with the role=gateway label and a Gateway-role configuration: OTLP source, sink and sink-archive destinations.

2. 2. Route

   Why? Only error logs must go to the alerting tool.

   In the gateway, add routing: level=ERROR to sink, everything to sink-archive.

3. 3. Export to Git

   Why? Code becomes the source of truth.

   Export every configuration as YAML and commit them.

4. 4. Rebuild on a new server

   Why? A recovery plan has to be tested.

   Delete the PostgreSQL volume, restart the server, re-apply the configurations and restart the rollouts.

5. 5. Wrap-up

   Why? A production pipeline fits on one page.

   Draw a diagram: collectors, gateway, destinations, measured throughput, and what happens if the Bindplane server goes down.

Difficulty level : ●●●●○ (4/5)