Context table successfully cleared

Audit events for context tables are created only for actions performed by users.

The event can be assigned the succeeded or failed status.

Since the request to clear an context table is made over a remote connection, a data transfer error may occur at any moment: both before and after deletion.

This means that the context table may be cleared successfully, but the event gets the failed status anyway, because EventOutcome returns the TCP/IP connection status of the request, but not the succeeded or failed status of the context table clearing.

Event field name	Field value
`DeviceAction`	`context table cleared`
`EventOutcome`	`succeeded` or `failed`
`SourceTranslatedAddress`	This field contains the value of the HTTP header x-real-ip or x-forwarded-for. If these headers are absent, the field will be empty.
`SourceAddress`	The address from which the user logged in. If the user logged in using a proxy, there will be a proxy address.
`SourcePort`	Port from which the user logged in. If the user logged in using a proxy, there will be a port on the proxy side.
`SourceUserName`	User name of the user that cleared the context table.
`SourceUserID`	ID of the user that cleared the context table.
`DeviceExternalID`	ID of the service whose context table was cleared.
`ExternalID`	Context table ID
`Name`	Name of the context table.
`Message`	If EventOutcome = `failed`, an error message can be found here.
`DeviceCustomString5`	Service tenant ID. Some errors prevent adding tenant information to the event.
`DeviceCustomString5Label`	tenant ID
`DeviceCustomString6`	Tenant name.
`DeviceCustomString6Label`	tenant name

Page top