-
Notifications
You must be signed in to change notification settings - Fork 474
[proofpoint_itm] Initial release of Proofpoint ITM #13153
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
Conversation
/test |
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
🚀 Benchmarks reportTo see the full report comment with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This test only exercises a single API collections. We should make it collect at least two in order to test pagination.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we have only 2 query params, i.e, since
, and limit
, we are unable to have pagination call in system test.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's unfortunate. Can you confirm that it has been tested against a real endpoint then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not convinced that the situation here prevents that. If you have a risingValue
timestamp that cannot be reasonably expected to exist, say "3025-03-01T12:00:00Z", then you can filter the request query on since
starting with a 2 and have the second rule filter on starting with a 3.
packages/proofpoint_itm/data_stream/report/_dev/test/pipeline/test-alert.log
Outdated
Show resolved
Hide resolved
packages/proofpoint_itm/data_stream/report/agent/stream/cel.yml.hbs
Outdated
Show resolved
Hide resolved
/test |
/test |
💚 Build Succeeded
History
|
|
@muskan-agarwal26 Before merge, can you note where the test data input cases were obtained from? For both the system and pipeline tests. Proposed commit message body:
with |
@efd6 |
Package proofpoint_itm - 0.1.0 containing this change is available at https://epr.elastic.co/package/proofpoint_itm/0.1.0/ |
Add report data stream including collection and ingest logic with mapping to the ECS, and dashboard visualisations. Pipeline and system test data have been extracted from Splunk and sanitized to ensure data integrity.
Add report data stream including collection and ingest logic with mapping to the ECS, and dashboard visualisations. Pipeline and system test data have been extracted from Splunk and sanitized to ensure data integrity.
Add report data stream including collection and ingest logic with mapping to the ECS, and dashboard visualisations. Pipeline and system test data have been extracted from Splunk and sanitized to ensure data integrity.
Add report data stream including collection and ingest logic with mapping to the ECS, and dashboard visualisations. Pipeline and system test data have been extracted from Splunk and sanitized to ensure data integrity.
Proposed commit message
Checklist
changelog.yml
file.How to test this PR locally
Screenshots