Fix a couple of IAST modules to use the IGSpanInfo in the event over the active span

[mcculls]

Motivation

Avoids use of activeSpan when the span is already available in the gateway event.

Contributor Checklist

• Format the title according to the contribution guidelines
• Assign the type: and (comp: or inst:) labels in addition to any other useful labels
• Avoid using close, fix, or any linking keywords when referencing an issue
  Use solves instead, and assign the PR milestone to the issue
• Update the CODEOWNERS file on source file addition, migration, or deletion
• Update public documentation with any new configuration flags or behaviors
• Once approved, use merge queue to merge the PR

Jira ticket: [PROJ-IDENT]

[PerfectSlayer]

Thanks for the follow up changes

[datadog-official]

More details

The cast (AgentSpan) igSpanInfo is safe for all production inputs: AgentSpan extends IGSpanInfo and no class in this codebase implements IGSpanInfo without also implementing AgentSpan (verified by exhaustive grep). Null is handled correctly — an NPE from igSpanInfo.getTags() on line 39 (before the cast on line 51) is swallowed by the existing catch (Throwable e) block, so the 'exception not thrown if igSpanInfo is null' test continues to pass. No behavioral regressions found.

Was this helpful? React 👍 or 👎

_{📊 Validated against 5 scenarios · Open Bits AI session}

_{🤖 Datadog Autotest · Commit 9965175 · What is Autotest? · Any feedback? Reach out in #autotest}

[datadog-official]

🎯 Code Coverage (details)
• Patch Coverage: 100.00%
• Overall Coverage: 79.99% (+22.94%)

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9965175 | Docs | Datadog PR Page | Give us feedback!}

[dd-octo-sts]

🟢 Java Benchmark SLOs — All performance SLOs passed

Suite	Status
Startup	🟢 pass

SLO thresholds are defined here based on automatically generated metrics. A warning is raised when results are within 5% of the threshold.

PR vs. master results

Scenario	Candidate	master	Δ (95% CI of mean)
startup:insecure-bank:iast:Agent	14.01 s	13.93 s	[-0.1%; +1.3%] (no difference)
startup:insecure-bank:tracing:Agent	12.96 s	13.01 s	[-1.2%; +0.3%] (no difference)
startup:petclinic:appsec:Agent	16.88 s	16.05 s	[+0.7%; +9.6%] (maybe worse)
startup:petclinic:iast:Agent	16.87 s	16.98 s	[-1.5%; +0.2%] (no difference)
startup:petclinic:profiling:Agent	16.49 s	16.73 s	[-2.5%; -0.3%] (maybe better)
startup:petclinic:sca:Agent	16.92 s	16.86 s	[-0.7%; +1.3%] (no difference)
startup:petclinic:tracing:Agent	16.09 s	16.24 s	[-1.9%; -0.0%] (maybe better)

Commit: 9965175c · CI Pipeline · Benchmarking Platform UI

---

Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion.

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-14 12:43:01 UTC ℹ️ Start processing command /merge

---

2026-07-14 12:43:06 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-14 14:43:41 UTC ❌ MergeQueue: The build pipeline has timeout

The merge request has been interrupted because the build 7085489522989408789 took longer than expected. The current limit for the base branch 'master' is 120 minutes.

Possible reasons:

• some mandatory checkruns are failing:
  • Check pull request labels
  • Check pull requests
  • Enforce Groovy migration

[dd-octo-sts]

/merge

[gh-worker-devflow-routing-ef8351]

View all feedbacks in Devflow UI.

2026-07-14 14:44:06 UTC ℹ️ Start processing command /merge

---

2026-07-14 14:44:11 UTC ℹ️ MergeQueue: pull request added to the queue

The expected merge time in master is approximately 2h (p90).

---

2026-07-14 15:43:58 UTC ℹ️ MergeQueue: This merge request was merged