Add logging around a failure you can't reproduce

Adds logging so the next failure shows why it happened, with personal data masked.

What you ask

Search Acme

billing

2
  1. Tom

    @devboxes a payout statement comes out empty once or twice a week and we can't reproduce it. can you add logging so we see why next time?

  2. devboxes APP

    #65 logs the payout ID, the period and how many bookings the query found, right before the statement renders. No names or amounts go in the log. Checks pass.

    Opened #65

What devboxes does

  1. Work out what the failure depends on

    • devboxes lists the decisions and values that can lead to the failure, with references to the files.
  2. Add the logging

    • Each of those decisions now logs its values.
    • Any personal data in the logs is masked.
  3. Verify

    1. Install dependencies

    2. Test

    3. Lint

    4. If it fails

      1. Fix

        • The tests pass.
      2. Test again

      3. Lint again

  4. Publish

  5. Review

Good for

Startups

More tasks to ship from issues

Ask devboxes to add logging around a failure you can't reproduce

Get started for free