Service monitor scrap tempo metrics for monolithic

[rubenvp8510]

No description provided.

[codecov-commenter]

Codecov Report

❌ Patch coverage is 21.58273% with 218 lines in your changes missing coverage. Please review.
✅ Project coverage is 56.01%. Comparing base (0b0e615) to head (ea76497).
⚠️ Report is 20 commits behind head on main.

Files with missing lines	Patch %	Lines
internal/manifests/monolithic/certificates.go	0.00%	63 Missing ⚠️
...roller/tempo/certrotation_monolithic_controller.go	0.00%	55 Missing ⚠️
internal/manifests/monolithic/statefulset.go	13.88%	29 Missing and 2 partials ⚠️
...al/certrotation/handlers/certrotation_discovery.go	0.00%	21 Missing ⚠️
internal/manifests/monolithic/configmap.go	16.66%	19 Missing and 1 partial ⚠️
cmd/start/main.go	0.00%	8 Missing ⚠️
...nternal/certrotation/handlers/check_cert_expiry.go	0.00%	4 Missing ⚠️
internal/certrotation/var.go	20.00%	4 Missing ⚠️
internal/certrotation/handlers/options.go	0.00%	3 Missing ⚠️
internal/certrotation/handlers/rotate_certs.go	0.00%	3 Missing ⚠️
... and 2 more

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1274      +/-   ##
==========================================
- Coverage   57.64%   56.01%   -1.64%     
==========================================
  Files         121      125       +4     
  Lines       11277    11709     +432     
==========================================
+ Hits         6501     6559      +58     
- Misses       4418     4800     +382     
+ Partials      358      350       -8     

Flag	Coverage Δ
unittests	56.01% <21.58%> (-1.64%)	⬇️

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.

[andreasgerstmayr]

Does the internal server serve metrics, or only the readiness probes?

internal_server:
    http_listen_address: ""

Otherwise everyone has access to the Tempo API and can circumvent the gateway. That means we have to setup mTLS between tempo and the gateway also for the monolithic, which is what I tried to avoid by using localhost here.

[rubenvp8510]

Unfortunately internal server doesn't expose the metrics :( We will need to protect it using mTLS which is something I also don't wanted

[andreasgerstmayr]

Where is this function being called?