Prometheus metrics & standby nodes

[Thomas St.]

I have successfully enabled the prometheus metrics endpoint

telemetry {
  prometheus_retention_time = "24h"
  disable_hostname = true
}

And I can scrape the metrics in prometheus by querying all running vault servers in the vault cluster (2 instances). Based on GitHub Comment I would expect to see the metrics for each vault server (one primary and one standby). But comparing the metrics it looks to me like the standby ones are just the primary ones. E.g. I would expect consul get, list, put and delete operations are 0 or much less on standby. It seems the metrics api call is forwarded to the primary node?

Do I miss anything?

Prometheus scrapes the metrics with provided vault http api endpoint "/sys/metrics".

Thanks for your help.

[Thomas St.]

I assume standby nodes cannot handle "sys/metrics" calls and they will forward the request to the active one (but I don't have an overview of the entire code). I am just wondering, if this is by intention? From monitoring perspective, I think this is not useful.

[Brian Kassouf]

Hey Thomas,

This is a good point and I don't think is intentional. Would you mind creating a github issue with the same information? 

Best,

Brian

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vault-tool+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vault-tool/093ab955-44d7-4d9d-96e1-720a88546d6e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Thomas St.]

Hey Brian,

Thanks for your comment - I created the issue 6802

Best Regards,

Thomas

On Wednesday, May 29, 2019 at 11:11:39 PM UTC+2, Brian Kassouf wrote:

Hey Thomas,

This is a good point and I don't think is intentional. Would you mind creating a github issue with the same information? 

Best,

Brian

On Wed, May 29, 2019 at 4:08 PM Thomas St. <thoma...@gmail.com> wrote:

I assume standby nodes cannot handle "sys/metrics" calls and they will forward the request to the active one (but I don't have an overview of the entire code). I am just wondering, if this is by intention? From monitoring perspective, I think this is not useful.

On Monday, May 27, 2019 at 4:47:05 PM UTC+2, Thomas St. wrote:

I have successfully enabled the prometheus metrics endpoint

telemetry {
  prometheus_retention_time = "24h"
  disable_hostname = true
}

And I can scrape the metrics in prometheus by querying all running vault servers in the vault cluster (2 instances). Based on GitHub Comment I would expect to see the metrics for each vault server (one primary and one standby). But comparing the metrics it looks to me like the standby ones are just the primary ones. E.g. I would expect consul get, list, put and delete operations are 0 or much less on standby. It seems the metrics api call is forwarded to the primary node?

Do I miss anything?

Prometheus scrapes the metrics with provided vault http api endpoint "/sys/metrics".

Thanks for your help.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/hashicorp/vault/issues
IRC: #vault-tool on Freenode
---
You received this message because you are subscribed to the Google Groups "Vault" group.

To unsubscribe from this group and stop receiving emails from it, send an email to vault...@googlegroups.com.