Skip to content

Conversation

@Daksh-10
Copy link

@Daksh-10 Daksh-10 commented Aug 13, 2025

Solves #1394

The changes increment the counter after checking if a cached query is sent upstream due to it being in a transaction.

Screenshot from 2025-08-13 18-12-13

The metric is exposed on http://127.0.0.1:6033/metrics

1. Create cache from Select * from tb1 where ID=1;
2.  Select * from tb1 where ID=1; (counter will not be updated)
3. Start transaction;
4. Select * from tb1 where ID=1; (counter will be updated)

@Daksh-10
Copy link
Author

Hi @altmannmarcelo,
I updated the PR. What are your thoughts?

@Daksh-10 Daksh-10 changed the title metric: counter for cached queries in transaction metric: counter for cached queries executed in transaction Aug 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant