You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you request metric without any usable slices (e.x. no data for a long time and everything was rolled up out of the disk, but metadata still there) - you'll have resulting list with timeStep = 1, which isn't that good (it'll require recalculation of this slice on later stages). With this patch, ceres will return slice with more proper time steps (will look for them in the config file or use default one, instead of '1').
Though in current form it depends on dkulikovskiy's branch, because this commit also improves his detection of unneeded slices.
The text was updated successfully, but these errors were encountered:
Confirmed, however this would only apply if you request the data outside of graphite, as normally if a node does not hasDataForInterval() then graphite won't bother looking it up.
vladimir-smirnov-sociomantic@555f974
If you request metric without any usable slices (e.x. no data for a long time and everything was rolled up out of the disk, but metadata still there) - you'll have resulting list with timeStep = 1, which isn't that good (it'll require recalculation of this slice on later stages). With this patch, ceres will return slice with more proper time steps (will look for them in the config file or use default one, instead of '1').
Though in current form it depends on dkulikovskiy's branch, because this commit also improves his detection of unneeded slices.
The text was updated successfully, but these errors were encountered: