An incident is a term used in WinGate to describe the moment when a set of specific conditions can arise during its activity. WinGate allows you to define the conditions that it deems will constitute an incident. The subsequent occurrence of these incidents can then be used to trigger a notification plan in the Notifications system.
Incidents can be created by using the various incident configurations that are available in WinGate. Whenever the incident occurs, it is reported to the Notifications system and the incident details logged.
Currently there are four ways of creating and defining an incident in WinGate:
When configuring a policy, you can use a Notification policy item registered by the Notifications system, to create a point in the policy evaluation where an incident will be deemed to have taken place. This allows you to choose what conditions should be evaluated by the policy that will lead it to reporting the incident in the Notification policy item.
WinGate Data module - Data monitoring/Threshold checking
When you select data to be monitored in WinGate, there is an option to set threshold values that the monitored data should never exceed or fall below. These thresholds allow you to create incidents whenever the threshold value is passed. This means that notification plans can be created to respond to changes in data that is being monitored at any time, such as setting a maximum value threshold on the number of HTTP requests per hour, the number of connections per second etc.
When configuring the WinGate Update settings, you can use the Notifications tab to create an incident when the updates fail, or when there are new updates available.
Using a WinGate script system/Symbol Browser
When using a WinGate script system (such as the Lua script and Javascript event processors) or a WinGate configuration that has access to a Symbol Browser, you can use the Notifications object registered by the Notifications system to create incidents. You can use the Notifications.Report method provided by the Notifications object to report (create) an incident if required. This allows you to report and handle incidents based on the evaluation process of the script where you use the Notifications object, or from within any configuration that has access to the Symbol Browser.
This method will automatically check for the existence of the incident given in the Text Incident parameter. If it is not found, an incident with that name will be created automatically and trigger the specified notification plan.
e.g. A script could contain:
Notifications.Report("testincident","Someone created a test incident","thetestplan")
This would check to see if a incident called testincident exists. If it doesn't it will create and report an incident called testincident to the Notifications system. Included with the incident report will be the message: Someone created a test incident, and this incident will initiate the execution of a predefined notification plan called thetestplan.
When an incident triggers the execution of a notification plan, the incident will be reported under the name given to it in the configuration you used to create the incident. If you wish to define separate incidents, each incident must have unique name when they are first being configured.
You can use basic Full-Text Searches against the page title and body to find matching articles. Use the following search modifiers to refine your query:
