Skip to content

[sysdig] Add Agentless Deployment Support #19355

Closed

Description

@moxarth-rathod

Description

Add agentless support to the sysdig.

Requirements

Following the established Phase I pattern, for each integration see the Onboarding Integration Guide.

1. Technical implementation

  • Update integration manifest.yml to enable agentless deployment mode ()
  • Update integration documentation with agentless deployment instructions
  • Update changelog.md

Example reference: #13367

2. Performance documentation

  • Test and document throughput in agentless (requires access to vendor environment and/or sample data)
  • Document specific metrics for each integration. For example/where possible:
    • API response time: Average time for vendor API calls to complete
    • Events processed per minute: How many log entries/events the integration can handle
    • Error rates: Percentage of failed API calls or data processing errors
    • Container resource usage: CPU and memory consumption under typical load
    • Vendor-specific limits: Rate limiting thresholds and API quotas

Example documentation format: "Crowdstrike Falcon Intelligence: 200ms avg API response, 5,000 events/min, 0.1% error rate, 512MB RAM/0.5CPU, 1000 API calls/hour limit"

Dependencies

  • Agentless infrastructure GA readiness (still in beta)
  • Input compatibility: Currently agentless is optimized for httpjson and cel inputs
  • UX enhancement: Add agentless deployment filter/toggle to integrations catalog page for better discoverability

Activity

  1. added
    Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]
    Team:SDE-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]
    on Jun 3, 2026
  2. infra-vault-gh-plugin-prod commented on Jun 3, 2026

    @infra-vault-gh-plugin-prod

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

  3. github-actions commented on Jun 3, 2026

    @github-actions
    Contributor

    tl;dr: I recommend enabling agentless deployment for Sysdig at the package level, but documenting it as API/CEL-focused support while keeping Alerts (http_endpoint) as agent-based behavior. This matches existing patterns in this repo for mixed-input integrations.

    Recommendation

    Enable deployment_modes.agentless in packages/sysdig/manifest.yml (beta metadata included), keep current inputs unchanged, and update Sysdig docs to clearly separate:

    1. Agentless-capable API polling streams (event, cspm, vulnerability via CEL)
    2. Agent-based webhook stream (alerts via http_endpoint)
    Findings
    • packages/sysdig/manifest.yml:41-51 has one policy template with http_endpoint + cel inputs and no deployment_modes.
    • packages/sysdig/data_stream/alerts/manifest.yml:4-25 is input: http_endpoint and requires listener settings (listen_address, listen_port) — this is inbound webhook style.
    • packages/sysdig/data_stream/event/manifest.yml:4-8, packages/sysdig/data_stream/cspm/manifest.yml:4-8, packages/sysdig/data_stream/vulnerability/manifest.yml:4-8 are all input: cel API polling streams.
    • packages/sysdig/docs/README.md:23-27 currently has only Agent-based installation; :33-39 makes Alerts webhook sound mandatory before API setup.
    • Repo precedent for agentless metadata:
      • packages/forgerock/manifest.yml:20-28 (deployment_modes.default + deployment_modes.agentless with release/org/division/team)
      • packages/darktrace/manifest.yml:27-35 same structure.
    • Repo precedent for mixed push + polling inputs with agentless enabled:
      • packages/zscaler_zia/manifest.yml:72-80 enables agentless at policy level,
      • while still containing tcp/http_endpoint (:82, :129) and cel (:191) inputs.
    • Docs precedent for agentless language:
      • packages/forgerock/docs/README.md:5-8 has a standard “Agentless Enabled Integration” section and beta/cloud caveat.

    GitHub context limitation: issue/related-item bodies are integrity-filtered in this environment, so this triage is based on repository evidence only.

    Verification

    I ran workspace commands to verify current package/test layout and local tooling availability:

    $ ls -1 packages/sysdig/data_stream/*/_dev/test/system/test-default-config.yml
    packages/sysdig/data_stream/alerts/_dev/test/system/test-default-config.yml
    packages/sysdig/data_stream/cspm/_dev/test/system/test-default-config.yml
    packages/sysdig/data_stream/event/_dev/test/system/test-default-config.yml
    packages/sysdig/data_stream/vulnerability/_dev/test/system/test-default-config.yml
    $ elastic-package check -C packages/sysdig -v
    bash: elastic-package: command not found
    Detailed Action Plan
    1. Update packages/sysdig/manifest.yml under policy_templates[0] (:41+) to add:
      • deployment_modes.default.enabled: true
      • deployment_modes.agentless.enabled: true
      • deployment_modes.agentless.release: beta
      • deployment_modes.agentless.organization/division/team (follow team convention used by forgerock/darktrace).
    2. Bump Sysdig package version (minor bump recommended for capability addition), and add a changelog entry in packages/sysdig/changelog.yml as type: enhancement.
    3. Update docs source packages/sysdig/_dev/build/docs/README.md:
      • Add agentless section (using established wording/caveats similar to forgerock/docs/README.md:5-8).
      • Split setup guidance into API/CEL vs Alerts webhook so users don’t assume webhook is required for agentless.
    4. Regenerate docs output so packages/sysdig/docs/README.md stays in sync.
    5. Validate package with standard package checks in an environment with elastic-package available (recommended gate before merge).

    Suggested scope decision: keep current mixed-input policy template (least invasive), and make support boundaries explicit in docs rather than restructuring templates in this issue.

    Related Items
    Type Link Relevance
    Issue #19355 Current triage target
    File packages/sysdig/manifest.yml:41-51 Missing deployment_modes; contains mixed http_endpoint + cel inputs
    File packages/sysdig/data_stream/alerts/manifest.yml:4-25 Webhook/listener-style stream likely agent-based path
    Files packages/sysdig/data_stream/{event,cspm,vulnerability}/manifest.yml:4-8 API polling streams (cel) suitable for agentless mode
    File packages/sysdig/docs/README.md:23-39 Current docs are agent-based-only and webhook-first
    File packages/forgerock/manifest.yml:20-28 Canonical agentless metadata pattern
    PR #19205 Prior “Enable Agentless deployment” precedent (forgerock/changelog.yml:9-11)
    File packages/zscaler_zia/manifest.yml:72-80,82,129,191 Precedent for agentless + mixed push/polling inputs
    Web https://www.elastic.co/guide/en/serverless/current/security-agentless-integrations.html Agentless docs reference used in multiple package READMEs

    Note

    🔒 Integrity filter blocked 4 items

    The following items were blocked because they don't meet the GitHub integrity level.

    • #13085 search_pull_requests: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19355 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #17973 search_issues: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".
    • #19355 issue_read: has lower integrity than agent requires. The agent cannot read data with integrity below "approved".

    To allow these resources, lower min-integrity in your GitHub frontmatter:

    tools:
      github:
        min-integrity: approved  # merged | approved | unapproved | none

    What is this? | From workflow: Issue Triage

    Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Integration:sysdigSysdigTeam:SDE-CrestCrest developers on the Security Integrations team [elastic/sit-crest-contractors]Team:Security-Service IntegrationsSecurity Service Integrations team [elastic/security-service-integrations]enhancementNew feature or request

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    ⌂ 换网址