Connecting Metrics
Now that you've configured all the Metrics Sources for this Sandbox, you'll modify the default prometheus_metrics
Pipeline to change a few metadata fields.
important
- On the Collect tab, hover over the blue plus button on the right side of the Kubernetes Metrics Source.
- Click the blue plus button. While holding down the mouse button, drag the connector to the Prometheus Destination and then release.
- In the Connection Configuration dialog, select Pipeline.
- The Add Pipeline to Connection dialog will appear.
- Click the prometheus_metrics link to open the Pipeline editor.
- Expand the Eval Function by clicking the number 2.
- Change the Value Expressions to the following:
Name | Value Expression |
---|---|
job | job || 'cribl' |
instance | __metadata.kube.node.metadata.name || host |
- Click Save.
- Click the X in the top right corner to close the Pipeline editor dialog.
- Select the radio button to the left of the prometheus_metrics pipeline.
- Click Save .
Connect the Prometheus Scraper Sources
Repeat the same connection for the two Prometheus Scraper sources.
important
- On the Collect tab, hover over the blue plus button on the right side of the cadvisor_metrics Source.
- Click the blue plus button. While holding down the mouse button, drag the connector to the Prometheus Destination and then release.
- In the Connection Configuration dialog, select Pipeline.
- The Add Pipeline to Connection dialog will appear.
- Select the radio button to the left of the prometheus_metrics Pipeline.
- Click Save.
Repeat the same process for the kubelet_metrics source.
important
- On the Collect tab, hover over the blue plus button on the right side of the kubelet_metrics Source.
- Click the blue plus button. While holding down the mouse button, drag the connector to the Prometheus Destination and then release.
- In the Connection Configuration dialog, select Pipeline.
- The Add Pipeline to Connection dialog will appear.
- Select the radio button to the left of the prometheus_metrics Pipeline.
- Click Save .
Next, let's wrap up our Cribl Edge configuration!