Skip to content

Document SIGHUP reload of Kibana logging config (self-managed) - #8436

Draft
gsoldevila wants to merge 1 commit into
mainfrom
kibana-hot-reload-logging-docs
Draft

gsoldevila wants to merge 1 commit into
mainfrom
kibana-hot-reload-logging-docs

Conversation

@gsoldevila

Copy link
Copy Markdown
Member

Summary

Documents that self-managed {{kib}} re-reads kibana.yml and re-applies its logging configuration when it receives a SIGHUP signal, without a restart. This is the reliable no-restart path for temporarily raising verbosity while troubleshooting (adjust a logger level or meta filters, reload, capture logs, revert, reload again).

Adds a "Reload the logging configuration without restarting" section to the self-managed Configure Kibana page, covering:

  • The kill -HUP <pid> workflow and the Docker docker kill --signal=HUP variant.
  • The multi-worker case (signal each process).
  • How to confirm the reload (Reloaded logging configuration due to SIGHUP log line).
  • The Windows limitation (SIGHUP unavailable → restart instead).

Scoped to logging on purpose: SIGHUP re-reads the whole kibana.yml, but logging is the configuration that Kibana deliberately re-applies live.

Relates to elastic/kibana#271682 (parent epic elastic/kibana#257240).

Adds a section explaining that self-managed Kibana re-reads kibana.yml and
re-applies its logging configuration on SIGHUP, without a restart. Useful for
temporarily raising verbosity while troubleshooting.

Relates to elastic/kibana#271682.

Co-authored-by: Cursor <cursoragent@cursor.com>
@github-actions

Copy link
Copy Markdown
Contributor

Elastic Docs AI PR menu

Check the box to run an AI review for this pull request.

  • Review docs changes (docs-review). Status: not started.

Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team.

@github-actions

github-actions Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

🔍 Preview links for changed docs

@github-actions

Copy link
Copy Markdown
Contributor

✅ Elastic Docs Style Checker (Vale)

No issues found on modified lines!


The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale.

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