Skip to content

[pull] master from DataDog:master#525

Merged
pull[bot] merged 2 commits into
ConnectionMaster:masterfrom
DataDog:master
May 8, 2026
Merged

[pull] master from DataDog:master#525
pull[bot] merged 2 commits into
ConnectionMaster:masterfrom
DataDog:master

Conversation

@pull

@pull pull Bot commented May 8, 2026

Copy link
Copy Markdown

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )

joelmarcotte and others added 2 commits May 8, 2026 14:08
* [postgres] Qualify diagnose category with instance host to distinguish multiple instances

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* [postgres] Add changelog entry for #23620

Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>

* [postgres] Use `instance=<host>` prefix for diagnose category

Replaces the `postgres:<host>` prefix on the diagnose category with
`instance=<host>` so the host attribution reads as a key/value pair.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* [postgres] Use canonical database_identifier in diagnose category

Replaces the hand-built `host:port` value with `check.database_identifier`,
the canonical instance identifier already used in metadata, health events,
and statement payloads. Categories now match what's surfaced in the UI and
other logs/debug channels.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* [postgres] Fall back to host:port when database_identifier is unavailable

`database_identifier` resolves a Template over `_config` and `tags`, which
can fail when the very config diagnose is meant to surface is broken. Wrap
it in a try/except and fall back to the raw `host:port` so the diagnose
category is always populated.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
…ine (#23349)

* Map event_id to ocsf.metadata.correlation_uid in all sub-pipelines

* use uid instead of correlation_uid

* Map exe and comm to OCSF actor process fields in Network Activity pipeline

Add exe -> ocsf.actor.process.path and comm -> ocsf.actor.process.name
mappings to the Network Activity [4001] Syscall sub-pipeline.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Add actor.process expectations to Network Activity SYSCALL test

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

* Add host profile and full actor mappings to Network Activity SYSCALL pipeline

Network Activity (4001) has no native actor attribute, which caused the
earlier exe/comm -> ocsf.actor.process.* mappings to be rejected by the
schema validator. Declaring profiles: [host] on the SYSCALL->4001
schema-processor makes actor (and device) valid attributes on the class.

Also expand actor mappings for parity with the FS-from-SYSCALL
sub-pipeline: pid, uid/UID, auid/AUID, ses, tty.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

* Add metadata.profiles to Network Activity SYSCALL test expectation

The schema-processor emits ocsf.metadata.profiles: [host] when the host
profile is declared on the schema. Mirror the format used by IAM
sub-pipeline tests (e.g. line 141).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
@pull pull Bot locked and limited conversation to collaborators May 8, 2026
@pull pull Bot added the ⤵️ pull label May 8, 2026
@pull pull Bot merged commit 53f43d3 into ConnectionMaster:master May 8, 2026
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants