feat(logs): add NLog integration
#5176
Draft
@sentry/warden / warden
completed
May 1, 2026 in 1m 35s
1 issue
Low
DateTimeOffset constructed from DateTime may use unintended local offset - `src/Sentry.NLog/SentryTarget.Structured.cs:10`
The constructor new DateTimeOffset(logEvent.TimeStamp) infers the offset from the DateTime's Kind: Local/Unspecified uses the machine's local offset, while Utc uses zero. NLog's default TimeSource produces local DateTimes, so the resulting offset will reflect server-local time, which can be inconsistent across deployments and may cause confusion when correlating Sentry log timestamps. If a custom TimeSource yields DateTimeKind.Unspecified it will silently be treated as local. Consider normalizing to UTC explicitly.
4 skills analyzed
| Skill | Findings | Duration | Cost |
|---|---|---|---|
| code-review | 0 | 1m 34s | $1.35 |
| find-bugs | 1 | 53.0s | $1.35 |
| gha-security-review | 0 | 26.8s | $2.27 |
| security-review | 0 | 1m 8s | $1.23 |
Duration: 4m 2s · Tokens: 1.2M in / 3.3k out · Cost: $6.20
Loading