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

[transport] make dial error logging compatible with ECS #227

Merged
merged 1 commit into from
Sep 9, 2024

Conversation

belimawr
Copy link
Contributor

@belimawr belimawr commented Sep 6, 2024

What does this PR do?

The LoggingDiler was logging an error with the field 'network' set as the network type (tcp/upd), however 'network' is an object in ECS, this would cause the log entry to be rejected by Elasticsearch.

Why is it important?

It makes our logs compatible with ECS

Checklist

  • My code follows the style guidelines of this project
  • [ ] I have commented my code, particularly in hard-to-understand areas
  • [ ] I have added tests that prove my fix is effective or that my feature works

## Author's Checklist
## Related issues

The LoggingDiler was logging an error with the field 'network' set as
the network type (tcp/upd), however 'network' is an object in ECS,
this would cause the log entry to be rejected by Elasticsearch.
@belimawr belimawr added the Team:Elastic-Agent Label for the Agent team label Sep 6, 2024
@belimawr belimawr self-assigned this Sep 6, 2024
@belimawr belimawr requested a review from a team as a code owner September 6, 2024 20:39
@belimawr belimawr requested review from rdner and faec and removed request for a team September 6, 2024 20:39
@elasticmachine
Copy link
Collaborator

💚 Build Succeeded

cc @belimawr

@belimawr belimawr merged commit 1111a9e into elastic:main Sep 9, 2024
6 checks passed
@belimawr belimawr deleted the fix-non-ecs-log-entry branch September 9, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Team:Elastic-Agent Label for the Agent team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants