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

digital_guardian: fix mapping of dg_alert.alert_wb field and add export profile guid #12818

Merged
merged 4 commits into from
Feb 20, 2025

Conversation

efd6
Copy link
Contributor

@efd6 efd6 commented Feb 18, 2025

Proposed commit message

See title.

Note

Alternative approach is to keep the field type as an integer and map to yes/no to 1/0. This is not ideal.

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

@efd6 efd6 added bugfix Pull request that fixes a bug issue Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations] Integration:digital_guardian Digital Guardian labels Feb 18, 2025
@efd6 efd6 self-assigned this Feb 18, 2025
@efd6 efd6 force-pushed the 12441-digital_guardian branch from 7807ffa to 3358e4b Compare February 18, 2025 03:33
- name: dg_alert.alert_wb
type: integer
type: keyword
Copy link
Contributor Author

Choose a reason for hiding this comment

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

The alternative here is to keep this as an integer and map to 0/1.

@efd6 efd6 force-pushed the 12441-digital_guardian branch from 3358e4b to de4ba06 Compare February 18, 2025 03:50
@efd6 efd6 changed the title digital_guardian: fix mapping of dg_alert.alert_wb field digital_guardian: fix mapping of dg_alert.alert_wb field and add export profile guid Feb 18, 2025
@elastic-vault-github-plugin-prod

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@efd6 efd6 marked this pull request as ready for review February 18, 2025 04:21
@efd6 efd6 requested a review from a team as a code owner February 18, 2025 04:21
@elasticmachine
Copy link

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

Comment on lines 16 to 24
- name: dg_alert.alert_etl
type: keyword
description: Alert ETL
- name: dg_alert.alert_etu
type: date
description: Alert ETU
- name: dg_alert.alert_ur
type: date
description: Alert UR
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
- name: dg_alert.alert_etl
type: keyword
description: Alert ETL
- name: dg_alert.alert_etu
type: date
description: Alert ETU
- name: dg_alert.alert_ur
type: date
description: Alert UR
- name: dg_alert.alert_etl
type: date
description: Alert ETL
- name: dg_alert.alert_etu
type: date
description: Alert ETU
- name: dg_alert.alert_ur
type: keyword
description: Alert UR

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Thanks

@elasticmachine
Copy link

💚 Build Succeeded

History

cc @efd6

@efd6 efd6 merged commit 366b4ab into elastic:main Feb 20, 2025
6 checks passed
@elastic-vault-github-plugin-prod

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bugfix Pull request that fixes a bug issue Integration:digital_guardian Digital Guardian Team:Security-Service Integrations Security Service Integrations Team [elastic/security-service-integrations]
Projects
None yet
3 participants