--
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/b61afd9e-23cc-4d70-86a1-ca737a9b9d48%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Rohit,That is exactly right! The barrier operations are the raw internal read/writes, while the consul ones reflect those that missed the read cache.
Best Regards,Armon DadgarOn September 7, 2017 at 9:40:20 PM, ~Rohit Koul (rohit...@gmail.com) wrote:
@All,--Wondering if someone could explain a bit more about barrier metrics. What exactly are these?I am running a 3 vault cluster with 3 node consul backend. My understanding of difference between things like vault.consul.get and vault.barrier.get was that barrier.gets is going to include the hits to the vault read cache - because those don't make a get request to the consul backend.Is that a correct way to look at the barrier metrics?Thanks
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+unsubscribe@googlegroups.com.