-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
Add contention graphs and open sql connections to metrics page in CC #73566
Comments
Writing up a quick update here, CRDB currently doesn't emit the second However, emitting the transaction contention metrics is currently blocked by a bug (#78675). (this is either a bug within a the trace analyzer or vectorized stats collector, still investigating). |
Thanks for updating the thread @Azhng. I added the 3 Connection metrics as well which came up in a couple threads. They should be already available but if not, let me know and we can create a separate issue. |
I think the |
Related to cockroachdb#73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections.
Related to cockroachdb#73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections.
Related to cockroachdb#73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections.
79175: sql: collect contention stats for sql stats when tracing is enabled r=yuzefovich a=Azhng Resolves #78675 Previously, contention stats was not collected for SQL Stats even when tracing was enabled. This was caused by two bugs: 1. instrumentationHelper skipping analyzing traces when tracing is enabled 2. transaction statistics ignore traces when tracing is turned on at the higher level. This commit ensures that contention stats is collected when tracing is turned on. Release note (bug fix): Contention statistics are now being collected for SQL Stats when tracing is enabled. 79606: sql/pgwire: add sql.conn.failures metric r=maryliag a=Azhng Related to #73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections. 79670: Updates to restore & backup sql diagrams r=ericharmeling a=kathancox Release note: None 79772: ui: fix raft messages graph r=Santamaura a=Santamaura Previously, when a user attempted to drag-to-zoom on the graph or use the date picker it would not work properly. This is due to missing props that set the time window and the time scale. Therefore, this patch updates the props to include these in order to have the date picker and graph drag-to-zoom working again. resolves #79614 Release note (bug fix): Update props on the raft messages page to include functions to set the time window and time scale in order to fix date picker and drag-to-zoom functionality. Co-authored-by: Azhng <[email protected]> Co-authored-by: Kathryn Hancox <[email protected]> Co-authored-by: Santamaura <[email protected]>
Expose transaction contention metric for cockroachdb#73566. Release note (sql change): new sql.txn.contended.count metric exposes total number of transactions that experienced contentions.
@Azhng can you paste screenshots of the charts here? Adding @Annebirzin as FYI |
s.mov |
Oops the issue got closed by accident. |
Nice! I had a few nits (mostly copy updates): SQL Connection Latency
SQL Statement Latency
SQL Open Sessions
SQL Connection Attempts
Full Scans
Statement Errors
SQL Statement Contention
General
cc @kevin-v-ngo |
Expose transaction contention metric for cockroachdb#73566. Release note (sql change): new sql.txn.contended.count metric exposes total number of transactions that experienced contentions.
Expose transaction contention metric for cockroachdb#73566. Release note (sql change): new sql.txn.contended.count metric exposes total number of transactions that experienced contentions.
Related to #73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections.
Related to #73566 This commit adds the the new sql.conn.failures counter metric that reflects the number of failed SQL connections. Release note (sql change): the new sql.conn.failures counter metric shows number of failed SQL connections.
79176: sql: add sql.txn.contended.count metric r=Azhng a=Azhng Expose transaction contention metric for #73566. Release note (sql change): new sql.txn.contended.count metric exposes total number of transactions that experienced contentions. Co-authored-by: Azhng <[email protected]>
Expose transaction contention metric for cockroachdb#73566. Release note (sql change): new sql.txn.contended.count metric exposes total number of transactions that experienced contentions.
As per #69799, the metrics page with some preliminary graphs was created for CC serverless. The following metrics need to be surfaced and the graphs should be added to the metrics page:
Epic CC-5060
Jira issue: CRDB-11647
The text was updated successfully, but these errors were encountered: