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

feat: LogPipeline flow health status based on Fluent Bit alerts #963

Merged
merged 35 commits into from
Apr 12, 2024

Conversation

skhalash
Copy link
Collaborator

@skhalash skhalash commented Apr 10, 2024

Description

Changes proposed in this pull request (what was done and why):

  • Map Fluent Bit metrics-based alerts to the LogPipeline status
  • Refactor the existing self-monitor prober and webhook handler code to allow a LogPipeline variant

Changes refer to particular issues, PRs or documents:

Traceability

  • The PR is linked to a GitHub issue.
  • New features have a milestone set.
  • New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
  • The corresponding GitHub issue has a respective area and kind label.
  • The follow-up issues (if any) are linked in the Related Issues section.
  • Adjusted the documentation if the change is user-facing.
  • The feature is unit-tested
  • The feature is e2e-tested

@kyma-bot kyma-bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 10, 2024
@kyma-bot
Copy link
Contributor

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@kyma-bot kyma-bot added cla: yes Indicates the PR's author has signed the CLA. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Apr 10, 2024
@skhalash skhalash marked this pull request as ready for review April 11, 2024 12:04
@skhalash skhalash requested a review from a team as a code owner April 11, 2024 12:04
@kyma-bot kyma-bot removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 11, 2024
@skhalash skhalash added this to the 1.14.0 milestone Apr 11, 2024
@skhalash skhalash added kind/feature Categorizes issue or PR as related to a new feature. area/logs LogPipeline labels Apr 11, 2024
@chrkl chrkl self-assigned this Apr 12, 2024
@kyma-bot kyma-bot added the lgtm Looks good to me! label Apr 12, 2024
@kyma-bot kyma-bot merged commit 0d0a49a into kyma-project:main Apr 12, 2024
24 checks passed
@skhalash skhalash deleted the self-monitor-log-pipeline-status branch April 30, 2024 09:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/logs LogPipeline cla: yes Indicates the PR's author has signed the CLA. kind/feature Categorizes issue or PR as related to a new feature. lgtm Looks good to me! size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants