Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

[BUG] Sample feature output visualisation is incorrect #407

Open
allenphilip93 opened this issue Mar 23, 2022 · 3 comments
Open

[BUG] Sample feature output visualisation is incorrect #407

allenphilip93 opened this issue Mar 23, 2022 · 3 comments

Comments

@allenphilip93
Copy link

allenphilip93 commented Mar 23, 2022

Description:
The sample feature output visualisation is shown differently from the actual value

Actuals:
image

Sample Feature Output:
image

I've taken the sample index and applied the same filters in both the cases. For the feature I've aggregated by count on one of the filtered features.
drawing

ES Version: 1.10.1

@kaituo
Copy link
Member

kaituo commented Mar 25, 2022

The actual graph showed it is per 12 hours. Does it mean you have a count of doc.transactionEvent.store_name.keyword every 12 hours? What intervals do you use for the detector?

@allenphilip93
Copy link
Author

allenphilip93 commented Apr 6, 2022

Yes, I've configured the anomaly detector interval for 12h with default window size (8 intervals). I'm also using the same field for x-axis (lastModifiedOn) for both the cases.

Just to clarify, the plot for Sample Feature Breakdown is essentially the input time series feature for the detector in the same default timezone right?

@kaituo
Copy link
Member

kaituo commented Apr 18, 2022

Tried to reproduce your bug without success. It is hard to make the graph look exactly the same as AD dashboard and Kibana Visualization use different start and end timestamps to aggregate data. For example, even though both graphs use 5 minute interval, AD dashboard uses the range between 1650180367561 and 1650180367561 to aggregate data, while Kibana Visualization uses the range between 1650180317561 and 1650180317561 to aggregate data. But the rough trend and shape of the line should match. But from your graphs, we have totally different things.

Also, yes, the plot for Sample Feature Breakdown is essentially the input time series feature for the detector in the same default timezone.

Can you share your data and configuration (including AD and visualization configuration)? We can also get on a call if it is easier. If yes, please leave your email and preferred time slots.

Example 1 (5 min interval):
Screen Shot 2022-04-18 at 10 32 34 AM

Screen Shot 2022-04-18 at 10 32 43 AM

Example 2 (5 minute interval):
Screen Shot 2022-04-18 at 10 17 21 AM

Screen Shot 2022-04-18 at 10 17 06 AM

Example 3 (12 hr interval):
Screen Shot 2022-04-18 at 12 29 31 PM

Screen Shot 2022-04-18 at 12 29 40 PM

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

No branches or pull requests

2 participants