Skip to content
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

[DOCS] enabling logging.verbose depends on silent and quiet settings being false #74827

Closed
wants to merge 3 commits into from
Closed
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/setup/settings.asciidoc
Original file line number Diff line number Diff line change
Expand Up @@ -304,7 +304,7 @@ list of timezones, refer to https://en.wikipedia.org/wiki/List_of_tz_database_ti

| [[logging-verbose]] `logging.verbose:` {ece-icon}
| Set to `true` to log all events, including system usage information and all
requests. *Default: `false`*
requests. Requires `logging.silent` and `logging.quiet` set to `false`. *Default: `false`*
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it also be worth adding a note to logging.quiet that it requires logging.silent to be true?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe I can be clearer here, but if either logging.silent or logging.quiet are set to true then also setting logging.verbose to true will result in Kibana failing to start. Put another way, the logging.verbose setting is mutually exclusive to these other two settings.
Separately, I don't think if logging.silent is true then logging.quiet also needs to be true or vice-versa to avoid issues, but I can also test this in case it's another dependency.
We might indicate the opposite configuration in the docs for these other two settings if you want to use them then you need to ensure verbose is false, which should cover warning for this startup failure scenario from the context of these two different groups of settings.


| `map.includeElasticMapsService:` {ess-icon}
| Set to `false` to disable connections to Elastic Maps Service.
Expand Down