Skip to content

[checkpoint] Move last update time - #17633

Merged
kgeller merged 24 commits into
elastic:mainfrom
ash-darin:move_last_update_time
Apr 28, 2026
Merged

[checkpoint] Move last update time#17633
kgeller merged 24 commits into
elastic:mainfrom
ash-darin:move_last_update_time

Conversation

@ash-darin

@ash-darin ash-darin commented Mar 3, 2026

Copy link
Copy Markdown
Contributor

Enhancement

Proposed commit message

Events may include last_hit_time and lastupdatetime.

Lastupdatetime is in all observed cases later than last_hit_time and should therefore mark the end of the event. The current order of processors parses last_hit_time as event.end after lastupdatetime though, therefore overwriting the date parsed from lastupdatetime.

This PR changes this order and additionally removes the attempt to parse the date as ISO, as the dates of last_hit_time and lastupdatetime are always UNIX Timestamps.

This documentation
describes "lastupdatetime" as an "integer".

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.

How to test this PR locally

Checking this is problematic, as the sourcefields are both discarded.

@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

Reviewers

Buildkite won't run for external contributors automatically; you need to add a comment:

  • /test : will kick off a build in Buildkite.

NOTE: https://github.com/elastic/integrations/blob/main/.buildkite/pull-requests.json contains all those details.

@ash-darin ash-darin changed the title Move last update time Mar 3, 2026
@andrewkroh andrewkroh added the Integration:checkpoint Check Point label Mar 3, 2026

@ash-darin ash-darin left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

Resolved conflict of versioning with other approved patch.

Comment thread packages/checkpoint/changelog.yml
ash-darin and others added 2 commits April 9, 2026 13:57
@ash-darin
ash-darin marked this pull request as ready for review April 9, 2026 11:58
@ash-darin
ash-darin requested a review from a team as a code owner April 9, 2026 11:58
@andrewkroh andrewkroh added the Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience] label Apr 9, 2026
@elasticmachine

Copy link
Copy Markdown

Pinging @elastic/integration-experience (Team:Integration-Experience)

@kgeller

kgeller commented Apr 15, 2026

Copy link
Copy Markdown
Member

/test

@ash-darin

ash-darin commented Apr 16, 2026

Copy link
Copy Markdown
Contributor Author

Apparently I can not trigger tests.

@kgeller I forgot to update the manifest, sorry about that. I now rectified it.

@kgeller

kgeller commented Apr 16, 2026

Copy link
Copy Markdown
Member

/test

@kgeller

kgeller commented Apr 16, 2026

Copy link
Copy Markdown
Member

Apparently I can not trigger tests.

@kgeller I forgot to update the manifest, sorry about that. I now rectified it.

Thanks for fixing up the manifest!

Looks like now you're running into actual test failures. I'd suggest running those locally and ensuring ✅ and then I can get CI to go green as well. The elastic-package test command has some pretty thorough docs https://github.com/elastic/elastic-package/tree/main?tab=readme-ov-file#elastic-package-test

Test suite complains:

"event.risk_score"'s Go type, string, does not match the expected field type: float 

But fields in checkpoint are always strings
Comment thread packages/checkpoint/data_stream/firewall/fields/fields.yml
Test case became malformed in the anonymization process. Added Quotation marks.
@kgeller

kgeller commented Apr 28, 2026

Copy link
Copy Markdown
Member

/test

Comment thread packages/checkpoint/docs/README.md
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

🚀 Benchmarks report

To see the full report comment with /test benchmark fullreport

@elasticmachine

Copy link
Copy Markdown

💚 Build Succeeded

History

@kgeller kgeller left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

LGTM!

@ash-darin thanks for doing that additional cleanup of the field addition and convert processor!

@kgeller
kgeller merged commit ab4a347 into elastic:main Apr 28, 2026
5 checks passed
@elastic-vault-github-plugin-prod

Copy link
Copy Markdown
Contributor

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

@andrewkroh andrewkroh added the documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. label Apr 29, 2026
@ash-darin
ash-darin deleted the move_last_update_time branch April 30, 2026 15:07
herrBez pushed a commit to herrBez/integrations that referenced this pull request Jun 1, 2026
* Change parsing order

* remove unecessary time check

* provide log message

* undo previous error, fix correct timestamp

* Incement version counter

* Add Changelog message

* Update PR number

* Update packages/checkpoint/changelog.yml

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>

* Update version in manifest

* define missing field

* convert app_risk to float

Test suite complains:

"event.risk_score"'s Go type, string, does not match the expected field type: float 

But fields in checkpoint are always strings

* Update test-checkpoint.log

Test case became malformed in the anonymization process. Added Quotation marks.

* regenerated the readme

---------

Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
Co-authored-by: Kylie Meli <kylie.geller@elastic.co>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation. Applied to PRs that modify *.md files. Integration:checkpoint Check Point Team:Integration-Experience Security Integrations Integration Experience [elastic/integration-experience]

4 participants