Vtgate metrics: Added plan and query type metrics#17727
Vtgate metrics: Added plan and query type metrics#17727harshit-gangal merged 22 commits intovitessio:mainfrom
Conversation
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Review ChecklistHello reviewers! 👋 Please follow this checklist when reviewing this Pull Request. General
Tests
Documentation
New flags
If a workflow is added or modified:
Backward compatibility
|
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #17727 +/- ##
==========================================
+ Coverage 67.45% 67.52% +0.06%
==========================================
Files 1594 1594
Lines 259064 259472 +408
==========================================
+ Hits 174760 175211 +451
+ Misses 84304 84261 -43 ☔ View full report in Codecov by Sentry. |
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
…st for metrics Signed-off-by: Harshit Gangal <harshit@planetscale.com>
…nd using lookup vindex as lookup plan type Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
|
Website Doc PR: vitessio/website#1935 |
|
I understand that we can't re-use QueriesProcessed and QueriesRouted, because that might break people's dashboards, but we need to come up with some other names for QueryProcessed and QueryRouted which are grammatical. Leaving this comment as a place-holder while I try to think of alternatives. |
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Andres Taylor <andres@planetscale.com>
Signed-off-by: Andres Taylor <andres@planetscale.com>
Here are my suggestions
|
Count is self-explanatory, as it already implies a counter. Using Counts looks redundant in this context. |
| const ( | ||
| PlanUnknown PlanType = iota | ||
| PlanLocal | ||
| PlanPassthrough | ||
| PlanMultiShard | ||
| PlanLookup | ||
| PlanScatter | ||
| PlanJoinOp | ||
| PlanForeignKey | ||
| PlanComplex | ||
| PlanOnlineDDL | ||
| PlanDirectDDL | ||
| PlanTransaction | ||
| PlanTopoOp | ||
| ) |
There was a problem hiding this comment.
It could be good to have a link to the docs here as a comment (https://github.com/vitessio/website/pull/1935/files#diff-4badcfb66b7411dea206a299af9b9f8e3d349d817ad332798f747b0b9a40ad9f), both to help us know what each value mean and also to remind us that modifying this list implies that we need to change the docs.
The problem is that we don't have any good options because |
| // TODO: @harshit/@systay - Remove these deprecated stats once we have a replacement in a released version. | ||
| queriesProcessed = stats.NewCountersWithSingleLabel("QueriesProcessed", "Deprecated: Queries processed at vtgate by plan type", "Plan") | ||
| queriesRouted = stats.NewCountersWithSingleLabel("QueriesRouted", "Deprecated: Queries routed from vtgate to vttablet by plan type", "Plan") | ||
| queriesProcessedByTable = stats.NewCountersWithMultiLabels("QueriesProcessedByTable", "Deprecated: Queries processed at vtgate by plan type, keyspace and table", []string{"Plan", "Keyspace", "Table"}) |
There was a problem hiding this comment.
We seem to be dropping the table metrics. Can we add that as a dimension to the new metrics? They have been useful in the past in debugging production issues.
There was a problem hiding this comment.
I have added QueryTables as replacement metric for it.
changelog/22.0/22.0.0/summary.md
Outdated
| 2. QueryRouted - This counts the number of shards the query was executed on. | ||
|
|
||
| Deprecated: | ||
| 1. QueriesProcessed |
There was a problem hiding this comment.
In code you are deprecating the table metrics, but that is missing from here.
There was a problem hiding this comment.
I have added QueryTables as replacement metric and updated the summary notes.
changelog/22.0/22.0.0/summary.md
Outdated
| ### <a id="vtgate-metrics"/>VTGate Metrics | ||
|
|
||
| Added two new metrics for queries with query type, plan type and tablet type as dimension. | ||
| 1. QueryProcessed - This counts the number of query executed. |
There was a problem hiding this comment.
| 1. QueryProcessed - This counts the number of query executed. | |
| 1. QueryProcessed - This counts the number of queries processed by this vtgate. |
There was a problem hiding this comment.
I am not sure if adding this VTGate helps.
Any time-series database will accumulate data from all VTGates and show a single view.
However, users can add instance as a dimension to view it on a per-VTGate basis.
The metrics themselves are collected at a single-process level.
changelog/22.0/22.0.0/summary.md
Outdated
|
|
||
| Added two new metrics for queries with query type, plan type and tablet type as dimension. | ||
| 1. QueryProcessed - This counts the number of query executed. | ||
| 2. QueryRouted - This counts the number of shards the query was executed on. |
There was a problem hiding this comment.
This says shards but the actual description of the metric says "routed to vttablets". Which one is it?
There was a problem hiding this comment.
For this metric, ‘shards’ and ‘vttablets’ are effectively similar in meaning. A query is routed to either the primary or a replica of a shard, but not both.
There was a problem hiding this comment.
I have updated it.
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
60bebfc to
72c561a
Compare
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
dca525e to
30a5c69
Compare
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Signed-off-by: Harshit Gangal <harshit@planetscale.com>
Description
This PR adds classification of query plans based on their execution strategy.
Additionally, it deprecates four metrics and introduces three replacements.
The Queries metric counter, which tracks queries processed at VTGate, will be published with Query, Plan, and Tablet type labels. This improves observability into query distribution and execution patterns.
Plan Classification
Query plans are categorized into different types based on their execution behavior:
Local– Queries executed locally on VTGate without involving any shard.Passthrough– Queries forwarded to single shard without having any additional processing at VTGate.MultiShard– Queries executed across multiple shards with controlled routing.Lookup– Queries using lookup vindexes to resolve keyspace IDs efficiently and route to specific shards.Scatter– Queries broadcast to all shards.JoinOp– Queries involving join operations across multiple shards, with Join on VTGate.ForeignKey– Queries handling foreign key constraints, such as cascades and validations.Complex– Queries with intricate execution logic requiring VTGate to process results.OnlineDDL– DDLs executed though Online Schema change workflow.DirectDDL– DDLs directly executed on the shards.Transaction– Queries managing transactions, including BEGIN, COMMIT, ROLLBACK, and SAVEPOINT.Topology- Queries that involves accessing Topology Server for Get/Put.Published Metrics
Sample metrics from VTGate's
/metricspath:Related Issue(s)
Checklist