chore(worker): wrangler.toml has no [observability] block, so production Worker logs are not kept

Open Beginner friendly
#17 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
82/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
cloud, javascript

Research direction

Open wrangler.toml at the repo root and confirm it only sets name, entry point and compatibility_date. Add an [observability] block with enabled = true plus a commented head_sampling_rate explaining the free-plan log limits, then add a test that parses the TOML (e.g. with a TOML parser in the existing test setup) and asserts the flag is true. Done means the new config test passes alongside the existing suite.

Written by the indexing model from the issue text.

Description

agents area: runtime automation chore cli consistency dependencies developer-experience difficulty: easy documentation enhancement good first issue help wanted hygiene json-output priority: P3 starters tests

Problem

wrangler.toml in flisk-sh/analytics has no [observability] block. Without it, Worker logs and errors are not persisted, so when a user reports a 500 or a slow request there is nothing to look at after the fact (live wrangler tail only shows requests while someone is watching).

Repro:

gh api repos/flisk-sh/analytics/contents/wrangler.toml --jq .content | base64 -d | grep -c observability
# 0

Root Cause Analysis

The Worker config sets name, entry point and compatibility_date only. Cloudflare Workers Logs is opt-in per Worker through [observability].

TDD Fix Plan

  1. RED: Add a test that parses wrangler.toml and asserts observability.enabled is true.
    GREEN: Add [observability] with enabled = true (consider head_sampling_rate to stay inside the free plan's log limits).

REFACTOR: None expected.

Acceptance Criteria

  • wrangler.toml enables observability
  • Sampling rate is documented in the file
  • All new tests pass
  • Existing tests still pass
Dominant language
JavaScript
Stars
0
Forks
2
Avg merge
1h 33m
Merged PRs (30d)
7

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from flisk-sh/analytics

All issues in flisk-sh/analytics

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.