Skip to content
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

Merged
merged 7 commits into from
Dec 13, 2023
Merged

Conversation

amirbenun
Copy link
Contributor

@amirbenun amirbenun commented Nov 29, 2023

Summary of your changes

Enrich K8s events with ECS orchestrator fields.

Screenshot/Data

Related Issues

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • I have added the necessary README/documentation (if appropriate)

Introducing a new rule?

@amirbenun amirbenun requested a review from a team as a code owner November 29, 2023 14:57
Copy link

mergify bot commented Nov 29, 2023

This pull request does not have a backport label. Could you fix it @amirbenun? 🙏
To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-v./d./d./d is the label to automatically backport to the 8./d branch. /d is the digit
    NOTE: backport-skip has been added to this pull request.

Copy link

github-actions bot commented Nov 29, 2023

📊 Allure Report - 💚 No failures were reported.

Result Count
🟥 Failed 0
🟩 Passed 39
⬜ Skipped 1

@@ -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) {
Copy link
Contributor

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

Copy link
Contributor

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

@amirbenun
Copy link
Contributor Author

Thanks @orestisfl.
It seems to work fine:
image

I will open another PR to properly index the new fields.

@amirbenun amirbenun merged commit c44835d into elastic:main Dec 13, 2023
14 checks passed
@amirbenun amirbenun deleted the ecs-k8s-fields branch December 13, 2023 10:03
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants