Build(deps): Bump ruby/setup-ruby from 1.298.0 to 1.299.0 (#21)
Bumps ruby/setup-ruby from 1.298.0 to 1.299.0.
Release notes
Sourced from ruby/setup-ruby's releases.
v1.299.0
What's Changed
- Update CRuby releases on Windows by
@ruby-builder-botin ruby/setup-ruby#896Full Changelog: https://github.com/ruby/setup-ruby/compare/v1.298.0...v1.299.0
Commits
3ff19f5Update CRuby releases on Windows- See full diff in compare view
Dependabot will resolve any conflicts with this PR as long as you don’t alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Signed-off-by: dependabot[bot] support@github.com Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802032778号
fluent-plugin-parser-cri
Fluentd parser plugin to parse CRI logs.
CRI logs consist of
time,stream,logtagandmessageparts like below:Installation
RubyGems
Configuration
stream/logtagfields or not when<parse>section is specified. Default istrue<parse> section (optional)
Same as parser plugin configuration.
This nested
<parse>is used for parsingmessagepart.Log and configuration example
Basic case
With this configuration, following CRI log
is parsed to
Parse message part with parsers
By specifying
<parse>section, you can parsemessagepart with parser plugins.With this configuration, following CRI log
is parsed to
If you don’t need
stream/logtagfields, setmerge_cri_fields falselike below:Concatenate multiple
messagerecords into oneIf you want to concatenate the following
messagerecords into one record, use @type concat filter plugin withuse_partial_cri_logtagparameter.See fluent-plugin-concat’s usage in more details.
Copyright