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

Automated cherry pick of #1463: bugfix: change log-analytics created index prefix #1464

Conversation

erda-bot
Copy link
Member

Cherry pick of #1463 on release/1.2.

Squashed commit message:

commit 467236d865b18c0bfbbfaa2dc2aa4c6d5f84a1af
Author: 郭刚平 <512979011@qq.com>
Date:   Mon Aug 16 19:18:45 2021 +0800

    bugfix: change log-analytics created index prefix (#1463)

What type of this PR

Add one of the following kinds:
/kind bug

What this PR does / why we need it:

index of log-analytics es not rolling

Specified Reviewers:

/assign @liuhaoyang @recallsong

ChangeLog

Language Changelog
🇺🇸 English Fix ES index of log-analytics not rolling
🇨🇳 中文 修复日志分析ES索引未滚动的问题

Need cherry-pick to release versions?

/cherry-pick release/1.2

@erda-bot
Copy link
Member Author

Automated cherry pick can ONLY be triggered when this PR is MERGED!

@liuhaoyang
Copy link
Contributor

/approve

@codecov
Copy link

codecov bot commented Aug 16, 2021

Codecov Report

Merging #1464 (467236d) into release/1.2 (c22c399) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@             Coverage Diff              @@
##           release/1.2    #1464   +/-   ##
============================================
  Coverage        12.08%   12.08%           
============================================
  Files              981      981           
  Lines           102241   102241           
============================================
  Hits             12359    12359           
  Misses           88776    88776           
  Partials          1106     1106           

@erda-bot erda-bot merged commit cfc8e7e into erda-project:release/1.2 Aug 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants