Hello Izabela,
Thank you for your help.
No. I didn't succeed to scrap a prometheus exporter through "Full" SSL with DT. I succeeded with Prometheus to use TLS authentication, but not with DT. Anyway, I disabled the Certificate validation check with the following annotation:
metrics.dynatrace.com/insecure_skip_verify: "true"
That's ok for the moment. But if you succeded to create the right configmap or secret and the annoations in DT, I would be pleased to see how you have done.
I'm facing the same kind of issue when instead of using tls and certificate to scrape a prometheus exporter => When I have to use a bearer_token to authenticate on the prometheus exporter. . I've not found a DT annotation to add in the HTTP request Header: Authorization: Bearer<token>. A token is needed for instance to scrape sonarqube exporter on port 9000. It works fine with prometheus by using the following key value:
bearer_token: <token> in the prometheus yaml config or in the ServiceMonitor => but an annotation like the following don't work either with DT:
metrics.dynatrace.com/{bearer_token, bearerToken, token} : <token>
Here is the URL describing the sonaqube API monitoring via Prometheus with a token used in the HTTP header of the request:
https://dev.irpteam.com/sq/documentation/instance-administration/monitoring/
