[sysdig] Add agentless deployment#19470
Conversation
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
🚀 Benchmarks reportTo see the full report comment with |
|
Pinging @elastic/security-service-integrations (Team:Security-Service Integrations) |
| default: | ||
| enabled: true | ||
| agentless: | ||
| enabled: true |
| - script: | ||
| description: Remove Sysdig placeholder and empty values from content fields before type conversion. | ||
| tag: script_sanitize_content_fields | ||
| lang: painless |
There was a problem hiding this comment.
Do we need to do this pass again? Since you added a processor to raw JSON at the beginning.
| link: https://github.com/elastic/integrations/pull/19470 | ||
| - description: Fix handling of null values in string for event data stream. | ||
| type: bugfix | ||
| link: https://github.com/elastic/integrations/pull/1 |
There was a problem hiding this comment.
| link: https://github.com/elastic/integrations/pull/1 | |
| link: https://github.com/elastic/integrations/pull/19470 |
There was a problem hiding this comment.
@moxarth-rathod, looks like this isn't fixed and CI failing due to this. Can you please check
|
Changelog link mismatch — expected
Tip If expected, add the |
💔 Build Failed
Failed CI StepsHistory
|
Proposed commit message
Checklist
changelog.ymlfile.How to test this PR locally
Related issues