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

[8.0](backport #28927) Remove logging.files.suffix option and always use datetime suffixes #29065

Merged
merged 1 commit into from
Nov 22, 2021

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Nov 22, 2021

This is an automatic backport of pull request #28927 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

…#28927)

## What does this PR do?

This PR contains several improvements to the output file log rotation:
* Removes suffix option as discussed offline
* Filenames end in extension name so users get a hint about the contents
* Removes `time.Sleep` from testing code
* Datetime format no longer contains hour and minutes. In case of conflict on rotation, an index is appended to the filename.

## Why is it important?

Previously, log file suffixes were configurable. Users had the option to either add the count or the datetime to the end of the log file. From now on, we only allow datetime based naming. Hence the configuration option `logging.files.suffix` is removed.

Example:
Filebeat is writing logs to `filebeat-20211111.ndjson` actively. Then a few minutes later it gets rotated, and the new active file becomes `filebeat-20211111-1.ndjson`.

This change should help with Beats not being able to rotate files on Windows.

(cherry picked from commit f2ae281)
@mergify mergify bot requested review from a team as code owners November 22, 2021 09:39
@mergify mergify bot added the backport label Nov 22, 2021
@mergify mergify bot assigned kvch Nov 22, 2021
@botelastic botelastic bot added the needs_team Indicates that the issue/PR needs a Team:* label label Nov 22, 2021
@botelastic
Copy link

botelastic bot commented Nov 22, 2021

This pull request doesn't have a Team:<team> label.

@elasticmachine
Copy link
Collaborator

elasticmachine commented Nov 22, 2021

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2021-11-22T10:18:11.400+0000

  • Duration: 147 min 23 sec

  • Commit: b6400b8

Test stats 🧪

Test Results
Failed 0
Passed 48604
Skipped 4296
Total 52900

💚 Flaky test report

Tests succeeded.

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

  • /package : Generate the packages and run the E2E tests.

  • /beats-tester : Run the installation tests with beats-tester.

  • run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)

@kvch
Copy link
Contributor

kvch commented Nov 22, 2021

jenkins run tests

@kvch kvch merged commit 59326b9 into 8.0 Nov 22, 2021
@mergify mergify bot deleted the mergify/bp/8.0/pr-28927 branch November 22, 2021 13:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport needs_team Indicates that the issue/PR needs a Team:* label
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants