Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dump info about ssl.cachesize usage #1181

Open
rfrail3 opened this issue Mar 12, 2021 · 1 comment
Open

Dump info about ssl.cachesize usage #1181

rfrail3 opened this issue Mar 12, 2021 · 1 comment
Labels
type: feature This issue describes a feature request / wishlist.

Comments

@rfrail3
Copy link

rfrail3 commented Mar 12, 2021

What should haproxy do differently? Which functionality do you think we should add?

Via configuration file you can set the ssl.cachesize, but it isn't possible to know the current usage.
It would be nice to have a new line on "show info" with that information, for example, in combination with the current two SslCahe entries:

SslCacheLookups: 12669910
SslCacheMisses: 9994550
SslCacheUsage: 15766

Also commented in https://discourse.haproxy.org/t/check-usage-of-ssl-cachesize/6337

What are you trying to do?

Easily know the current ssl cache usage.

Output of haproxy -vv and uname -a

# haproxy -vv
HA-Proxy version 2.2.10-6a09215 2021/03/03 - https://haproxy.org/
@rfrail3 rfrail3 added the type: feature This issue describes a feature request / wishlist. label Mar 12, 2021
@rlebreton
Copy link
Contributor

The cache entries are not removed from the cache until we try to insert a new entry and the cache is full. So the cache is bound to be "full" after some time and it won't ever be emptied. This notion of cache usage would not mean much after the cache is full, it would almost always give a value close to your tune.ssl.cachesize.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature This issue describes a feature request / wishlist.
Projects
None yet
Development

No branches or pull requests

2 participants