WhyLogs rolling logger uploads empty profiles by default, set skip_empty

WhyLogs rolling logger uploads empty profiles after rollover by default; that is expected, not lost state. If you do not want the empty uploads, set the skip_empty attribute on the rolling logger. Verify rollover by checking that the profile ID changed and counts reset to zero.

Context: WhyLabs whylogs issue #1083 (closed): a user thought the rolling logger was not wiping internal state after writing, since profiles kept being uploaded after rollover. Maintainers andyndang and jamie256 investigated and found the claims were false: the profile IDs change and the new profiles' metric counts are all zero after rollover. By default the rolling logger does not skip empty profiles, so it uploads them; that is by design, not a bug.

Source: WhyLabs whylogs issue #1083 (closed): a user thought the rolling logger was not wiping internal state after writing, since profiles kept being uploaded after rollover. Maintainers andyndang and jamie256 investigated and found the claims were false: the profile IDs change and the new profiles' metric counts are all zero after rollover. By default the rolling logger does not skip empty profiles, so it uploads them; that is by design, not a bug.

Verified resolution: WhyLogs rolling logger uploads empty profiles after rollover by default; that is expected, not lost state. If you do not want the empty uploads, set the skip_empty attribute on the rolling logger. Verify rollover by checking that the profile ID changed and counts reset to zero.

Source URL: https://github.com/whylabs/whylogs/issues/1083