Configuring tcp probes for blackbox-exporter

[IWWE]

Hello,

I'm having trouble understanding how to configure tcp probes to service ports other than http servers.

Can someone give me an example how to probe a ssh-port?

I already successfully configured prom to probe http servers via blackbox-exporter:

  - job_name: 'blackbox'
    metrics_path: /probe
    params:
      module: [http_2xx]  # Look for a HTTP 200 response.
    static_configs:
      - targets:
        - https://example.com
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: blackbox-exporter:9115  # The blackbox exporter's real hostname:port.

There is no example in the blackbox-exporter project how to configure other modules other than http_2xx. Also, although I understand golang quite well, I don't understand where that _2xx suffix comes from.

[Brian Brazil]

On 26 July 2018 at 08:48, IWWE <iwit...@webware-experts.de> wrote:

Hello,

I'm having trouble understanding how to configure tcp probes to service ports other than http servers.

Can someone give me an example how to probe a ssh-port?

https://www.robustperception.io/checking-if-ssh-is-responding-with-prometheus has an example.

 

I already successfully configured prom to probe http servers via blackbox-exporter:

  - job_name: 'blackbox'
    metrics_path: /probe
    params:
      module: [http_2xx]  # Look for a HTTP 200 response.
    static_configs:
      - targets:
        - https://example.com
    relabel_configs:
      - source_labels: [__address__]
        target_label: __param_target
      - source_labels: [__param_target]
        target_label: instance
      - target_label: __address__
        replacement: blackbox-exporter:9115  # The blackbox exporter's real hostname:port.

There is no example in the blackbox-exporter project how to configure other modules other than http_2xx. Also, although I understand golang quite well, I don't understand where that _2xx suffix comes from.

http_2xx is an opaque string, it's the name of a module configured in the blackbox exporter's config file.

--

Brian Brazil

www.robustperception.io

[IWWE]

Thanks Brian, I think I understand it a little bit more now.

[jonny...@gmail.com]

I'm having a trouble with Prometheus and blackbox-exporter integration. That's my situation: I have a blackbox-exporter deployed in an AWS cluster [service name: blackbox; namespace: kube-system] and also a Prometheus [service name: prometheus; namespace: kube-system]. I've configured Prometheus very much like you:

- job_name: blackbox-endpoints

      params:

        module:

        - http_2xx

      scrape_interval: 1m

      scrape_timeout: 10s

      metrics_path: /probe

      scheme: http

      file_sd_configs:

      - files:

        - /etc/blackbox-endpoints/*.yml

        refresh_interval: 1m

      relabel_configs:

        - source_labels: [__address__]

          target_label: __param_target

        - source_labels: [__param_target]

          target_label: instance

        - target_label: __address__

          replacement: blackbox.kube-system:9115

But when and ran my Prometheus it doesn't show the blackbox-endpoints job. Is it necessary any other configuration to do it works?

[IWWE]

First, check if prometheus sucesfully loaded the configuration file then check if the exporter blackbox.kube-system is reachable on port 9155 from your prometheus instance.

Does the exporter show up in your prometheues targets?

[Jonnys Gomes]

First, check if prometheus sucesfully loaded the configuration file then check if the exporter blackbox.kube-system is reachable on port 9155 from your prometheus instance.

Yes, the configuration file is loaded. I'm able to see it on Prometheus UI > Status > Configuration. And also, the blackbox is running and reachable on 9115. I'm able to enter into Prometheus Pod and do ' wget blackbox.kube-system:9115 ' with success.

Does the exporter show up in your prometheues targets?

No, and that's the problem. I do not understand why.

--
You received this message because you are subscribed to a topic in the Google Groups "Prometheus Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/prometheus-users/Je5BfIHc1ZI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to prometheus-use...@googlegroups.com.
To post to this group, send email to promethe...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/prometheus-users/cb6af363-1ad5-4256-8a7e-e15b01c5f051%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Atenciosamente,

Jonnys Gomes.

[jonny...@gmail.com]

First, check if prometheus sucesfully loaded the configuration file then check if the exporter blackbox.kube-system is reachable on port 9155 from your prometheus instance.

Yes, the configuration file is loaded. I'm able to see it on Prometheus UI > Status > Configuration. And also, the blackbox is running and reachable on 9115. I'm able to enter into Prometheus Pod and do ' wget blackbox.kube-system:9115 ' with success.

Does the exporter show up in your prometheues targets?

No, and that's the problem. I do not understand why.

[IWWE]

The target not showing up seems strange. Could be something with the kube system.

Sorry, I don't have any more ideas.

[jonny...@gmail.com]

It worked for me using the configuration for Blackbox Exporter in this link. Thanks anyway.