How to check Credential Application availability using Blackbox

[karthick MJ]

Hello Team,

I have been setting up prometheus monitoring for my company.  Recently I have been facing some trouble to monitor some applications which all have credentials. If I put the application URL as an end point along it stating the application is down,whereas it is actually up & running. 

How/where should I pass the credentials to monitor such application availability? 

It would be very grateful if I could get a solution to my concern as I'm new to Prometheus who struggling here and there. 

Regards & Thanks

Karthick Jaysankar 

[Stuart Clark]

Each authenticated endpoint (or set if they share the same credentials) would have a job within the Prometheus configuration file. You can then set those credentials (for example supplying a username and password for basic auth).

--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

[karthick MJ]

Team, 

Any assistance with my issue.. 

Thanks

Karthick 

On Mon, Aug 23, 2021 at 5:18 PM karthick MJ <karthic...@gmail.com> wrote:

Hi,

Thanks its works.. I have configured one credential application which stating "probe_http_status_code 401" error. Can you please let me know how to ignore certificate error / http error.  

# HELP probe_dns_lookup_time_seconds Returns the time taken for probe dns lookup in seconds
# TYPE probe_dns_lookup_time_seconds gauge
probe_dns_lookup_time_seconds 0.001877078
# HELP probe_duration_seconds Returns how long the probe took to complete in seconds
# TYPE probe_duration_seconds gauge
probe_duration_seconds 0.024474061
# HELP probe_failed_due_to_regex Indicates if probe failed due to regex
# TYPE probe_failed_due_to_regex gauge
probe_failed_due_to_regex 0
# HELP probe_http_content_length Length of http content response
# TYPE probe_http_content_length gauge
probe_http_content_length 1293
# HELP probe_http_duration_seconds Duration of http request by phase, summed over all redirects
# TYPE probe_http_duration_seconds gauge
probe_http_duration_seconds{phase="connect"} 0.0011588
probe_http_duration_seconds{phase="processing"} 0.00169862
probe_http_duration_seconds{phase="resolve"} 0.001877078
probe_http_duration_seconds{phase="tls"} 0.019060778
probe_http_duration_seconds{phase="transfer"} 0.000186192
# HELP probe_http_redirects The number of redirects
# TYPE probe_http_redirects gauge
probe_http_redirects 0
# HELP probe_http_ssl Indicates if SSL was used for the final redirect
# TYPE probe_http_ssl gauge
probe_http_ssl 1
# HELP probe_http_status_code Response HTTP status code
# TYPE probe_http_status_code gauge
probe_http_status_code 401
# HELP probe_http_uncompressed_body_length Length of uncompressed response body
# TYPE probe_http_uncompressed_body_length gauge
probe_http_uncompressed_body_length 1293
# HELP probe_http_version Returns the version of HTTP of the probe response
# TYPE probe_http_version gauge
probe_http_version 2
# HELP probe_ip_addr_hash Specifies the hash of IP address. It's useful to detect if the IP address changes.
# TYPE probe_ip_addr_hash gauge
probe_ip_addr_hash 3.82454287e+08
# HELP probe_ip_protocol Specifies whether probe ip protocol is IP4 or IP6
# TYPE probe_ip_protocol gauge
probe_ip_protocol 4
# HELP probe_ssl_earliest_cert_expiry Returns earliest SSL cert expiry in unixtime
# TYPE probe_ssl_earliest_cert_expiry gauge
probe_ssl_earliest_cert_expiry 1.65287162e+09
# HELP probe_ssl_last_chain_expiry_timestamp_seconds Returns last SSL chain expiry in timestamp seconds
# TYPE probe_ssl_last_chain_expiry_timestamp_seconds gauge
probe_ssl_last_chain_expiry_timestamp_seconds 1.65287162e+09
# HELP probe_ssl_last_chain_info Contains SSL leaf certificate information
# TYPE probe_ssl_last_chain_info gauge
probe_ssl_last_chain_info{fingerprint_sha256="0c4c0863eb28685e1f07148bef06b8a4e36aa6b4a287bc50ae95fe773ae29723"} 1
# HELP probe_success Displays whether or not the probe was a success
# TYPE probe_success gauge
probe_success 0
# HELP probe_tls_version_info Contains the TLS version used
# TYPE probe_tls_version_info gauge
probe_tls_version_info{version="TLS 1.2"} 

On Mon, Aug 23, 2021 at 1:07 PM karthick MJ <karthic...@gmail.com> wrote:

Hi,

Using 2.26.0 version. 

[ec2-user@i****** prometheus]$ ./prometheus --version
prometheus, version 2.26.0 (branch: HEAD, revision: 3cafc58827d1ebd1a67749f88be4                                                                                                             218f0bab3d8d)
  build user:       root@a67cafebe6d0
  build date:       20210331-11:56:23
  go version:       go1.16.2
  platform:         linux/amd64

On Mon, Aug 23, 2021 at 1:01 PM Stuart Clark <stuart...@jahingo.com> wrote:

On 2021-08-23 08:16, karthick MJ wrote:
> Hi,
>
> If I set those credentials under basic auth it throwing some error
> like below.
>
> [ec2-user@ip-********** prometheus]$ sudo ./promtool check config
> prometheus.yml
> Checking prometheus.yml
>   FAILED: parsing YAML file prometheus.yml: yaml: unmarshal errors:
>   line 12: cannot unmarshal !!seq into config.plain
>

Are you using the most recent version of Prometheus (2.29.1) or
something older?

--
Stuart Clark