-
Notifications
You must be signed in to change notification settings - Fork 11
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
About trace data in abnormal time #11
Comments
"there is almost no trace information near the injected anomaly" |
For example, if I inject an exception into a service at 10:00, I might not log any trace data from 9:50 to 10:20. |
Sorry for the confusion. You need to align the time manually. Traces are collected at the UTC+8 time zone while records are at the UTC+0 (or the opposite) |
Yes, I've seen this in a previous issue, but it still comes up. Due to the lack of relevant anomaly trace, I'm not really sure how the TraceAnomaly calculates the anomaly and calculates the relevant metrics, I hope you can help me. |
I'll check it. |
Thank you very much for your help, much appreciated! |
Sorry to bother you, has this issue been resolved now? I seem to have encountered a similar problem... |
Any update? |
I am glad to see that you post your code and data. while analyzing the dataset you published, I found that there is almost no trace information near the injected anomaly, may I ask if this part of the trace data is not collected or cleaned up, very much looking forward to your answer.
The text was updated successfully, but these errors were encountered: