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

Add processor optional input for the Kubernetes integration #4288

Closed
ChrsMark opened this issue Sep 23, 2022 · 3 comments · Fixed by #4363
Closed

Add processor optional input for the Kubernetes integration #4288

ChrsMark opened this issue Sep 23, 2022 · 3 comments · Fixed by #4363
Assignees
Labels
8.6 candidate release-pending Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team [elastic/obs-cloudnative-monitoring] v8.6.0

Comments

@ChrsMark
Copy link
Member

At the moment we cannot add a processor in the Kubernetes integration when it is managed by Fleet UI. It would be helpful to add a processor optional input so as to cover cases like when orchestrator fields are not populated in specific environments.

@ChrsMark ChrsMark added release-pending Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team [elastic/obs-cloudnative-monitoring] labels Sep 23, 2022
@ChrsMark ChrsMark self-assigned this Sep 23, 2022
@gizas
Copy link
Contributor

gizas commented Sep 23, 2022

Long term solution would be: elastic/kibana#140276

@vnirocha
Copy link

Any updates on this? The issue is closed but it seems like the new version is not available to download on kibana.

@gizas
Copy link
Contributor

gizas commented Nov 1, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
8.6 candidate release-pending Team:Cloudnative-Monitoring Label for the Cloud Native Monitoring team [elastic/obs-cloudnative-monitoring] v8.6.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants