-
Notifications
You must be signed in to change notification settings - Fork 14
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
Chore: Update fluent-bit configuration to support CloudEvents from Tekton Pipelines #108
Labels
Comments
SergK
added a commit
that referenced
this issue
Jul 8, 2024
This commit modifies the fluent-bit configuration to include an additional port (8888) for receiving CloudEvents from Tekton Pipelines. This allows fluent-bit to capture both Kubernetes events and CloudEvents, providing a more comprehensive logging solution. The configuration also includes the necessary inputs and outputs for forwarding the logs to an OpenSearch cluster with specific formatting and TLS settings. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 8, 2024
This commit modifies the fluent-bit configuration to include an additional port (8888) for receiving CloudEvents from Tekton Pipelines. This allows fluent-bit to capture both Kubernetes events and CloudEvents, providing a more comprehensive logging solution. The configuration also includes the necessary inputs and outputs for forwarding the logs to an OpenSearch cluster with specific formatting and TLS settings. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 8, 2024
This commit modifies the fluent-bit configuration to include an additional port (8888) for receiving CloudEvents from Tekton Pipelines. This allows fluent-bit to capture both Kubernetes events and CloudEvents, providing a more comprehensive logging solution. The configuration also includes the necessary inputs and outputs for forwarding the logs to an OpenSearch cluster with specific formatting and TLS settings. Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
github-project-automation
bot
moved this from In Progress
to Done
in KubeRocketCI (EPAM Delivery Platform)
Jul 8, 2024
SergK
added a commit
that referenced
this issue
Jul 8, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 8, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 8, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 8, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 9, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 9, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 11, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
SergK
added a commit
that referenced
this issue
Jul 11, 2024
Signed-off-by: Sergiy Kulanov <sergiy_kulanov@epam.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
Currently, our fluent-bit setup does not capture CloudEvents from Tekton Pipelines. This limits our logging capabilities to only Kubernetes events.
Describe the solution you'd like
I would like the fluent-bit configuration to be updated to include an additional port (8888) specifically for receiving CloudEvents from Tekton Pipelines. This update will allow fluent-bit to capture both Kubernetes events and CloudEvents, providing a more comprehensive logging solution. The configuration should also include the necessary inputs and outputs for forwarding the logs to an OpenSearch cluster, with specific formatting and TLS settings.
Describe alternatives you've considered
N/A
Additional context
This change is crucial for improving our logging infrastructure by integrating CloudEvents from Tekton Pipelines, thus offering a more detailed and comprehensive view of events within our system.
The text was updated successfully, but these errors were encountered: