conf/events
The conf/events directory contains configuration files that tie actions to a set of events. In the web UI this functionality is controlled using the System > Alerting and System > Alerting > Event Types pages. The configuration files in conf/events represent the functionality configured on both these pages. The name of the configuration files are the "Event Type" names as shown in the UI. In the SOAP API and CLI this is managed in the Alerting.EventType section. The events subscribed to by a particular event type configuration are identified by an object type and a set of event tags using keys of the form "type!<object-type>!event_tags <tag-list>". For example: "type!vservers!event_tags vsstart vsstop". The events subscribed to can be further filtered to specific configuration objects using keys of the form "type!<object-type>!object_names <object-names>". The table below lists the object types and all the event tags that are available for them.
Key | Description |
|---|---|
actions | The actions triggered by events matching this event type. (See the type!*!event_tags and type!*!object_names keys.) The value is a list of files to execute when a matching event occurs, these files must be located within the conf/actions directory. Refer to the documentation for the conf/actions configuration section for more information regarding how these files are executed. Value type: list Default value: <none> |
built_in | If set to Yes this indicates that this configuration is built-in (provided as part of the software) and cannot be deleted or edited. Value type: Yes / No Default value: "No" |
note | A description of this event type. Value type: string Default value: <none> |
type!*!event_tags | This key is used to specify the object types and event tags that will trigger the configured actions. The object type is specified in place of the * (asterisk) in the key name. The key can be used multiple times in a configuration file to subscribe to events from multiple object types. The value can be * (asterisk) to subscribe to all events raised by the specified object type, or can be a list of specific event tags (refer to the table in the conf/events section documentation for a list of all object types and event tags). The following example sends an email alert when any virtual server starts or stops: actions E-Mail type!vservers!event_tags vsstart vsstop type!vservers!object_names * If this is in a file named conf/events/VSStartStop then on the System > Alerting UI page a mapping will be shown associating the event type "VSStartStop" with the action "E-Mail". See type!*!object_names for additional information. Value type: list Default value: <none> |
type!*!object_names | This key can be used to restrict the events that will trigger the configured actions to ones raised by objects with specific names (filenames). The * (asterisk) in the key must be replaced by an object type matching one that has also been used in a type!<object-type>!event_tags key. The value is a list containing the names of objects of the type specified in the key. (If this key is not specified then the default value of * (asterisk) is assumed, which means to subscribe to events from all objects of the given type). The following example sends email alert whenever the virtual server named "Very Important" starts or stops: actions E-Mail type!vservers!event_tags vsstart vsstop type!vservers!object_names "Very Important" If this is in a file named conf/events/VSStartStop then on the System > Alerting UI page a mapping will be shown associating the event type "VSStartStop" with the action "E-Mail". See type!*!event_tags for additional information. Value type: list Default value: <none> |
Event tags by object type
Event Tag | Description |
|---|---|
Event tags for object type: "cloudcredentials" | |
apistatusprocesshanging | A cloud API process querying changes to cloud instances is hanging |
autoscaleresponseparseerror | An API call made by the autoscaler process has returned a response that could not be parsed |
autoscalestatusupdateerror | An API call made by the autoscaler process has reported an error |
autoscalingprocesstimedout | A cloud API process has timed out |
usedcredsdeleted | A Cloud Credentials object has been deleted but it was still in use (The configuration file containing cloud credentials was removed, but the credentials were still being used by one or more autoscaled pools.) |
Event tags for object type: "config" | |
confadd | Configuration file added |
confdel | Configuration file deleted |
confmod | Configuration file modified |
confok | Configuration file now OK |
Event tags for object type: "faulttolerance" | |
activatealldead | Activating this machine automatically because it is the only working machine in its Traffic IP Groups |
activatedautomatically | Machine has recovered and been activated automatically because it would cause no service disruption |
allmachinesok | All machines are working (All machines are working) |
autofailbackafterdelay | Automatic failback after delay |
autofailbacktimercancelled | Auto-failback delay timer cancelled |
autofailbacktimerstarted | Auto-failback wait period started |
autofailbacktimerstopped | Auto-failback delay timer stopped due to system failure |
bgpneighborsdegraded | Some of the BGP neighbors do not have established sessions |
bgpneighborsfailed | None of the BGP neighbors have an established session (None of the BGP neighbors have an established session) |
bgpneighborsok | There are established sessions with all BGP neighbors (There are established sessions with all BGP neighbors) |
bgpnoneighbors | There are no valid BGP neighbors defined (There are no valid BGP neighbors defined) |
clockjump | The system clock jumped forwards or backwards by more than one second |
clocknotmonotonic | The monotonic system clock went backwards |
dropec2ipwarn | Removing EC2 IP Address from all machines; it is no longer a part of any Traffic IP Groups |
dropgceipwarn | Removing GCE IP Address from all machines; it is no longer a part of any Traffic IP Groups |
dropipinfo | Dropping Traffic IP Address due to a configuration change or traffic manager recovery |
dropipwarn | Dropping Traffic IP Address due to an error (The Traffic IP address was dropped due to a network failure) |
ec2flipperraiselocalworking | Moving EC2 IP Address; local machine is working |
ec2flipperraiseothersdead | Moving EC2 IP Address; other machines have failed |
ec2iperr | Problem occurred when managing an EC2 IP address |
ec2nopublicip | Cannot raise Elastic IP on this machine until EC2 provides it with a public IP address (An Elastic IP cannot currently be moved to this machine. This is usually because it has recently had its Elastic IP moved to another box, and EC2 has not yet returned its default public IP address.) |
ec2nosecondaryprivateip | Cannot raise Elastic IP on this machine as no suitable secondary IP is available on the allowed network card(s) (An Elastic IP cannot currently be moved to this machine. This is usually because it doesn't have a secondary private address with either no EIP association assigned to network interface(s) or is used by a virtual server.) |
flipperbackendsworking | Back-end nodes are now working (Back-end nodes are now working) |
flipperdadreraise | Re-raising Traffic IP Address; Operating system did not fully raise the address (This address is being re-raised to circumvent the operating system's Duplicate Address Detection feature) |
flipperfrontendsworking | Frontend machines are now working (The machines that your traffic manager is using to check network connectivity on the frontend (usually the default gateway) are now working) |
flipperipexists | Failed to raise Traffic IP Address; the address exists elsewhere on your network and cannot be raised |
flipperraiselocalworking | Raising Traffic IP Address; local machine is working |
flipperraiseosdrop | Raising Traffic IP Address; Operating System had dropped this IP address (Traffic IP Addresses are automatically managed by the traffic manager, and their configuration should only be altered from the vTM Admin Server.) |
flipperraiseothersdead | Raising Traffic IP Address; other machines have failed (The Traffic IP Address will be raised as a result of the the death of another machine, or a config change.) |
flipperraiseremotedropped | This Traffic Manager has re-raised traffic IP addresses as the remote machine which was hosting them has dropped them |
flipperrecovered | Machine is ready to raise Traffic IP addresses |
gceflipperraiselocalworking | Moving GCE IP Address; local machine is working |
gceflipperraiseothersdead | Moving GCE IP Address; other machines have failed |
gceiperr | Problem occurred when managing a GCE IP address |
gcenofreenic | Cannot associate more External IP addresses with this instance, all interfaces are allocated (Cannot associate an external IP with this instance, all NICs are reserved) |
machinefail | Remote machine has failed |
machineok | Remote machine is now working (Remote machine is now working) |
machinerecovered | Remote machine has recovered and can raise Traffic IP addresses |
machinetimeout | Remote machine has timed out and been marked as failed |
multihostload | The amount of load handled by the local machine destined for this Traffic IP has changed |
ospfneighborsdegraded | Some of the monitored OSPF neighbors are not peered (Some of the neighboring OSPF routers being monitored by flipper!ospfv2_neighbor_addrs are not peered) |
ospfneighborsfailed | None of the monitored OSPF neighbors are peered (None of the neighboring OSPF routers being monitored by flipper!ospfv2_neighbor_addrs are peered) |
ospfneighborsok | All monitored OSPF neighbors are peered (The neighboring OSPF routers being monitored by flipper!ospfv2_neighbor_addrs are all peered) |
pingbackendfail | Failed to ping back-end nodes |
pingfrontendfail | Failed to ping any of the machines used to check the front-end connectivity |
pinggwfail | Failed to ping default gateway |
pingsendfail | Failed to send ping packets |
routingswfailed | Routing software had a major failure and will be restarted (The routing software stack used for Route Health Injection has had a major failure and will be restarted.) |
routingswfailurelimitreached | Routing software has failed and reached its failure limit (The maximum number of failures in a set period has been reached by the routing software stack used for Route Health Injection.) |
routingswoperational | Routing software is now operational (The routing software stack used for Route Health Injection has started.) |
routingswstartfailed | Routing software failed to start (The routing software stack used for Route Health Injection failed to start within the allowed time.) |
statebaddata | Received an invalid response from another cluster member (An incorrectly formatted session persistence state message was received (for example version incompatibility between traffic managers).) |
stateconnfail | Failed to connect to another cluster member for state sharing (The traffic manager failed to establish the connection used for session persistence state sharing.) |
stateok | Successfully connected to another cluster member for state sharing |
statereadfail | Reading state data from another cluster member failed (The traffic manager failed to read session persistence information from another traffic manager.) |
statetimeout | Timeout while sending state data to another cluster member (Another traffic manager in the cluster failed to respond to a session persistence state message within (2 * 'state_sync_time').) |
stateunexpected | Received unexpected state data from another cluster member (A session persistence state message was received when the traffic manager was not expecting it.) |
statewritefail | Writing state data to another cluster member failed (The traffic manager failed to write session persistence state to another cluster member.) |
zclustermoderr | An error occurred when using the zcluster Multi-Hosted IP kernel module |
Event tags for object type: "general" | |
analyticsconnected | Analytics Transaction Metadata Export connected (A successful connection has been made to the transaction export endpoint) |
analyticsconnectionerror | Analytics Transaction Metadata Export connection failure (Failed to make a connection to the transaction export endpoint) |
analyticsdisconnected | Analytics Transaction Metadata Export disconnected (The connection to the transaction export endpoint was broken) |
appfirewallcontrolerror | Application firewall control command failed |
appfirewallcontrolrestarted | Application firewall restarted (Application firewall restarted) |
appfirewallcontrolstarted | Application firewall started (Application firewall started) |
appfirewallcontrolstopped | Application firewall stopped (Application firewall stopped) |
appfirewallcontroltimeout | Application firewall control command timed out |
appliance | Appliance notification |
audit | An audit log event has occured |
autherror | An error occurred during user authentication |
autoscaleresolvefailure | A hostname used for DNS-derived Autoscaling doesn't resolve |
autoscalinglicenseerror | Autoscaling not permitted by licence key |
childcommsfail | There was an error communicating with a child process (A helper process did not properly acknowledge a control request.) |
commchanneldied | SD Communications Channel Agent died (SD Communications Channel Agent died) |
commchannelstartfail | Failed to start SD Communications Channel Agent (Failed to start SD Communications Channel Agent) |
commchannelterminatefail | SD Communications Channel Agent failed to terminate (The SD Communications Channel Agent failed to terminate promptly) |
confrepfailed | Replication of configuration has failed |
confreptimeout | Replication of configuration has timed out (Replication of configuration has timed out) |
discopluginfailed | Traffic manager failed to get the required output from the Service Discovery plugin (Traffic manager failed to get the required output from the plugin) |
discoplugininfo | Service Discovery plugin returned extra logging information (Plugin returned extra information which should be logged) |
discoplugininvalid | Service Discovery plugin returned invalid output (Plugin returned a node with missing information) |
discopluginstartfail | Traffic manager failed to start the Service Discovery Plugin (Failed to run a plugin) |
discopluginstartsuccess | Traffic manager has now successfully run the Service Discovery plugin (Traffic manager has now successfully run the plugin) |
discopluginwarning | Service Discovery succeeded but provided a warning (Plugin succeeded but gave a warning in the error field.) |
dnszonecreaterecord | The built-in DNS server has failed to create a DNS record |
dnszoneparse | The built-in DNS server has failed to parse a DNS zone file |
dnszonevalidate | The built-in DNS server has failed to validate a DNS zone file |
ec2dataretrievalfailed | Traffic manager failed to get the required data from Amazon servers (Traffic manager failed to get the required data from Amazon servers) |
ec2dataretrievalsuccessful | Traffic manager has now successfully retrieved the required data from Amazon servers (Traffic manager has now successfully retrieved the required data from Amazon servers) |
ec2initialized | The EC2 instance is now initialized (The EC2 instance is now initialized) |
fewfreefds | Running out of free file descriptors (There are few free file descriptors remaining; this machine will soon become unable to establish new connections. See the manual for information on tuning to correct this.) |
fipsfailinit | FIPS 140-2 cryptographic module initialization failed (A failure occurred when loading or during power-up testing of the FIPS 140-2 cryptographic module.) |
fipsfailops | FIPS 140-2 cryptographic module operations failed (Unable to fully enable or retain the context for valid use of the FIPS 140-2 cryptographic module in the Traffic Manager.) |
gcedataretrievalfailed | Traffic manager failed to get the required data from GCE instance |
gcedataretrievalsuccessful | Traffic manager has now successfully retrieved the required data from GCE instance (Traffic manager has now successfully retrieved the required data from GCE instance) |
geodataloadfail | Failed to load geolocation data |
licensetoomanylocations | A location has been disabled because you have exceeded the licence limit |
logdiskfull | Log disk partition full (Log disk partition full) |
logdiskoverload | Log disk partition usage has exceeded threshold (Log disk partition usage has exceeded threshold) |
logdiskrecovered | Log disk partition usage has recovered (Log disk partition usage has recovered) |
nameserveravailable | DNS-derived Autoscaling will resume updating, as the DNS server is now responding (DNS-derived Autoscaling will resume updating, as the DNS server is now responding) |
nameserverunavailable | DNS-derived Autoscaling will not update, as the DNS server is unavailable (DNS-derived Autoscaling will not update, as the DNS server is unavailable) |
numlocations-exceeded | Total number of locations exceeded the maximum limit |
numnodes-exceeded | Total number of nodes exceeded the maximum number of nodes that can be monitored |
numpools-exceeded | Total number of pools exceeded the maximum limit |
numtipg-exceeded | Total number of traffic IP group exceeded the maximum limit |
ocspstaplingfail | OCSP request (for OCSP stapling) failed (An OCSP request for a certificate, to be used for OCSP stapling has failed. The error log line contains the name of the certificate and the URL to which the request was made.) |
ocspstaplingnomem | Insufficient memory for OCSP stapling (The memory allocated for OCSP stapling was not large enough to store the responses for all configured certificates.) |
ocspstaplingrevoked | An OCSP request (for OCSP stapling) reported that a certificate was revoked (An OCSP request for a certificate, to be used for OCSP stapling, was successful but reported that the certificate was revoked. The error log line contains the name of the certificate and the URL to which the request was made.) |
ocspstaplingunknown | An OCSP request (for OCSP stapling) reported that a certificate was unknown (An OCSP request for a certificate, to be used for OCSP stapling, was successful but reported that the certificate was unknown. The error log line contains the name of the certificate and the URL to which the request was made.) |
ocspstaplingunrevoked | An old but good OCSP response was returned for a revoked certificate (An OCSP request for a certificate previously indicated that a certificate had been revoked, but a recent response indicates that it is OK. This may indicate an OCSP replay attack. The error log line contains the name of the certificate and the URL to which the request was made.) |
restartrequired | Software must be restarted to apply configuration changes |
running | Software is running |
sslcrltoobig | CRL does not fit in the configured amount of shared memory, increase ssl!crl_mem!size and restart software |
sslticketencryptionkeyunavailable | No SSL ticket encryption key available (No SSL ticket encryption key is available. The traffic manager will not be able to create new SSL session tickets until a new key has been provided. SSL connections to virtual servers will still be accepted while this error persists.) |
sysctlreboot | Virtual Traffic Manager Appliance reboot required (A reboot is required) |
timemovedback | Time has been moved back (This machine's clock has been set backwards by a significant amount; your traffic manager should be restarted to prevent problems with timeouts, fault tolerance and other areas.) |
unspecifiedreboot | Virtual Traffic Manager restart/reboot required (A restart/reboot is required, cause unspecified) |
upgradereboot | Virtual Traffic Manager Appliance reboot required (A reboot is required) |
upgraderestart | Virtual Traffic Manager software restart required (A restart is required) |
watchdog | Traffic Manager process stall detected by the watchdog (A traffic manager process stall was detected by the watchdog. This can be caused by overloaded virtual machine infrastructure, or by software defects. The program state has been logged for inclusion in a technical support request.) |
zxtmcpustarvation | The number of simultaneously active connections has reached a level that the software cannot process in due time because of CPU starvation; there is a high risk of connections timing out |
zxtmhighload | The number of simultaneously active connections has reached a level that the software cannot process in due time; there is a high risk of connections timing out |
zxtmswerror | Internal software error |
Event tags for object type: "java" | |
javadied | Java runner died |
javanotfound | Cannot start Java runner, program not found |
javastarted | Java runner started |
javastartfail | Java runner failed to start |
javastop | Java support has stopped (Java is now either unlicensed or disabled in Global Settings.) |
javaterminatefail | Java runner failed to terminate (The process handling Java extensions failed to terminate promptly. Contact your support provider.) |
servleterror | Servlet encountered an error |
Event tags for object type: "licensekeys" | |
analyticslicensedisabled | Realtime Analytics support has been disabled |
analyticslicenseenabled | Realtime Analytics support has been enabled |
autoscalinglicensedisabled | Autoscaling support has been disabled |
autoscalinglicenseenabled | Autoscaling support has been enabled |
bwlimited | License key bandwidth limit has been hit |
cachesizereduced | Configured cache size exceeds license limit, only using amount allowed by license |
communityeditionclustertoobig | Cluster size exceeds the Community Edition limit |
expired | License expired (The license in use has expired.) |
expiresoon | License key expires within 7 days |
expiresoon15 | License key expires within 15 days |
expiresoon30 | License key expires within 30 days |
expiresoon60 | License key expires within 60 days |
expiresoon90 | License key expires within 90 days |
lessmemallowed | License allows less memory for caching |
license-authorized | License key authorized (License key authorized) |
license-authorized-ts | License key authorized by authorization code (License key authorized by authorization code) |
license-explicitlydisabled-ts | License key explicitly disabled from authorization code |
license-graceperiodexpired | Unable to authorize license key |
license-graceperiodexpired-ts | Unable to authorize license key |
license-rejected-authorized | License server rejected license key; key remains authorized |
license-rejected-authorized-ts | License key rejected from authorization code; key remains authorized |
license-rejected-unauthorized | License server rejected license key; key is not authorized (License server rejected license key; key is not authorized) |
license-rejected-unauthorized-ts | License key rejected from authorization code |
license-timedout-authorized | Unable to contact license server; license key remains authorized |
license-timedout-authorized-ts | Unable to run authorization code to completion; key remains valid |
license-timedout-unauthorized | Unable to contact license server; license key is not authorized (Unable to contact license server; license key is not authorized) |
license-timedout-unauthorized-ts | Unable to run authorization code to completion |
license-unauthorized | License not authorized by remote server (The current license had not been authorized by the license server.) |
licenseclustertoobig | Cluster size exceeds license key limit |
licensecorrupt | Invalid License (This key is invalid and cannot be used; you should upload a valid key.) |
licensestate-malformed | Error detected in LicenseStateFile format |
licensestate-write-failed | Unable to preserve license state (The license state file could not be updated.) |
morememallowed | License allows more memory for caching |
ssltpslimited | License key SSL transactions-per-second limit has been hit |
tpslimited | License key transactions-per-second limit has been hit |
unlicensed | Started without a license |
usinglicense | Using license key (This license key currently determines the available features, because it has more features than any other available keys.) |
webcachelicensenewmax | A new limit on the maximum cache size is in place |
Event tags for object type: "locations" | |
locationavailable | Location is now available for GLB Service (Location is now available for GLB Service) |
locationdisabled | Location has been disabled for GLB Service (Location has been disabled for GLB Service) |
locationdraining | Location is being drained for GLB Service (Location is being drained for GLB Service) |
locationenabled | Location has just been enabled for GLB Service (Location has just been enabled for GLB Service) |
locationfail | Location has failed for GLB Service (Location has failed for GLB Service) |
locationmonitorfail | A monitor has detected a failure in this location |
locationmonitorok | A monitor has indicated this location is now working |
locationnotdraining | Location is not being drained for GLB Service (Location is not being drained for GLB Service) |
locationok | Location is now healthy for GLB Service (Location is now healthy for GLB Service) |
locationsoapfail | An external SOAP agent has detected a failure in this location (An external SOAP agent has detected a failure in this location) |
locationsoapok | An external SOAP agent indicates this location is now working (An external SOAP agent indicates this location is now working) |
locationunavailable | Location has become unavailable for GLB Service (Location has become unavailable for GLB Service) |
locempty | Location no longer contains any machines |
locmovemachine | Machine now in location |
Event tags for object type: "monitors" | |
monitorfail | Monitor has detected a failure |
monitorok | Monitor is working |
Event tags for object type: "pools" | |
apichangeprocesshanging | API change process still running after refractory period is over |
autonodecreationcomplete | The creation of a new node requested by an autoscaled pool is now complete |
autonodecreationstarted | Creation of new node instigated |
autonodedestroyed | A cloud API call to destroy a node has been started |
autonodedestructioncomplete | The destruction of a node in an autoscaled pool is now complete |
autonodedisappeared | A node in an autoscaled pool has disappeared from the cloud |
autonodeexisted | IP address of newly created instance already existed in pool's node list (The autoscaler has been informed about the completion of an instance creation in the cloud, but unexpectedly a node with the same ip address already existed in the pool's node list.) |
autonodenopublicip | Node has no public IP address (We want the public IP but it is unset) |
autonoderemoved | A node in an DNS-derived autoscaled pool has been removed |
autonodestatuschange | The status of a node in an autoscaled pool has changed (The status of a node in an autoscaled pool has changed. This can be, for instance, a node moving from the 'pending' state, when it is still being created/finalized in the cloud environment, to the 'active' state, when it can be fully used.) |
autoscalednodecontested | Two pools are trying to use the same instance |
autoscaledpoolrefractory | An autoscaled pool is now refractory (An autoscaled pool's size has recently changed, so no further changes are made until it has settled down) |
autoscaledpooltoobig | Over maximum size - shrinking |
autoscaledpooltoosmall | Minimum size undercut - growing |
autoscaleinvalidargforcreatenode | The 'imageid' was empty when attempting to create a node in an autoscaled pool |
autoscaleinvalidargfordeletenode | 'unique id' was empty when attempting to destroy a node in an autoscaled pool |
autoscalepoolconfupdate | A pool config file has been updated by the autoscaler process |
autoscalewrongimageid | A node created by the autoscaler has the wrong imageid |
autoscalewrongname | A node created by the autoscaler has a non-matching name |
autoscalewrongsizeid | A node created by the autoscaler has the wrong sizeid |
autoscalingchangeprocessfailure | An API process that should have created or destroyed a node has failed to produce the expected result |
autoscalingdisabled | Autoscaling for a pool has been disabled due to errors communicating with the cloud API |
autoscalinghitfloor | Minimum size reached, cannot shrink further |
autoscalinghitroof | Maximum size reached by autoscaled pool, cannot grow further |
autoscalinghysteresiscantgrow | An autoscaled pool is waiting to grow (An autoscaled pool should grow according to its response statistics, but the hysteresis setting demands that the growth condition persist for a longer time before the pool actually creates a new node.) |
autoscalinghysteresiscantshrink | An autoscaled pool is waiting to shrink (An autoscaled pool should shrink according to its response statistics, but the hysteresis setting demands that the shrink condition persist for a longer time before the pool actually creates a new node.) |
autoscalingpoolstatechange | An autoscaled pool's state has changed |
autoscalingresuscitatepool | An autoscaled pool has failed completely |
badcontentlen | HTTP response contained an invalid Content-Length header (The HTTP response contained an invalid 'Content-Length' header. The traffic manager will not be able to detect the end of the response and the response cannot make use of keep-alives.) |
cannotshrinkemptypool | Attempt to scale down a pool that only had pending nodes or none at all |
ehloinvalid | Node returned invalid EHLO response |
nodedrainingtodelete | Removed node is in use and will be drained (Removed node is in use and will be drained) |
nodedrainingtodeletetimeout | Draining to delete period for node has expired (Draining to delete period has timed out for node.) |
nodefail | Node has failed |
noderesolvefailure | Failed to resolve node address |
noderesolvemultiple | Node resolves to multiple IP addresses |
nodeworking | Node is working again |
nostarttls | Node doesn't provide STARTTLS support |
pooldied | Pool has no back-end nodes responding |
poolnonodes | Pool configuration contains no valid backend nodes |
poolok | Pool now has working nodes (One or more nodes are now available for this pool.) |
starttlsinvalid | Node returned invalid STARTTLS response |
Event tags for object type: "protection" | |
triggersummary | Summary of recent service protection events (Service protection has generated a summary of recent events. The frequency of these messages is configured by log_time on each service protection class.) |
Event tags for object type: "rules" | |
aptimizedisabled | Rule attempted to use Web Accelerator but it is not enabled |
aptimizeuseunknownprofile | Rule selected an unknown Web Accelerator profile |
aptimizeuseunknownscope | Rule selected an unknown Web Accelerator scope |
datalocalstorefull | data.local.set() has run out of space |
datastorefull | data.set() has run out of space (data.set() operations will continue to fail until data.remove() or data.reset() is used) |
forwardproxybadhost | Rule selected an unresolvable host (A rule selected a host which could not be resolved to an IP address) |
invalidemit | Rule used event.emit() with an invalid custom event (The event ID was empty or contained invalid characters.) |
norate | Rule selected an unknown rate shaping class |
poolactivenodesunknown | Rule references an unknown pool via pool.activenodes |
pooluseunknown | Rule selected an unknown pool |
ruleabort | Rule aborted during execution |
rulebodycomperror | Rule encountered invalid data while uncompressing response (Rule could not decompress a compressed HTTP response body) |
rulebufferlarge | Rule has buffered more data than expected (A rule is using more data than expected according to the configuration setting trafficscript!memory_warning in the Global Settings page. This is a warning only; this connection will continue to be handled. If many connections exceed the limit at the same time, your traffic manager might slow down or run out of memory. Consider re-writing the rule to reduce its memory usage or changing the limit.) |
rulelogmsginfo | Rule logged an info message using log.info |
rulelogmsgserious | Rule logged an error message using log.error |
rulelogmsgwarn | Rule logged a warning message using log.warn |
rulenopersistence | Rule selected an unknown session persistence class |
ruleoverrun | Rule exceeded execution time warning threshold |
rulesinvalidrequestbody | Client sent invalid HTTP request body (Invalid request body data encountered by rule) |
rulestreamerrorgetresponse | Attempt to use http.getResponse or http.getResponseBody after http.stream.startResponse (Attempt to use http.getResponse or http.getResponseBody after http.stream.startResponse.) |
rulestreamerrorinternal | Internal error while processing HTTP stream |
rulestreamerrornotenough | Rule did not supply enough data in HTTP stream (Rule had specified a content length but then supplied less data than advertised. Correct Content-Length header in rule/Java Extension or remove it altogether.) |
rulestreamerrornotfinished | Attempt to initialize HTTP stream before previous stream had finished (Either a rule called http.stream.startResponse() twice or a rule failed to call http.stream.finishResponse() and its connection was kept-alive. Check the use of the http.stream.* TrafficScript * functions in your rules.) |
rulestreamerrornotstarted | Attempt to stream data or finish a stream before streaming had been initialized (A rule called http.stream.writeResponse() or http.stream.finishResponse() before calling http.stream.startResponse(). Check the use of the http.stream.* TrafficScript functions in your rules.) |
rulestreamerrorprocessfailure | Data supplied to HTTP stream could not be processed (The data provided by a rule for streaming could not be processed successfully. Check the use of the http.stream.* TrafficScript functions in your rules.) |
rulestreamerrortoomuch | Rule supplied too much data in HTTP stream (Rule had specified a content length but then supplied more data than advertised. Correct Content-Length header in rule/Java Extension or remove it altogether.) |
rulexmlerr | Rule encountered an XML error |
serviceruleabort | GLB service rule aborted during execution |
servicerulelocdead | GLB service rule specified a location that has either failed or been marked as draining in the service configuration |
servicerulelocnotconfigured | GLB service rule specified a location that is not configured for the service |
servicerulelocunknown | GLB service rule specified an unknown location |
Event tags for object type: "services" | |
glbactivedcmismatch | Active datacentre mismatches among cluster members |
glbdeadlocmissingips | A DNS Query returned IP addresses that are not configured for any location that is currently alive |
glbfailalter | Failed to alter DNS packet for global load balancing (The DNS packet could not be altered. This usually occurs when the record is signed using DNSSEC, and there is no private key configured to re-sign it.) |
glblogwritefail | Failed to write log file for GLB service |
glbmanualfailback | Manual failback triggered (Manual failback triggered) |
glbmissingips | A DNS Query returned IP addresses that are not configured in any location |
glbnewmaster | A location has been set as active for a GLB service |
glbnolocations | No valid location could be chosen for Global Load Balancing |
glbservicedied | GLB Service has failed (GLB Service has failed) |
glbserviceok | GLB Service has recovered (GLB Service has recovered) |
glbtoomanylocations | There are too many Data Centers configured and the Global Load Balancing feature is not guaranteed to work reliably with more than 255 Data Centres |
Event tags for object type: "slm" | |
slmclasslimitexceeded | SLM shared memory limit exceeded (The number of SLM classes configured requires more shared memory than is currently reserved for them. SLM classes will continue to work, but with reduced accuracy. For full accuracy, please increase the configuration key slm_class_limit on the Global Settings page and restart your traffic manager.) |
slmfallenbelowserious | SLM has fallen below serious threshold (The percentage of requests meeting the monitor's criteria has fallen below the serious threshold.) |
slmfallenbelowwarn | SLM has fallen below warning threshold (A lower percentage of requests meet this monitor's criteria than desired, and this was not the case at the previous check.) |
slmnodeinfo | Node information when SLM is non-conforming (no SNMP trap) (A summary of the nodes that have contributed to the SLM failure when it falls below the serious threshold. This event will not trigger an SNMP trap.) |
slmrecoveredserious | SLM has risen above the serious threshold (The percentage of requests that meet this monitor's criteria has risen above the serious threshold. The percentage was below the serious threshold at the previous check.) |
slmrecoveredwarn | SLM has recovered (The percentage of requests that meet this monitor's criteria has risen above the warning threshold. The percentage was below the warning threshold at the previous check.) |
Event tags for object type: "sslhw" | |
sslhwfail | SSL hardware support failed (SSL hardware support has stopped with an error) |
sslhwrestart | SSL hardware support restarted |
sslhwstart | SSL hardware support started |
Event tags for object type: "vservers" | |
connerror | A protocol error has occurred |
connfail | A socket connection failure has occurred |
dnsaddzone | The built-in DNS server has successfully added a DNS zone |
dnserroraddzone | The built-in DNS server has failed to add a DNS zone |
dnserrordeletezone | The built-in DNS server has failed to delete a DNS zone |
dnssecexpired | DNSSEC zone contains expired signatures (DNSSEC zone contains expired signatures) |
dnssecexpires | DNSSEC zone contains signatures that are about to expire (DNSSEC zone contains signatures that are about to expire) |
dnszonedelete | DNS zone has been deleted |
idpcertexpired | IDP certificate expired (IDP certificate expired) |
idpcerttoexpire | IDP certificate will expire within seven days (IDP certificate to expire) |
logfiledeleted | A virtual server request log file was deleted (appliances only) |
maxclientbufferdrop | Dropped connection, request exceeded max_client_buffer limit (The traffic manager is still reading the request, but the amount of data read in is larger than max_client_buffer - abandon the connection) |
poolpersistencemismatch | Pool uses a session persistence class that does not work with this virtual server's protocol |
privkeyok | Private key now OK (hardware available) (The private key for this virtual server is now available, because some required hardware is available again.) |
respcompfail | Error compressing HTTP response |
responsetoolarge | Response headers from webserver too large (The response headers from the webserver were bigger than max_server_buffer; the request will be rejected with an error.) |
rtspstreamnoports | No suitable ports available for streaming data connection (Consider changing the tuneables 'streaming_portrange_low' and 'streaming_portrange_high'.) |
samlauthnrequestcompressionfailure | Failed to compress SAML authentication request |
samlauthnrequestfailure | Failed to create SAML authentication request |
samlcookiedecryptfailure | Failed to decrypt SAML session cookie (Failed to decrypt SAML session cookie) |
samlcookieencryptfailure | Failed to encrypt cookie content (Failed to encrypt cookie content) |
samlnouserinresponse | No user specified in SAML response (No user specified in SAML response) |
samlrelaystatedecryptfailure | Failed to decrypt SAML RelayState (Failed to decrypt SAML RelayState) |
samlrelaystateencryptfailure | Failed to encrypt SAML RelayState (Failed to encrypt SAML RelayState) |
samlrelaystateinvalid | Failed to extract information from SAML RelayState |
samlresponseparsefailure | SAML response parse failure |
samlresponsevalidationfailure | SAML response validation failed |
samlsigverificationfailure | SAML response signature verification error |
sipstreamnoports | No suitable ports available for streaming data connection (Consider changing the tuneables 'streaming_portrange_low' and 'streaming_portrange_high'.) |
ssldrop | Request(s) received while SSL configuration invalid, connection closed |
sslfail | One or more SSL connections from clients failed recently (One or more SSL connections from clients failed recently) |
sslhandshakemsgsizelimit | SSL handshake messages have exceeded the size permitted by configuration (SSL handshake messages have exceeded the size permitted by configuration.) |
sslrehandshakemininterval | SSL re-handshake requests have exceeded the frequency permitted by configuration (SSL re-handshake requests have exceeded the frequency permitted by configuration.) |
vscacertexpired | Certificate Authority certificate expired (Certificate Authority certificate expired) |
vscacerttoexpire | Certificate Authority certificate will expire within seven days (Certificate Authority certificate to expire) |
vscrloutofdate | CRL for a Certificate Authority is out of date |
vslogwritefail | Failed to write log file for virtual server |
vssslcertexpired | Public SSL certificate expired (Public SSL certificate expired) |
vssslcerttoexpire | Public SSL certificate will expire within seven days (Public SSL certificate to expire) |
vsstart | Virtual server started |
vsstop | Virtual server stopped |
Event tags for object type: "zxtms" | |
versionmismatch | Configuration update refused: traffic manager version mismatch |