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

View cache Data in quarkus dev-ui (quarkus-cache) #37642

Closed
guyruisseau opened this issue Dec 10, 2023 · 6 comments · Fixed by #37660
Closed

View cache Data in quarkus dev-ui (quarkus-cache) #37642

guyruisseau opened this issue Dec 10, 2023 · 6 comments · Fixed by #37660
Milestone

Comments

@guyruisseau
Copy link

guyruisseau commented Dec 10, 2023

Description

Hi,

it is possible to visualize data cached from quarkus cache extension in the quarkus dev-ui ? I can visualiaze the count ouf elments but no the element cached. I found nothing about it in the documentation or i missed something...
I tried whith jVisualVm but I also found nothing

Thanks Guillaume

Implementation ideas

Visualize data cache in the dev-ui

Copy link

quarkus-bot bot commented Dec 10, 2023

/cc @cescoffier (devui), @gwenneg (cache), @phillip-kruger (devui)

@mkouba
Copy link
Contributor

mkouba commented Dec 11, 2023

I suppose that you want to show the cached keys and not the values, right?

@cescoffier
Copy link
Member

Because the values can be complex objects, I'm not sure we can display anything.
Keys - no problem.

@guyruisseau
Copy link
Author

The both :) But if you can't display value (as Json text for example), keys should be very usefull to start

@mkouba
Copy link
Contributor

mkouba commented Dec 11, 2023

Yes, I'm working on a PR for keys...

mkouba added a commit to mkouba/quarkus that referenced this issue Dec 11, 2023
@quarkus-bot quarkus-bot bot added this to the 3.7 - main milestone Dec 12, 2023
@guyruisseau
Copy link
Author

thank you, you are super efficient :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants