[exporter/prometheusremotewrite] WAL metrics

[ArthurSens]

Component(s)

exporter/prometheusremotewrite

Is your feature request related to a problem? Please describe.

It's a bit difficult to observe how well the Prometheus Remote Write exporter's WAL is performing while running in production

Describe the solution you'd like

It would be awesome if we had a few metrics to measure it's efficiency:

• Data throughput
• Write/Read success ratio
• Write/Read latency
• Pipeline lag

Describe alternatives you've considered

No response

Additional context

No response

[github-actions]

Pinging code owners:

• exporter/prometheusremotewrite: @Aneurysm9 @rapphil @dashpole @ArthurSens

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

Pinging code owners for exporter/prometheusremotewrite: @Aneurysm9 @rapphil @dashpole @ArthurSens. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[NickAnge]

Hey, I would like to work on this issue.

[ArthurSens]

Awesome, thanks @NickAnge! Feel free to ping us if you need help :)

[NickAnge]

Hey @ArthurSens . Its still in early stage, but I wanted to ask your opinion about the code structure. I followed a similar approach to the generated_telemetry.go. Created an interface to wrap wal telemetry functions, but I feel that I am changing the wal structure a lot (for example by adding exporter setting (here)).

The metric generation seems straightforward. I have added the Writes (Total/failures) as an example