You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 22, 2024. It is now read-only.
postgres_statements_query_info may be really, really long. this can lead to a problem, that victoria/ptometheus wouldn't scrape any data from exporter because of timeout or metrics length. Anyway, nobody cares about full query, usually we take a little bit from beginning to make further discussion or grep by source code. It would be wonderfull if we could set a size of query label in postgres_statements_query_info metric, i.e. first 100 symbols or bytes. Thanks!
The text was updated successfully, but these errors were encountered:
bykvaadm
changed the title
Support of cutting statements from pg_stat_statements
Support of limiting query label size from postgres_statements_query_info metric
Oct 27, 2021
bykvaadm
changed the title
Support of limiting query label size from postgres_statements_query_info metric
Support of limiting size of query label from postgres_statements_query_info metric
Oct 27, 2021
@glushakov@bykvaadm you can use no_track_mode feature to disable whole query text in metrics. Environment variable named PGSCV_NO_TRACK_MODE is available for this purpose.
I also think that we can limit it. the not_track_mode just remove the query and use the queryId. Is there anyway to lookup the queryId later and access the actual query? If not, I think limiting the actual query maybe to 255 char could be enough for debuggning.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
postgres_statements_query_info may be really, really long. this can lead to a problem, that victoria/ptometheus wouldn't scrape any data from exporter because of timeout or metrics length. Anyway, nobody cares about full query, usually we take a little bit from beginning to make further discussion or grep by source code. It would be wonderfull if we could set a size of query label in postgres_statements_query_info metric, i.e. first 100 symbols or bytes. Thanks!
The text was updated successfully, but these errors were encountered: