Skip to content

Task: investigate why some log entries are no longer filtered out #67

@jonrandahl

Description

@jonrandahl

In the latest gem release, the logs contain additional information which should be filtered out and not exposed while running in production mode.

For example:

{"ts":"2025-09-12T14:31:30.479Z","level":"INFO ","message":"response: vary: \"Accept\"x-response-id: \"10398\"cache-control: \"no-transform, max-age=0\"content-type: \"application/json\"transfer-encoding: \"chunked\"date: \"Fri, 12 Sep 2025 14:31:27 GMT\""}

Investigate why the OPTIONAL keys are being generated

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions