TopicsReceivers
Receivers
Generic HTTPS endpoint
Posts a JSON array or newline-delimited JSON, with a bearer token, basic authentication, a custom header, or
an HMAC-SHA256 signature of the body (X-Signature-256: sha256=<hex>, sent with X-Timestamp; requests
signed this way are not compressed). Endpoint: the full https:// URL.
Microsoft Sentinel
The Logs Ingestion API with an Entra app registration (client credentials), which needs the role Monitoring
Metrics Publisher on the data collection rule. Endpoint: the logs ingestion endpoint of the data collection
rule (its JSON view), or of the data collection endpoint where you use one.
siem/sentinel/PxmLogExporter.kql describes the custom table, data
collection rule and parser function to create, and the role to assign. The receiver signs in at
login.microsoftonline.com, so it serves workspaces in Azure’s public cloud only.
Splunk HTTP Event Collector
/services/collector/event with the HEC token; siem/splunk/props.conf defines
the sourcetype pxm:logexporter. Endpoint: the HEC address, https://<host>:<port>. Create the token with
indexer acknowledgement off: the exporter sends no channel identifier, which Splunk requires when
acknowledgement is on. Install props.conf in an app on the search heads, for the fields; for events from the
TLS stream or from files, also on the indexers or heavy forwarders that receive them, for the line breaking and
the timestamps. Events through the HTTP Event Collector need neither, since the exporter sends each one whole
with its time. The sourcetype also reads newline-delimited JSON from the TLS stream sink. For the syslog
format, put a syslog collector in front of Splunk that passes on the message part of each message, which is
the event’s JSON.
Azure Event Hubs
The REST endpoint of an event hub with a shared access policy that may send. Endpoint: the namespace host,
<namespace>.servicebus.windows.net. For Sentinel, the Microsoft Sentinel receiver is the direct path. Azure
Monitor can also ingest from Event Hubs
into a Log Analytics workspace, with requirements Microsoft sets.
TLS stream
The TLS stream sink sends syslog as RFC 5424 messages, each framed by its length in bytes (RFC 5425):
<PRI>1 TIMESTAMP HOSTNAME APP-NAME - MSGID STRUCTURED-DATA {the event's JSON}
PRI combines Syslog facility with the event’s severity, TIMESTAMP is the event’s time in UTC with
milliseconds, HOSTNAME is the tenant’s host, APP-NAME is Syslog app name and MSGID is the event’s name.
STRUCTURED-DATA names the software in the element origin, whatever APP-NAME says, and carries the event’s
id, seq, tenant and environment in the element pxmlogexporter@67183, so a collector that reads
structured data can route events or drop repeats without reading the JSON:
[origin enterpriseId="67183" software="pxmlogexporter" swVersion="1.0.0"][pxmlogexporter@67183 id="02020202-0202-4202-8202-020202020202" seq="2" tenant="abc123" environment="production"]
enterpriseId is egos.tech’s private enterprise number and swVersion the version of the exporter that
recorded the event. A parameter whose field the event lacks is left out; a value loses its control characters
and is cut to 255 bytes. While Mark messages as UTF-8 is on, a byte order mark comes before the JSON. A
message stays within 8,192 bytes. In the newline-delimited JSON format, each event is one line.
Centric PXM™ is a trademark of Centric Software, Inc.