webMethods and Intelligent Business Operations 10.2 | Administering Mediator | Mediator Configurations | Performance Metrics and Run-Time Events Schema Published to Elasticsearch and API Portal | Policy Violation Events Type
 
Policy Violation Events Type
Event Type: PolicyViolationEvents
Key
Description
alertDesc
The alert message defined in the run-time policy action.
Example: A violation was detected for policy (Unknown-Policyuser ): Consumer could not be identified. Anonymous access is not allowed for this service.
alertSource
The Mediator policy name that produced the event.
Example: EnforcePolicy
alertType
The value Monitor means the event was produced by the Monitor Service Performance action. The value Sla means the event was produced by the Monitor Service Level Agreement action or the Throttling Traffic Optimization action.
Example: policy violation, service level monitoring, and so on.
apiId
Sequential primary key. This column does not contain a NULL value.
Example: c0f84954-9732-11e5-b9f4-f159eafe47b2
apiName
Name of the API invoked. This column does not contain a NULL value.
Example: VirtualService_Policy ViolationEvent
apiVersion
Version of the API. By default, for every version of an API a system version number is generated. At the same time, user can also provide a version number which is set as a user version.
Example: API 1.0 and API 2.0
consumerId
The system generated consumer application ID.
Example: c0f84954-9732-11e5-b9f4-f159eafe47b2
consumerIp
Consumer IP.
Example: 10.20.248.33
consumerName
Comma-separated consumer names identified based on the policy that triggered the event.
Example: <consumer application name>
creationDate
Timestamp when the event is created. Example: 2015-08-26 04:13:35 PM
eventType
Type of the event.
Value: PolicyViolationEvents
operationName
Virtual service operation which has been invoked.
Example: in calc API, the operations include add, sub, multi, and div. If add operation is invoked the operation name has add.
sessionId
Session token. This is the IS session token or a GUID if the token is missing from the message context.
Example: 779be3201e5f19b3b0e0ab264379ebd3
targetName
Specifies the name of the Mediator instance from where the event is published.
Example: LOCAL-MED

Copyright © 2015- 2018 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.
Innovation Release