Best way to handle sec and ms level of granularity

[marcnuth]

Best way to handle sec and ms level of granularity

[hokiegeek2]

No worries! Yes, please do that so it can be tracked. I am currently testing the fix that resamples data with ms and sec granularity. It's taking awhile because I need to generate it from metricbeat.

[triciascully]

I vote for (3), and thanks for debugging this!

On a separate but related note, I've been manually running the code and setting the period to period = 96 because the data I'm working with is at a 15min interval - can you build in an option for configuration of the period as well, since people might be working with data that's every 10min, 15min, 30min, 2hrs, etc.?

[hokiegeek2]

Yep, I can do that! Please put in a issue so it can be tracked. Thanks —John

…

Sent from my iPhone

On Sep 20, 2018, at 4:55 PM, triciascully ***@***.***> wrote: I vote or (3), and thanks for debugging this! On a separate but related note, I've been manually running the code and setting the period to period = 96 because the data I'm working with is at a 15min interval - can you build in an option for configuration of the period as well, since people might be working with data that's every 10min, 15min, 30min, 2hrs, etc.? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[hokiegeek2]

Adding in code to do the following:

1. enable resampling of both sec and ms to minute
2. render resampling of both sec and ms to be configurable so that either the resampling to a minute granularity occurs or a ValueError is thrown

[triciascully]

Ah thank you, John! Sorry for the delay, I've been traveling - do you still need this in an issue?

[hokiegeek2]

Okay, pushed pull request.

[hokiegeek2]

@triciascully this is implemented and tested in the master branch of my fork

[hokiegeek2]

merged, thanks @Marcnuth