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

[BUG] Anomaly Charts highlight entire time series as anomaly #417

Closed
Amatullah opened this issue Nov 18, 2021 · 3 comments
Closed

[BUG] Anomaly Charts highlight entire time series as anomaly #417

Amatullah opened this issue Nov 18, 2021 · 3 comments
Assignees
Labels
🛠️ backend 🐛 bug Something isn't working
Milestone

Comments

@Amatullah
Copy link
Member

Amatullah commented Nov 18, 2021

Describe the bug

For some KPIs, anomaly charts highlight the entire data as an anomaly i.e. in red. The problem occurs in some Drilldowns and DQ graphs too.

Explain the environment

  • Chaos Genius version: 0.1.3-alpha
  • OS Version / Instance: AWS EC2
  • Deployment type: Docker

Screenshots

The overall chart has been highlighted as an anomaly.

Screenshot from 2021-11-18 09-45-16

In certain places when you zoom the chart exhibits normal behaviour and when you zoom in at other places, the problem persists.

Screenshot from 2021-11-18 09-45-50
Screenshot from 2021-11-18 09-46-01

@suranah suranah added 🐛 bug Something isn't working 🖥️ frontend 🧮 algorithms Core algorithms, optimization & ML model related labels Nov 18, 2021
@Amatullah Amatullah added 🐛 bug Something isn't working and removed 🐛 bug Something isn't working 🧮 algorithms Core algorithms, optimization & ML model related labels Nov 18, 2021
@manassolanki
Copy link
Member

Partially fixed at the frontend side. Need to fix the issues at the backend data ingestion time as well.

@kartikay-bagla
Copy link
Contributor

@manassolanki can you update on what issues at the backend are causing this? I'll start working towards them.

@Samyak2 Samyak2 added this to the v0.4.0 milestone Jan 6, 2022
@Amatullah
Copy link
Member Author

Issue was being caused by having multiple entries in the db for anomaly. Refer issue #451. This has been resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🛠️ backend 🐛 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

6 participants