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.

Sign up for GitHub

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

Jump to bottom

More intelligent ovalues mismatch resolution #4

Open
grobian opened this issue May 2, 2014 · 2 comments
Open

More intelligent ovalues mismatch resolution #4

grobian opened this issue May 2, 2014 · 2 comments
Milestone
0.80

Comments

@grobian
Copy link
Collaborator

grobian commented May 2, 2014

Currently zipper takes the first response received when there is a mismatch in granularity between copies received. This is due to configuration issue on the backends, but nevertheless it would be nice if the zipper could handle this more intelligently, such that we see more, and have less flapping (data is there, next load data isn't). For example, zipper could return the metric that has the least missing values (percentually?), iso the first received.
@dgryski
Copy link
Member

dgryski commented May 3, 2014

I might only implement it for the JSON responses

@dgryski
Copy link
Member

dgryski commented Oct 4, 2014

Also could return the highest granularity metric in case of conflicts.

dgryski added a commit that referenced this issue Oct 5, 2014
@dgryski
Choose a metric with high resolution as 'base' metric
444288c 
This way if we discover the metrics have different resolutions, we'll
return the one containing (hopefully) the most information.  Note that
we still might have 'more' information (in terms of non-None data
points) if we chose a different metric instead.  Future work, I guess.

Updates issue #4.
@Civil Civil added this to the 0.80 milestone Apr 25, 2017
@Civil Civil mentioned this issue Apr 25, 2017
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.80
Development

No branches or pull requests
3 participants
@grobian @Civil @dgryski