Skip to content

Conversation

@andrewkroh
Copy link
Member

@andrewkroh andrewkroh commented Apr 17, 2025

Proposed commit message

Falco was using data type 'text' for the process.group.id and
process.group.name fields, but those fields are defined as 'keyword' in
ECS leading to conflicts with other packages that are following ECS.

I modified the field definitions to use 'external: ecs' where possible.
And removed unused attributes from fields.yml files.

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.
  • I have verified that any added dashboard complies with Kibana's Dashboard good practices

Author's Checklist

  • [ ]

How to test this PR locally

Related issues

Screenshots

Falco was using data type 'text' for the process.group.id and
process.group.name fields, but those fields are defined as 'keyword'
in ECS leading to conflicts with other packages that are following ECS.

I modified the field definitions to use 'external: ecs' where possible.
And removed unused attributes from fields.yml files.
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@andrewkroh andrewkroh marked this pull request as ready for review April 17, 2025 15:28
@andrewkroh andrewkroh requested a review from a team as a code owner April 17, 2025 15:28
@andrewkroh andrewkroh added Integration:falco Falco Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations] labels Apr 17, 2025
@elasticmachine
Copy link

Pinging @elastic/security-service-integrations (Team:Security-Service Integrations)

description: Preserved Falco field
external: ecs
- name: event.dataset
type: constant_keyword
Copy link
Contributor

@ShourieG ShourieG Apr 22, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any specific reason we are not removing type: constant_keyword here, since we are already referencing ecs ?

external: ecs
value: falco.alerts
- name: event.module
type: constant_keyword
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same query as above

Copy link
Contributor

@ShourieG ShourieG left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@andrewkroh andrewkroh enabled auto-merge (squash) April 24, 2025 02:40
@elastic-sonarqube
Copy link

@elasticmachine
Copy link

💚 Build Succeeded

History

@andrewkroh andrewkroh merged commit 3467528 into elastic:main Apr 24, 2025
7 checks passed
@elastic-vault-github-plugin-prod

Package falco - 1.3.1 containing this change is available at https://epr.elastic.co/package/falco/1.3.1/

efd6 added a commit to efd6/integrations that referenced this pull request Jul 15, 2025
This essentially replays the field definitions changes in elastic#13589 and elastic#13589
but for the alerts_agent data stream.
efd6 added a commit to efd6/integrations that referenced this pull request Jul 15, 2025
This essentially replays the field definitions changes in elastic#13589 and elastic#13589
but for the alerts_agent data stream.
efd6 added a commit that referenced this pull request Jul 15, 2025
This essentially replays the field definitions changes in #13589 and #13589
but for the alerts_agent data stream.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Integration:falco Falco Team:Security-Service Integrations Security Service Integrations team [elastic/security-service-integrations]

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants