EventData Class
The Azure event log entries are of type EventData.
Variables are only populated by the server, and will be ignored when sending a request.
- Inheritance
-
azure.mgmt.monitor._serialization.ModelEventData
Constructor
EventData(**kwargs: Any)
Variables
Name | Description |
---|---|
authorization
|
The sender authorization information. |
claims
|
key value pairs to identify ARM permissions. |
caller
|
the email address of the user who has performed the operation, the UPN claim or SPN claim based on availability. |
description
|
the description of the event. |
id
|
the Id of this event as required by ARM for RBAC. It contains the EventDataID and a timestamp information. |
event_data_id
|
the event data Id. This is a unique identifier for an event. |
correlation_id
|
the correlation Id, usually a GUID in the string format. The correlation Id is shared among the events that belong to the same uber operation. |
event_name
|
the event name. This value should not be confused with OperationName. For practical purposes, OperationName might be more appealing to end users. |
category
|
the event category. |
http_request
|
the HTTP request info. Usually includes the 'clientRequestId', 'clientIpAddress' (IP address of the user who initiated the event) and 'method' (HTTP method e.g. PUT). |
level
|
str or
EventLevel
the event level. Known values are: "Critical", "Error", "Warning", "Informational", and "Verbose". |
resource_group_name
|
the resource group name of the impacted resource. |
resource_provider_name
|
the resource provider name of the impacted resource. |
resource_id
|
the resource uri that uniquely identifies the resource that caused this event. |
resource_type
|
the resource type. |
operation_id
|
It is usually a GUID shared among the events corresponding to single operation. This value should not be confused with EventName. |
operation_name
|
the operation name. |
properties
|
the set of <Key, Value> pairs (usually a Dictionary<String, String>) that includes details about the event. |
status
|
a string describing the status of the operation. Some typical values are: Started, In progress, Succeeded, Failed, Resolved. |
sub_status
|
the event sub status. Most of the time, when included, this captures the HTTP status code of the REST call. Common values are: OK (HTTP Status Code: 200), Created (HTTP Status Code: 201), Accepted (HTTP Status Code: 202), No Content (HTTP Status Code: 204), Bad Request(HTTP Status Code: 400), Not Found (HTTP Status Code: 404), Conflict (HTTP Status Code: 409), Internal Server Error (HTTP Status Code: 500), Service Unavailable (HTTP Status Code:503), Gateway Timeout (HTTP Status Code: 504). |
event_timestamp
|
the timestamp of when the event was generated by the Azure service processing the request corresponding the event. It in ISO 8601 format. |
submission_timestamp
|
the timestamp of when the event became available for querying via this API. It is in ISO 8601 format. This value should not be confused eventTimestamp. As there might be a delay between the occurrence time of the event, and the time that the event is submitted to the Azure logging infrastructure. |
subscription_id
|
the Azure subscription Id usually a GUID. |
tenant_id
|
the Azure tenant Id. |
Azure SDK for Python
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for