-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[8.0] Remove legacy logging #112305
[8.0] Remove legacy logging #112305
Conversation
retest |
@elasticmachine merge upstream |
merge conflict between base and head |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Self review.
I tried to grep all usages of the removed settings in the documentation, but may have potentially missed some, a second pair of eyes would be more than welcome.
@@ -163,7 +162,7 @@ export class CliDevMode { | |||
runExamples: cliArgs.runExamples, | |||
cache: cliArgs.cache, | |||
dist: cliArgs.dist, | |||
quiet: !!cliArgs.quiet, | |||
quiet: false, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elastic/kibana-operations I kept the property in the Optimizer
options and just set it to false to avoid more downstream changes. This can eventually be cleaned up as a follow-up (unless we really want to do it in current PR).
@@ -21,8 +21,6 @@ export interface EnvOptions { | |||
export interface CliArgs { | |||
dev: boolean; | |||
envName?: string; | |||
/** @deprecated */ | |||
quiet?: boolean; | |||
silent?: boolean; | |||
verbose?: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't sure if I should keep silent
and verbose
in CliArgs
. Those are effectively unused inside core
, as now their only usages is to change logging.root.level
from src/cli/serve/serve.js
, but at the same times, they're still cli args, so we may want to have them propagated to core for telemetry of some other need. WDYT?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know how many users rely on silent
and verbose
cli flags? What bothers me is that we allow using them as CLI flags
but not as config values. Btw we need to replace all the logging.*
values in kibana.yml
with their Kibana Logging system counterparts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know how many users rely on silent and verbose cli flags? What bothers me is that we allow using them as CLI flags but not as config values.
Yeah this bugs me too -- IIRC when we had last discussed this (I think with @spalger ?), the case was made that configuring appenders via the CLI is more cumbersome than when working in the yaml, and that it was a minimal maintenance burden to keep silent
and verbose
in place, which is why we only deprecated quiet
at the time.
Pinging @elastic/kibana-core (Team:Core) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Don't forget to remove the legacy logging system
mentions in
- code
message: `Setting [${fromPath}.logQueries] is deprecated and no longer used. You should set the log level to "debug" for the "elasticsearch.queries" context in "logging.loggers" or use "logging.verbose: true".`, - config file
Lines 93 to 104 in c09776d
# Enables you to specify a file where Kibana stores log output. #logging.dest: stdout # Set the value of this setting to true to suppress all logging output. #logging.silent: false # Set the value of this setting to true to suppress all logging output other than error messages. #logging.quiet: false # Set the value of this setting to true to log all events, including system usage information # and all requests. #logging.verbose: false - https://github.com/elastic/kibana/blob/c09776dc76cf8e7c4efa1a1dd5bac2a635d66193/docs/settings/logging-settings.asciidoc#backwards-compatibility
- https://github.com/elastic/kibana/blob/c09776dc76cf8e7c4efa1a1dd5bac2a635d66193/src/core/server/logging/README.mdx#logging-config-migration
- https://github.com/elastic/kibana/blob/c09776dc76cf8e7c4efa1a1dd5bac2a635d66193/docs/developer/architecture/core/logging-configuration-migration.asciidoc#logging-configuration-migration
- https://github.com/elastic/kibana/blob/c09776dc76cf8e7c4efa1a1dd5bac2a635d66193/docs/user/production-considerations/production.asciidoc#use-kib-in-a-production-environment
And ping Security solution. Detection engine
team to update their readme file
logging.verbose: true |
src/cli/serve/integration_tests/__fixtures__/invalid_config.yml
Outdated
Show resolved
Hide resolved
src/cli/serve/integration_tests/__fixtures__/reload_logging_config/kibana.test.yml
Show resolved
Hide resolved
logging.rotate.usePolling | ||
logging.silent | ||
logging.useUTC | ||
logging.verbose |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@elastic/kibana-security is xpack.security.audit.appender.legacyLoggingConfig
still necessary in this file?
@@ -21,8 +21,6 @@ export interface EnvOptions { | |||
export interface CliArgs { | |||
dev: boolean; | |||
envName?: string; | |||
/** @deprecated */ | |||
quiet?: boolean; | |||
silent?: boolean; | |||
verbose?: boolean; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we know how many users rely on silent
and verbose
cli flags? What bothers me is that we allow using them as CLI flags
but not as config values. Btw we need to replace all the logging.*
values in kibana.yml
with their Kibana Logging system counterparts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code review only; security plugin unit test snapshot change LGTM 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes on code under operations team code owners LGTM
💚 Build Succeeded
Metrics [docs]Public APIs missing exports
History
To update your PR or re-run it, just comment with: |
Summary
Merge blocked by https://github.com/elastic/cloud/issues/80187
Fix #50660
Fix #82240
Part of #103915
All in title.
Tasks
@kbn/legacy-logging
LegacyObjectToConfigAdapter
@hapi/good
/@hapi/good-squeeze
/@hapi/podium
from kibana dependenciessrc/core/server/legacy/logging/appenders
logging.root.appenders
to have adefault
src/core/server/legacy
)kibana-docker
filesrc/cli/serve/serve.js
to remove references to removed deprecated flags (quiet
,log-file
), and remove references to deprecated legacy config (used insideverbose
andsilent
)Checklist
Release Note
Kibana's logging configuration and log output format has changed. Please refer to the documentation for more detail on how to configure the new logging system.