BowerSecurity_CL columns
Every Sentinel path writes to one table, BowerSecurity_CL. SentinelSchema.Default in
src/Bower.Dcr defines the columns, and deploy/bicep/main.bicep and the Azure Monitor Agent
rule (deploy/bicep/ama-syslog-dcr.bicep) follow it. Tests fail when any of them differ, and a
test checks that this page lists the same columns in the same order.
The schema only ever grows: no column is renamed or retyped, and schemaVersion stays 1.0.0.
| Column | Type | From the envelope |
|---|---|---|
TimeGenerated | datetime | timeGenerated |
EventId | string | eventId |
EventOriginalId | string | eventOriginalId |
EventCategory | string | eventCategory |
EventType | string | eventType |
EventAction | string | eventAction |
EventResult | string | eventResult |
EventSeverity | string | eventSeverity |
ApplicationName | string | application.name |
ApplicationEnvironment | string | application.environment |
ActorUserId | string | actor.userId |
ActorUsername | string | actor.username |
SourceIpAddress | string | source.ipAddress |
CorrelationId | string | request.correlationId |
PolicyId | string | security.policyId |
PolicyVersion | string | security.policyVersion |
PolicyHash | string | security.policyHash |
ValueScore | int | security.valueScore |
CollectorId | string | collector.id |
PrivacyDetected | dynamic | privacy.detected |
Labels | dynamic | labels |
RawEnvelope | dynamic | the whole envelope |
TimeObserved | datetime | timeObserved |
EventOutcomeReason | string | eventOutcomeReason |
Target | dynamic | target |
Change | dynamic | change |
Attributes | dynamic | attributes |
Origin | dynamic | collector.origin, or the agent's host on the Azure Monitor Agent path |
Origin
Origin says where an event entered Bower, so a row can be traced to the system that wrote it
during an investigation. The producer cannot set it. Bower rebuilds collector on every event,
so a value an application puts there is replaced.
Origin.kind | Set by | Fields |
|---|---|---|
cloudwatch-logs | the collector, from the cloud forwarder's X-Bower-Origin header | logGroup, logStream (the CloudWatch Logs group and stream the line was written to, for example the instance ID) |
ama-syslog | the collection rule, from the row Azure Monitor Agent made | host (the agent's Computer) |
| (empty) | any other path: the producer is already identified by its ingest token |
cloudwatch-logs. The collector honours the header only from producers listed inBOWER_ORIGIN_PRODUCERS, which should be thebower-cloudagent's tokens-file producer ID. A header from any other producer is ignored. The log group and stream identify the server that wrote the line only as far as your IAM policies allow: limitlogs:PutLogEventsto each server's own stream (see the CloudWatch agent quick start).ama-syslog. The host is the machine the agent ran on, not a value in the message. A local account can still send a forged message on that host (see the trust boundary), but the row names the host it came from.
Live on 10-11-2026 (#249), Azure Monitor Agent 1.45.1 on Ubuntu 24.04: a row sent through
ama-syslog had Origin {"kind":"ama-syslog","host":"<the VM>"}. A row forged with logger by
nobody, whose envelope claimed a CloudWatch Logs origin, had the same Origin: the agent's real
host, not the claim. A record uploaded through the Logs Ingestion rule kept its
collector.origin (cloudwatch-logs, log group and stream) in Origin.
Example query, rows per server in the last day:
BowerSecurity_CL
| where TimeGenerated > ago(1d)
| summarize Rows = count() by Kind = tostring(Origin.kind),
Server = coalesce(tostring(Origin.host), tostring(Origin.logStream))
The two Azure paths, compared
Live on 11-11-2026 (#249), one VM sent the same envelope once through ama-syslog and once
through azure-logs-ingestion (managed identity) into the same table. Every typed column was
equal, including TimeGenerated to the millisecond, the empty strings in EventOriginalId and
ActorUserId, nulls in the dynamic columns, and accented text in EventOutcomeReason. The
differences:
| Column | ama-syslog | azure-logs-ingestion |
|---|---|---|
Origin | {"kind":"ama-syslog","host":"<the VM>"} | empty |
_ResourceId | the VM's resource ID | empty |
RawEnvelope | only the keys the envelope has | also eventOriginalId ("") and labels, privacy, target, change, attributes (null) |
The RawEnvelope difference is the Logs Ingestion stream declaring every column: pack_all()
packs declared columns that are absent too. Read optional envelope fields with isempty() or
isnull() rather than testing for the key, and the query works on both paths.