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
We use --log_queries_to_file option to log queries to file, then these queries are being indexed in ES(elastic search)
We only concerned about the queries that had an error, however this option is not able to filter queries that had an error , then get us many queries on ES.
For a very busy vitess cluster with many vtgate instances, the log volume being huge can potentially make trouble to our ES clusters, and we were not easy to find all these queries had error.
We would like to have an ability to use --log_queries_to_file but limit what’s logged there to queries that had an error
for instance to only log queries that had an error like following.
We use
--log_queries_to_file
option to log queries to file, then these queries are being indexed in ES(elastic search)We only concerned about the queries that had an error, however this option is not able to filter queries that had an error , then get us many queries on ES.
For a very busy vitess cluster with many vtgate instances, the log volume being huge can potentially make trouble to our ES clusters, and we were not easy to find all these queries had error.
We would like to have an ability to use
--log_queries_to_file
but limit what’s logged there to queries that had an errorfor instance to only log queries that had an error like following.
The text was updated successfully, but these errors were encountered: