https://github.com/petems/vector-reduce-prometheus-tags-to-datadog-metrics

https://github.com/petems/vector-reduce-prometheus-tags-to-datadog-metrics

Last synced: 1 day ago
JSON representation

• Host: GitHub
• URL: https://github.com/petems/vector-reduce-prometheus-tags-to-datadog-metrics
• Owner: petems
• Created: 2023-08-16T15:22:28.000Z (about 1 year ago)
• Default Branch: master
• Last Pushed: 2023-08-16T19:04:26.000Z (about 1 year ago)
• Last Synced: 2024-07-02T10:07:16.083Z (3 months ago)
• Homepage:
• Size: 1000 Bytes
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# vector-reduce-prometheus-tags-to-datadog-metrics

## What is this?

A sandbox/lab repo for showing how Vector can remove tags and reduce tag cardinality from a Prometheus endpoint

## Why?

Promtheus metrics can have a very high tag cardinality. Custom metrics sent to Datadog are charged on complexity, and a high tag cardinality can bring additional costs.

## How?

In this demo, Vector is running a simple topology in which the `prometheus` source fetches a promtheus metircs from an app that generates random Prometheus data (https://github.com/little-angry-clouds/prometheus-data-generator)

We then run one of two transforms to reduce tag cardinality:

Removing a tag completely:

```toml

[transforms.remove_tag.hooks]

  process = """

function (event, emit)

\t-- Remove tag

\tevent.metric.tags.tag_to_remove = "remove_me"

\temit(event)

end"""

```

Setting a tag cardinality limit

```toml

[transforms.reduce_cardinality]

type = "tag_cardinality_limit"

inputs = [ "remove_tag" ]

mode = 'exact'

[transforms.reduce_cardinality.fields]

value_limit = 2

limit_exceeded_action = "drop_tag"

```

To run this scenario, make sure you have the `DD_API_KEY` environment variable set to your Datadog

API key and then run:

```bash

$ docker compose up

```