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

Partition is healthy is logged unnecessarily #9207

Closed
deepthidevaki opened this issue Apr 22, 2022 · 1 comment · Fixed by #9208
Closed

Partition is healthy is logged unnecessarily #9207

deepthidevaki opened this issue Apr 22, 2022 · 1 comment · Fixed by #9208
Assignees
Labels
area/observability Marks an issue as observability related kind/bug Categorizes an issue or PR as a bug severity/low Marks a bug as having little to no noticeable impact for the user version:1.3.8 version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0

Comments

@deepthidevaki
Copy link
Contributor

Describe the bug

Partition is logged as healthy repeatedly. However we do not see it becoming unhealthy. This is just noise. We should log only if there is a change in the health status.

image

@deepthidevaki deepthidevaki added the kind/bug Categorizes an issue or PR as a bug label Apr 22, 2022
@deepthidevaki deepthidevaki self-assigned this Apr 22, 2022
@npepinpe
Copy link
Member

Yes! I also noticed it, it's very regular every minute or so 😮

@npepinpe npepinpe added area/observability Marks an issue as observability related severity/low Marks a bug as having little to no noticeable impact for the user labels Apr 22, 2022
zeebe-bors-camunda bot added a commit that referenced this issue Apr 22, 2022
9208: Do not log health status unnecessarily r=deepthidevaki a=deepthidevaki

## Description

* Compare current and previous healthstatus instead of healthreport 

## Related issues

closes #9207



Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Apr 22, 2022
9213: [Backport stable/8.0] Do not log health status unnecessarily r=deepthidevaki a=github-actions[bot]

# Description
Backport of #9208 to `stable/8.0`.

relates to #9207

Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Apr 22, 2022
9212: [Backport stable/1.3] Do not log health status unnecessarily r=deepthidevaki a=github-actions[bot]

# Description
Backport of #9208 to `stable/1.3`.

relates to #9207

Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Apr 22, 2022
9213: [Backport stable/8.0] Do not log health status unnecessarily r=deepthidevaki a=github-actions[bot]

# Description
Backport of #9208 to `stable/8.0`.

relates to #9207

Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
zeebe-bors-camunda bot added a commit that referenced this issue Apr 22, 2022
9212: [Backport stable/1.3] Do not log health status unnecessarily r=deepthidevaki a=github-actions[bot]

# Description
Backport of #9208 to `stable/1.3`.

relates to #9207

Co-authored-by: Deepthi Devaki Akkoorath <deepthidevaki@gmail.com>
@deepthidevaki deepthidevaki added the version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 label May 3, 2022
@Zelldon Zelldon added the version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0 label Oct 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/observability Marks an issue as observability related kind/bug Categorizes an issue or PR as a bug severity/low Marks a bug as having little to no noticeable impact for the user version:1.3.8 version:8.1.0-alpha1 Marks an issue as being completely or in parts released in 8.1.0-alpha1 version:8.1.0 Marks an issue as being completely or in parts released in 8.1.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants