[Serverless security] [akamai] Failing test daily: policy test: test-preserve.yml in akamai.siem_otel

Open Beginner friendly
#21,338 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
handlebars
Domain
testing

Research direction

Start with the policy test for akamai.siem_otel and its test-preserve.yml fixture, then compare the expected policy with the failing diff from Buildkite build 2075. Run the policy test locally and determine whether the fixture or generated policy should change; done means the test passes without losing the preserve-policy behavior.

Written by the indexing model from the issue text.

Description

automation flaky-test Integration:akamai Team:Security-Service Integrations
  • Serverless: security
  • Package: akamai
  • Failing test: policy test: test-preserve.yml
  • DataStream: siem_otel
  • Owners:
    • @elastic/security-service-integrations
    • @elastic/sit-crest-contractors

Error:

unexpected content in policy: --- want
+++ got
@@ -4,4 +4,92 @@
     elasticsearch/componentid-0:
+        bulk_response_filter_path: errors,items.*.error,items.*.status,items.*.failure_store
+        compression: gzip
+        compression_params:
+            level: 1
         endpoints:
             - https://elasticsearch:9200
+        include_source_on_error: true
+        logs_dynamic_id:
+            enabled: true
+        logs_dynamic_pipeline:
+            enabled: true
+        max_conns_per_host: 1
+        retry:
+            enabled: true
+            initial_interval: 1s
+            max_interval: 60s
+            max_retries: 3
+            retry_on_document_status:
+                - 429
+                - 500
+                - 501
+                - 502
+                - 503
+                - 504
+                - 505
+                - 506
+                - 507
+                - 508
+                - 510
+                - 511
+            retry_on_status:
+

First build failed: https://buildkite.com/elastic/integrations-serverless/builds/2075

Dominant language
Handlebars
Stars
334
Forks
652
Avg merge
1d 22h
Merged PRs (30d)
241

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from elastic/integrations

All issues in elastic/integrations

Similar issues

More Testing & QA issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.