added alerts for jaeger 2.x

[danish9039]

Which problem is this PR solving?

• [Bug]: prometheus_alerts.yml for jaeger 2.X #6820

Description of the changes

• add alerts for jaeger 2.x

How was this change tested?

Checklist

• I have read https://github.com/jaegertracing/jaeger/blob/master/CONTRIBUTING_GUIDELINES.md
• I have signed all commits
• I have added unit tests for the new functionality
• I have run lint and test steps successfully
  • for jaeger: make lint test
  • for jaeger-ui: npm run lint and npm run test

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.04%. Comparing base (712c1bc) to head (478f0aa).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #6854      +/-   ##
==========================================
+ Coverage   96.03%   96.04%   +0.01%     
==========================================
  Files         367      367              
  Lines       20831    20831              
==========================================
+ Hits        20005    20008       +3     
+ Misses        630      628       -2     
+ Partials      196      195       -1     

Flag	Coverage Δ
badger_v1	9.88% <ø> (ø)
badger_v2	2.05% <ø> (ø)
cassandra-4.x-v1-manual	14.87% <ø> (ø)
cassandra-4.x-v2-auto	2.04% <ø> (ø)
cassandra-4.x-v2-manual	2.04% <ø> (ø)
cassandra-5.x-v1-manual	14.87% <ø> (ø)
cassandra-5.x-v2-auto	2.04% <ø> (ø)
cassandra-5.x-v2-manual	2.04% <ø> (ø)
elasticsearch-6.x-v1	19.55% <ø> (ø)
elasticsearch-7.x-v1	19.62% <ø> (ø)
elasticsearch-8.x-v1	19.79% <ø> (ø)
elasticsearch-8.x-v2	2.05% <ø> (ø)
grpc_v1	10.92% <ø> (ø)
grpc_v2	7.98% <ø> (ø)
kafka-3.x-v1	10.18% <ø> (ø)
kafka-3.x-v2	2.05% <ø> (ø)
memory_v2	2.05% <ø> (ø)
opensearch-1.x-v1	19.67% <ø> (ø)
opensearch-2.x-v1	19.67% <ø> (ø)
opensearch-2.x-v2	2.05% <ø> (ø)
tailsampling-processor	0.55% <ø> (ø)
unittests	94.92% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[yurishkuro]

how can this be tested / validated?

[danish9039]

how can this be tested / validated?

i have tested this in my local machine by setting up jaeger v2 and opentelemetry collector and scrap it using prometheus , while runing a testing application for producing matrices and simulating scenarios , at first i investigated available metrices by curl http://127.0.0.1:8888/metrics , then i checked the all rules are visible in prometheus ui , then i created different scenarios and checked if the alerts where firing

[yurishkuro]

Thanks. It's good that you did manual testing, but as soon as some metric changes this file becomes invalid. How can it be tested automatically?