...
| Info | ||
|---|---|---|
| ||
This example shows the events in Snare format. The first four fields are the event header and may be formatted differently in other event formats. |
Example with checksums:
1. Formats
The following formats are possible formats for telemetry events:
...
| Field | Type | Description |
|---|---|---|
| Hostname | String | The host name of the originating computer. |
| EventType | String | TelemetryLog - the type of event generated. |
SeverityLevel | Integer | The severity level (Criticality) of the generated event. |
| TimeCreated | Datetime | The time at which the telemetry event was . (YYYY-MM-DDT hh:mm:ss) |
| MetricType | String | This is the hardware component source of the event; Events from the CPU, Disk, Memory or Network can be collected and are labelled as CPU, DSK, MEM or NET respectively. |
InstanceName | String | The name of the hardware interface the event is sourced. For example, if events from the Disk (DSK) are collected, there may be multiple storage interfaces present such as HarddiskVolume1, HarddiskVolume2, etc. |
| EventName | String | The name of the metric of the hardware interface. Given a hardware interface named by it's InstanceName, the EventName denotes the metric of the interface that is collected. Eg, EventName: ' % Free Space' from InstanceName:'HarddiskVolume1' |
| Value | Float | The value of the metric. |
| EventChecksum (Optional) | String | The calculated digest (checksum) valueSHA3-512 hash of the event excluding the EventChecksum field; this is additional optional data that may be set in the Event Options settings of the Agent. |
| EventSourceId (Optional) | Integer | The unique ID of the eventConfigurable ID/string for identifying the agent/host. This is also optional data like the EventChecksum and is selected likewise. |
...