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

[symantec_endpoint] Adopt ECS log.syslog mappings #7878

Conversation

andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Sep 19, 2023

What does this PR do?

ECS added log.syslog fields and those needed to be adopted by symantec_endpoint to avoid type conflicts across integrations and to make the syslog data representation consist.

As much as possible this tries to avoid breaking changes, but the field data type of log.syslog.version had to change from long to keyword to be consistent with ECS.

The other existing symantec_endpoint log.syslog fields that are not part of ECS were maintained and documented as deprecated. log.syslog.process.name is an alias to ECS log.syslog.appname. And log.syslog.process.name is kept as a long representation of ECS log.syslog.procid.

Fixes #7843

Checklist

  • I have reviewed tips for building integrations and this pull request is aligned with them.
  • I have verified that all data streams collect metrics or logs.
  • I have added an entry to my package's changelog.yml file.
  • I have verified that Kibana version constraints are current according to guidelines.

Related issues

@elasticmachine
Copy link

Pinging @elastic/security-external-integrations (Team:Security-External Integrations)

ECS added log.syslog fields and those needed to be adopted by
symantec_endpoint to avoid type conflicts across integrations
and to make the syslog data representation consist.

As much as possible this tries to avoid breaking changes, but
the field data type of log.syslog.version had to change from long to keyword
to be consistent with ECS.

The other existing symantec_endpoint log.syslog fields that are not part
of ECS were maintained and documented as deprecated. log.syslog.process.name
is an alias to ECS log.syslog.appname. And log.syslog.process.name is kept
as a long representation of ECS log.syslog.procid.

Fixes elastic#7843
@andrewkroh andrewkroh force-pushed the symantec_endpoint/feature/adopt-ecs-log-syslog branch from 9b87c74 to d4f0e7c Compare September 19, 2023 20:06
@elasticmachine
Copy link

elasticmachine commented Sep 19, 2023

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS
Pipeline View Test View Changes Artifacts preview preview

Expand to view the summary

Build stats

  • Start Time: 2023-09-19T20:07:45.221+0000

  • Duration: 16 min 1 sec

Test stats 🧪

Test Results
Failed 0
Passed 24
Skipped 0
Total 24

🤖 GitHub comments

Expand to view the GitHub comments

To re-run your PR in the CI, just comment with:

  • /test : Re-trigger the build.

@elasticmachine
Copy link

🌐 Coverage report

Name Metrics % (covered/total) Diff
Packages 100.0% (1/1) 💚
Files 100.0% (1/1) 💚 5.772
Classes 100.0% (1/1) 💚 5.772
Methods 100.0% (19/19) 💚 8.591
Lines 98.945% (844/853) 👍 11.896
Conditionals 100.0% (0/0) 💚

@andrewkroh andrewkroh merged commit cfa295b into elastic:main Sep 20, 2023
4 checks passed
@elasticmachine
Copy link

Package symantec_endpoint - 2.11.0 containing this change is available at https://epr.elastic.co/search?package=symantec_endpoint

1 similar comment
@elasticmachine
Copy link

Package symantec_endpoint - 2.11.0 containing this change is available at https://epr.elastic.co/search?package=symantec_endpoint

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[symantec_endpoint] log.syslog.version definition conflicts with ECS
3 participants