promtool debug metrics https://myserver:8181
collecting: https://myserver:8181/metrics 2022/09/09 11:15:05 http2: Transport failed to get client conn for myserver:8181: http2: no cached connection was available error completing debug command: error executing HTTP request: Get "https://myserver:8181/metrics": EOF If I open the url in a browser or with curl I get proper response :( Any hint what I might be missing? testssl.sh works fine too On Friday, 9 September 2022 at 10:37:13 UTC+2 Markus Glück wrote: > Hi guys, > I currently trying to debug a similar issue. I am also getting EOF only as > error in debug level from scrape manager. I had the same issue locally with > curl and LibreSSL on macOS. Updating the curl version to use openSSL fixed > it. So my assumption it's something related to SSL/TLS. My working curl > verbose output gives me this in regards to TLS: > > * ALPN: offers h2 > > * ALPN: offers http/1.1 > > } [5 bytes data] > > * TLSv1.3 (OUT), TLS handshake, Client hello (1): > > } [512 bytes data] > > * TLSv1.3 (IN), TLS handshake, Server hello (2): > > { [193 bytes data] > > * TLSv1.3 (OUT), TLS change cipher, Change cipher spec (1): > > } [1 bytes data] > > * TLSv1.3 (OUT), TLS handshake, Client hello (1): > > } [512 bytes data] > > * TLSv1.3 (IN), TLS handshake, Server hello (2): > > { [155 bytes data] > > * TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8): > > { [51 bytes data] > > * TLSv1.3 (IN), TLS handshake, Certificate (11): > > { [4943 bytes data] > > * TLSv1.3 (IN), TLS handshake, CERT verify (15): > > { [520 bytes data] > > * TLSv1.3 (IN), TLS handshake, Finished (20): > > { [52 bytes data] > > * TLSv1.3 (OUT), TLS handshake, Finished (20): > > } [52 bytes data] > > * SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384 > > * ALPN: server accepted h2 > > > but HOW do I get more info from Prometheus? > > Thx, > > Markus > > On Thursday, 14 July 2022 at 16:25:36 UTC+2 Brian Candler wrote: > >> The straightforward way to debug this by doing a scrape by hand: it's >> just a HTTP request. >> >> curl -g 'https://blah.local:9126/metrics' >> >> Add flag '-v' for more debugging if required (e.g. response headers may >> give you an extra clue). Once you're able to scrape the exporter with >> curl, then prometheus should be able to talk to it too. >> >> Given that it's https, if you get a certificate error then you can add >> flag '-k' to skip certificate verification. If that turns out to be the >> problem, then there are extra flags you can pass to curl, e.g. to pass the >> CA root certificate (if the target's cert was signed by a CA that's not in >> the system trust store). Once you've got all that working, you can make >> the corresponding changes to prometheus' tls_config. >> >> On Thursday, 14 July 2022 at 14:46:24 UTC+1 [email protected] wrote: >> >>> Hello Team, >>> >>> I have promethus installed on kubernet and add scraping targets from >>> cmdb using http_sd_config. >>> >>> I am getting EOF error while i add targets. And it’s show down. >>> >>> Can someone please help me what is the issue. >>> >>> For your reference attached screenshot of error. >>> >>> Thanks and regards >>> Ritesh patel >>> >> -- You received this message because you are subscribed to the Google Groups "Prometheus Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/80662be7-bc52-4d34-960d-41ecca5b4ec6n%40googlegroups.com.
