Failure metrics should include links to issues/tickets we collect from, as well as a Title or Description of the issue for better traceability

[etsauer]

Feature description

When I look at our current failure metrics, it's difficult for me to tell where the metric came from.

failure_resolution_timestamp{app="basic-nginx",endpoint="http",instance="10.129.1.140:8080",issue_number="MDT-6",job="failure-exporter",namespace="sdp-byapp-dashboard",pod="failure-exporter-4-c8pct",service="failure-exporter"}

I would like to see this data enriched so that I can get back to the issue or ticket that was captured, and also see a little bit more info about it, like a title or description. This is what I would propose

failure_resolution_timestamp{app="basic-nginx",endpoint="http",instance="10.129.1.140:8080",issue_number="MDT-6",issue_link="https://github.com/dora-metrics/pelorus/issues/1097", issue_title="There's a production outage with our application", job="failure-exporter",namespace="sdp-byapp-dashboard",pod="failure-exporter-4-c8pct",service="failure-exporter"}

How this will help you

This will improve users ability to validate the metrics we collect, learn how pelorus works, and increase trust in and adoption of the tool.

Feature priority

⌛ It will greatly improve my experience using Pelorus

Code of Conduct

• I agree to follow Pelorus's Code of Conduct