We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
when running load test, set --minloglevel=2, but it's difficult to find the elapsed time in log.
--minloglevel=2
we can add the query-id in log framework, and the log like query 1631774709873887, palapala then we can use grep or es to analyze the tracing.
query 1631774709873887, palapala
The text was updated successfully, but these errors were encountered:
cherry pick from nebula: fix traverse build path memory tracker (veso…
38a829c
…ft-inc#5619) (vesoft-inc#2880) fix traverse build path memory tracker (vesoft-inc#5619) Co-authored-by: jimingquan <mingquan.ji@vesoft.com>
No branches or pull requests
when running load test, set
--minloglevel=2
, but it's difficult to find the elapsed time in log.we can add the query-id in log framework, and the log like
query 1631774709873887, palapala
then we can use grep or es to analyze the tracing.
The text was updated successfully, but these errors were encountered: