To ensure compatibility with the newer version of Prometheus, we need to include the Content-Type header in the response. Without this header, Prometheus may mark the node as unavailable, resulting in missed counter recordings. Adding the Content-Type will guarantee proper metric collection and prevent nodes from being incorrectly flagged as down.
Originally posted by @rahulrawat31r in aab6e8a
Add the Content-Type header to the metrics response to ensure compatibility with newer versions of Prometheus. Without this header, Prometheus may mark the node as down and fail to record counters.
Impact
Prevents nodes from being incorrectly flagged as unavailable
Ensures counters are consistently recorded
Improves reliability of monitoring setup
Support
I can help with implementing this change and ensuring the response complies with Prometheus requirements.
Originally posted by @rahulrawat31r in aab6e8a
Add the Content-Type header to the metrics response to ensure compatibility with newer versions of Prometheus. Without this header, Prometheus may mark the node as down and fail to record counters.
Impact
Prevents nodes from being incorrectly flagged as unavailable
Ensures counters are consistently recorded
Improves reliability of monitoring setup
Support
I can help with implementing this change and ensuring the response complies with Prometheus requirements.