Skip to content
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

Some injected memory anomalies do not have impact on the memory metrics #11

Open
mistycheney opened this issue Mar 28, 2023 · 1 comment

Comments

@mistycheney
Copy link

mistycheney commented Mar 28, 2023

For example, I am checking the impact of the following injected anomaly:

2021-08-14 03:49:04,212 | WARNING | 0.0.0.4 | 172.17.0.3 | dbservice1 | [memory_anomalies] trigger a high memory program, start at 2021-08-14 03:39:03.575551 and lasts 600 seconds and use 1g memory

Below is a plot of the memory-related metrics on this node and service around that time. Red region is the duration of the high-memory program.
image

There is no change in any metric before and after the anomaly is injected.

@Xander-cloudwise
Copy link

Thank you for your concern to GAIA-Dataset. If the metrics of the Docker container cannot reflect the problem, you can try to view the host metrics of the corresponding IP address.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants