Skip to content

docs: Keploy's logs carry no application data unless KEPLOY_LOG_CONTENT is set - #933

Draft
slayerjain wants to merge 1 commit into
mainfrom
train/fix/log-content-docs
Draft

slayerjain wants to merge 1 commit into
mainfrom
train/fix/log-content-docs

Conversation

@slayerjain

Copy link
Copy Markdown
Member

Documents KEPLOY_LOG_CONTENT, from keploy/keploy#4858 (the switch) and keploy/keploy#4861 (the log lines it gates). Merge with the keploy release that ships them.

What changes for users

Keploy's log lines no longer carry the application's data by default: request and response bodies, header values, URL query values, database rows and bind values, recorded mocks. That holds at every level, --debug included, on the console, in keploy-logs.txt, and in the agent's agent-debug.log, which the agent writes on every Docker-mode run. A line names such a value by its length and a 12-hex-digit fingerprint, beside facts that are not data (message type, method and path, header names, ids, counts).

KEPLOY_LOG_CONTENT=1 (or true), read once at start, opts back into the data itself. Keploy passes it on to the agent it starts, in a container or through sudo.

The edit

versioned_docs/version-4.0.0/running-keploy/cli-commands.md:

  • A new section, "Log your application's data": the default, the fingerprint, how to opt in, a caution about sharing logs written with it set, and that test reports and mismatch tables still show the values they compare (they are not log lines).
  • The --debug entries of record and test link to it.

prettier@2.8.8 --check passes on the page.

…NT is set

Debug logs, agent-debug.log included, name a payload, a header value, a query value or a row by its length and fingerprint. KEPLOY_LOG_CONTENT=1 opts into the data itself; the page says where it applies, what it costs, and that reports still show the values they compare.

Signed-off-by: slayerjain <shubhamkjain@outlook.com>

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant