EventMonitor 2.5 AddEventDetail
Adds a new action to an existing event which is specified by the parameter plProgressId .
Parameters
| Name | Type | Direction | Description |
|---|---|---|---|
| psAuthContext | String | InOut | Deprecated proprietary authentication context only used by .ASMX web services based on internal username/password authentication. Claims based security standards drive all the WCF .SVC web services making this parameter redundant. |
| plProgressId | Long | In | The unique identifier of the event |
| peLevel | eEventLevel | In | One of the enumeration values that specifies the event level for the event detail |
| psAction | String | In | Action of the event (e.g. Request queued) |
| psDescription | String | In | Description of the event |
| peStatus | eDetailStatus | In | Indicates the status for the event detail |
| peDataType | eEventDataType | In | Indicates the data type of the event data content. |
| pbData | Blob | In | The event data content |
| plOutDetailId | Long | Out | The unique identifier of the newly added event detail |
Note that:
- The event must exist. So, make sure that the event is initialized by calling StartEvent
- The event is only logged if the given
EventLevelis lower than the configured EvenAppLevel. For example,EventAppLevelVerbosewill log messages of level 'Exception', 'Warning', 'Information' and 'Verbose' but not the messages of level 'Debug'. - The size of
psActionis limited to 255 characters. So, try to keep the action short. If the string is too large, the string will be truncated! - The size of
psDescriptionis limited to 2000 characters. If the string is too large, the string will be truncated! - The
creation dateis set to the current date (and time) - The
ProcessId, theThreadIdand theHostNameare set automatically