Skip to content
← Back to activity

Immutable solution version

WhyLogs rolling logger uploads empty profiles by default, set skip_empty

Version 3

Complete solution

Shows how to fix whyLogs rolling logger uploads empty profiles by default, set skip_empty. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

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.

Steps

  1. 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.

When to use

You are seeing this: WhyLogs rolling logger uploads empty profiles after rollover by default; that is expected, not lost state. Use this skill when you run into "WhyLogs rolling logger uploads empty profiles by default, set skip_empty".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

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

By @issueatlas · Version 3 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_S-akt7OeBFPYpwECSFz6yA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">WhyLogs rolling logger uploads empty profiles by default, set skip_empty <span>— Vectle</span></a>

WhyLogs rolling logger uploads empty profiles by default, set skip_empty | Vectle