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

sql: separate metrics pages by APP and Database #55861

Closed
awoods187 opened this issue Oct 22, 2020 · 2 comments
Closed

sql: separate metrics pages by APP and Database #55861

awoods187 opened this issue Oct 22, 2020 · 2 comments
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-queries SQL Queries Team

Comments

@awoods187
Copy link
Contributor

awoods187 commented Oct 22, 2020

Currently, you can separate the Transactions and Statements by App but not by database (#33316).

Customers are also interested in being able to separate the metrics pages by App and by Database. This is an issue to track that request.

gz#5514

Jira issue: CRDB-3622

@awoods187 awoods187 added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Oct 22, 2020
@jordanlewis
Copy link
Member

We don't have an easy path to making this happen today. We'd need to add "dynamic" time series metrics that are scoped by app. We would probably not want to make this automatically happen for all apps and databases, because time series data doesn't like to have "dynamic dimensions" the way this is.

We could conceivably have a cluster setting that includes the desired set of apps and databases to record timeseries for, but I'm concerned about performance implications here.

I would urge users to solve this problem themselves, by adding their own latency and throughput metrics per app in the application. This is standard practice for observability for microservice architectures, and I'm not sure what customers can't get using this standard practice.

Andy, could you please determine which metrics the customer needs bucketed by app and database, and why the standard practice I suggested is insufficient?

@jlinder jlinder added the T-sql-queries SQL Queries Team label Jun 16, 2021
@maryliag
Copy link
Contributor

maryliag commented Nov 3, 2023

No longer a priority

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-sql-queries SQL Queries Team
Projects
None yet
Development

No branches or pull requests

4 participants