Skip to content

doc: dump cyclic buffer log memory #155

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

climagabriel
Copy link

No description provided.

@pluknet
Copy link
Collaborator

pluknet commented Aug 11, 2025

The existing wording is simple and generic, it suggests using memory log on the main level, to walk through ngx_cycle->(next->)log.
I have doubts that documenting aspects of using it on sublevels (http, server, ..) may be as useful, given that memory log "does not have significant impact on performance even under high load" (c).
Further, in addition to implications with finding an appropriate log reference, using it that way may not catch all possible cases, e.g. if crash happened not in a request context.
That said, although possible in practice, it'd rather refrain from documenting this.

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.

2 participants