-
Notifications
You must be signed in to change notification settings - Fork 18.7k
Fluentd: add fluentd-async, fluentd-request-ack, and deprecate fluentd-async-connect #39086
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
Conversation
Ping @tagomoris @cpuguy83 PTAL @tagomoris I noticed two more options that are in the driver, but not exposed through the docker API;
|
Codecov Report
@@ Coverage Diff @@
## master #39086 +/- ##
=========================================
Coverage ? 37%
=========================================
Files ? 612
Lines ? 45390
Branches ? 0
=========================================
Hits ? 16795
Misses ? 26308
Partials ? 2287 |
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.
Basically LGTM. I commented on a point for usability.
} | ||
|
||
if cfg[asyncKey] != "" && cfg[asyncConnectKey] != "" { | ||
return config, errors.Errorf("conflicting options: cannot specify both '%s' and '%s", asyncKey, asyncConnectKey) |
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.
This error msg doesn't show the pair of keys now conflicting (just shows values of these keys). It should show conflicting keys and these values for users.
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.
It's best if it can show that the one is now deprecated and the other is recommended.
ping @kolyshkin @cpuguy83 PTAL |
12d8fca
to
29e019a
Compare
29e019a
to
1b4631c
Compare
rebased ping @kolyshkin @cpuguy83 @tiborvass PTAL |
3e519d0
to
89b98f7
Compare
@cpuguy83 updated; PTAL |
89b98f7
to
1166e83
Compare
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.
LGTM
This option was deperecated in the upstream fluentd logging driver v1.4.0, and while we documented it as deprecated in the API changelog, there was no mention yet in the deprecated docs. relates to: - fluent/fluent-logger-golang#56 - moby/moby#39086 Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This option was deperecated in the upstream fluentd logging driver v1.4.0, and while we documented it as deprecated in the API changelog, there was no mention yet in the deprecated docs. relates to: - fluent/fluent-logger-golang#56 - moby/moby#39086 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 95b0c43) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in docker v20.10 and removed in v28.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in docker v20.10 and removed in v28.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Docker's fluentd log driver supports passing an "async" option. The "fluentd-async-connect" option was deprecated in Docker v20.10.0 and completely removed in v28.0.0. Reference: https://docs.docker.com/engine/deprecated/#fluentd-async-connect-log-opt Functionally, both options are equivalent, see: moby/moby#39086. Since Docker's refactor of the fluentd async option was not versioned and affects all API versions, we need to determine the appropriate option using the Docker Server version, in order to be backwards compatible.
Follow up to #39074 (first two commits are from that PR; I'll rebase once that's merged)(rebased)closes #40332
fluentd-async
option, deprecatefluentd-async-connect
. This ia a rename of the old option. The old option remains functional, but when used will log a deprecation warning in fluentd. If both the new, and old option is set, a "conflicting options" error is produced. This change is not versioned, and affects all API versions.fluentd-request-ack
option. This adds a newfluentd-request-ack
logging option for the Fluentd logging driver. If enabled, the server will respond with an acknowledgement. This option improves the reliability of the message transmission. This change is not versioned, and affects all API versions.