-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Add ECS orchestrator fields #1604
Conversation
This pull request does not have a backport label. Could you fix it @amirbenun? 🙏
|
📊 Allure Report - 💚 No failures were reported.
|
@@ -82,7 +86,20 @@ func (r K8sResource) GetMetadata() (fetching.ResourceMetadata, error) { | |||
}, nil | |||
} | |||
|
|||
func (r K8sResource) GetElasticCommonData() (map[string]any, error) { return nil, nil } | |||
func (r K8sResource) GetElasticCommonData() (map[string]any, error) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please be aware that this might conflict with other data provider fields, see #1605
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's probably fine because the fields are already in the form of orchestrator.resource.xyz
but leaving this comment so you can verify that it's working as expected
Thanks @orestisfl. I will open another PR to properly index the new fields. |
Summary of your changes
Enrich K8s events with ECS orchestrator fields.
Screenshot/Data
Related Issues
Checklist
Introducing a new rule?