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: expose metrics in internal tables for monitoring #29396
Comments
Tagging as pgcompat for now, since that's a relevant fit - feel free to retag if there's a better home. |
Ab other option would be to add a specific user for monitoring purposes. That user should be able to connect and read the tables/views required to be able to figure out the database structure, sizes, performance metrics and parameters. Maybe it should be able to describe tables, perform explain plans but it should not be able to read user data. |
Any news on this? In our current world, where privacy concerns are getting more attention, it would be a smart move to allow for definition of users that can perform their tasks without automatically having access to user data. For monitoring we don't need to read the user tables, as long as we can explain the plans. For backup/recovery we don't need to read the user tables, as long as we can recover the database... |
@ikzelf there are two separate issues:
Regarding point 2 - this is the main reason why we are not willing to support you on this issue. However, what we can do is the following:
How does this sound? |
That sounds good, great. Things I would like to be able to monitor is
This all is mostly aiming on resource and availability monitoring/alerting |
@piyush-singh @awoods187 @rolandcrosby can you capture the above requirements in the telemetry roadmap and cross-check what we already have in prometheus. I think the following should happen:
I think all of these can be put in metrics (i.e. not sql telemetry). |
We have marked this issue as stale because it has been inactive for |
v22.2 will support grants on virtual tables. I've renamed the issue to capture the request for being able to do monitoring by referencing internal tables, and moving this to the SQL Observability team. |
Request from user @ikzelf on the forum
Currently, CRDB only allows root access to crdb_internal. Root cannot grant permissions to other users. Ronald can comment further, but this is currently preventing him from implementing a monitoring solution using SQL, which he's implemented for Postgres, Mysql, and other databases.
Jira issue: CRDB-4870
The text was updated successfully, but these errors were encountered: