Support port for "node" role under "kubernetes_sd_config"

[aerokite]

The node role discovers one target per cluster node with the address defaulting to the Kubelet's HTTP port.

If I have another service running on each node directly and exposes metrics on a particular port, what should I do?

If node role supports port, I can create another job to collect metrics with that port.

- job_name: 'kubernetes-node-metrics'
  kubernetes_sd_configs:
  - role: node
  port: 10240

Suppose, I have a service running on each node exposing metrics on port 10240. I can collect using your existing node role if you support port for kubernetes_sd_config.

[fabxc]

Generally, you would discover this with the endpoints discovery, which
doesn't care about on which node the endpoints run. The underlying
DaemonSet just makes it that way.

On Fri, Nov 18, 2016 at 9:39 AM Mir Shahriar Sabuj notifications@github.com
wrote:

The node role discovers one target per cluster node with the address
defaulting to the Kubelet's HTTP port.

If I have another service running on each node directly and exposes
metrics on a particular port, what should I do?

If node role supports port, I can create another job to collect metrics
with that port.

• job_name: 'kubernetes-node-metrics'
  kubernetes_sd_configs:
  • role: node
    port: 10240

Suppose, I have a service running on each node exposing metrics on port
10240. I can collect using your existing node role if you support that.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2199, or mute the thread
https://github.com/notifications/unsubscribe-auth/AEuA8mXwaUFPRw0JO5MdA7-MkxQAdgqLks5q_WRJgaJpZM4K2PV6
.

[lock]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.