Search

List of event types by category

Surveyor 6.x

Knowledge Base

This topic lists the event types that can occur under the categories shown in the Administrator console.

Introduction

When you view the Event Summary Report, specific events are grouped under different categories. This article lists every event type that can occur under each event category.

Client log location

C:\Program Files\Verdiem\Surveyor Agent\Logs

Categories

**Table 1. Admin Actions event category**

Includes all manual transitions to low-power states that an administrator sets on devices.
Event Types	Description	Normal event?
Sleep by Admin	Indicates Administrator API call to the client operating system's API for sleep (from menu in the Administrator console).	yes
Hibernate by Admin	Indicates Administrator API call to the OS's API for hibernate (from menu in the Administrator console).	yes
Shut down by Admin	Indicates Administrator API call to the OS's API for shut down (from menu in the Administrator console).	yes
Restart by Admin	Indicates Administrator API call to the OS's API for restart (from menu in the Administrator console).	yes

**Table 2. Idle Timer Actions category**

Transitions to low power states that occur specifically when the client is inactive (idle) for the length of time set in the policy assigned to it.
Event Types	Description	Normal event?
Sleep by Idle Timer	Indicates call to the OS's API for sleep when the Surveyor idle time countdown has expired. In other words, the client agent has been inactive for the amount of time specified for the CPU in the current policy.	yes
Hibernate by Idle Timer	Indicates call to the OS's API for hibernate when the Surveyor idle time countdown has expired. In other words, the client agent the CPU in the current policy.	yes

Other events recorded in this category include initial power scheme value when the client service is started, when a power scheme is set according to the policy schedule, when scheme is set by the user (because the scheme is created to allow the user to override it), and so on.

**Table 3. Policy Actions category**

This category includes events that occur through power state transition manager (PSTM) rules, and other events that occur when policies set schemes and change power states.
Event Types	Description	Normal event?
Application Protected	The PSTM vetoed a state change because a protected application was running.	yes
Script Vetoed	A PSTM script vetoed a state change.	yes
Application Detected	An application of interest was detected by way of PSTM rules.	yes
Application Terminated	PSTM terminated the indicated application.	yes
Scheme Initial Value	The initial value for the power scheme when the client service was started.	yes
Scheme Set by Policy	A switch to the power scheme enforced by the current policy when a scheduled event in the policy fires.	yes
User Scheme Restored	Restored the user's preferred scheme, because the currently scheduled policy allows for it.	yes
User Scheme Restored after Service Stop	Restored the user's preferred scheme because the Surveyor client service was stopped.	yes

**Table 4. Scheduled actions category**

Any power-state change that occurs according to the schedule set in the policy assigned to the client.
Event Types	Description	Normal event?
Sleep by Policy	The OS's API for sleep was called because a scheduled policy change occurred.	yes
Hibernate by Policy	The OS's API for hibernate was called because a scheduled policy change occurred.	yes
Shut Down by Policy	The OS's API for shut down was called because a scheduled policy change occurred.	yes
Restart by Policy	The OS's API for restart was called because a scheduled policy change occurred.	yes
Wake by Policy	Indicates a scheduled policy has triggered a wake event (always appears in conjunction with 104-Power Wake)	yes

**Table 5. Service events category**

Events logged by the client service, such as start, stop, or device check in. Events also include new database creation, and if data collection stops or starts for power state changes and user activity.
Event Types	Description	Normal event?
Service Started	The client service was started. CPU on is assumed; all other states are unknown.	yes
Service Stopped	The client service was stopped. All states should be considered unknown unless the subtype is Shutdown (CPU off).	no
Power State Collection Started	Indicates start of data collection for power state transitions. CPU on can be assumed; all other power states are unknown.	yes
Power State Collection Stopped	Indicates data collection stop for power state transitions; all power states go unknown.	no
User Activity Collection Started	Indicates start of data collection of user actions. Power states for all users go unknown.	yes
User Activity Collection Stopped	Indicates stop of data collection for user actions; power states for all users go unknown.	no
Database Created	Always the first event in a new database.	yes
High Sequence Number Changed	Indicates that the client updated its high sequence number to accommodate a detected re-imaging.	yes
Device Check-in	Client agent checks with the server for latest instructions (as set on the Server Settings page of Administrator console).	yes

**Table 6. State changes category**

Detailed power state change data and the request source (Surveyor server, a third party, or an unknown trigger). Also includes display-only logs for power-state changes.
Event Types	Description	Normal event?
On State	The current CPU state is on. This event is generated any time power state collection is started (through service start or a policy change).	yes
Shutdown State	Surveyor received notification from Windows that the CPU will turn off soon (user has received notification and allowed the shut down).	yes
Sleep State	Surveyor received notification from Windows that the CPU will transition to the sleep state soon (user has received notification and allowed the transition).	yes
Wake State	Surveyor client device wakes from a low power state (sleep or hibernate).	yes
Unknown State	This event is generated any time that power state collection is stopped (for example, if the client agent is uninstalled).	no
Sleep by Third-party	Indicates that a third-party, such as Cisco EnergyWise, called the OS sleep API.	yes
Hibernate by Third-party	Indicates that a third-party called the OS hibernate API.	yes
Shut Down by Third-party	Indicates that a third-party called the OS shut down API.	yes
Restart by Third-party	Indicates that a third-party called the OS restart API.	yes
Sleep by Unknown	Indicates that an unknown source has called the OS sleep API.	no
Hibernate by Unknown	Indicates that an unknown source has called the OS hibernate API.	no
Shut Down by Unknown	Indicates that an unknown source has called the OS shut down API.	no
Restart by Unknown	Indicates that an unknown source has called the OS restart API.	no
Wake by Unknown	Indicates that an unknown source has called the OS wake API.	no
Display On	One or more displays are in an on state. The power state (D-value) for each display is held.	yes
Display Sleep	No displays are in an on state, but at least one is in a sleep state.	yes
Display Unknown	The display state is unknown. This can indicate either that power state collection stopped or a failure of the detection APIs.	no

**Table 7. User actions category**

This category includes events that are logged when users take actions on power schemes or power-state change notifications, when you make these actions available to them through the policy configuration. For example, you can allow users to skip or delay a power-state change or to change the power scheme in the Windows Control Panel.
Event Types	Description	Normal event?
Scheme Changed by User	The end user or a third-party application changed the power scheme through the Windows Control Panel.	yes
Scheme Changed (No Policy)	The end user or a third-party application switched off the enforced policy.	yes
State Change Skipped	The end user chose to cancel a power state change when a notification message appears on their screen.	yes
State Change Delayed	The end user chose to delay a power state change when a notification message appears on their screen.	yes

Table 8. User activity category

Events that indicate whether a user is active or not, whether a transition to a low power state based on idle time is pending, and if user activity is unknown (in which case data and activity collection may have stopped, which will be indicated by an event in the Service Events category).
Event Types	Description	Normal event?
User Active	Mouse or keyboard activity indicates that user is active on a client computer.	yes
User Activity Unknown	The state of user activity is unknown. This can indicate that data collection has stopped or detection APIs have failed.	no
User Idle	Mouse or keyboard activity indicates that user is not active on a client computer.	yes
User Idle Pending	Mouse or keyboard activity indicates that user is not active on a client computer, and a transition to a low power state is pending.	yes

**Table 9. Configuration errors category**

Errors setting, querying, or deleting a power scheme; changing wake settings on mouse, keyboard (including whether it’s a USB device); or loading, parsing, or saving .config files.
Event Types	Description	Normal event?
Scheme Set API Failure	An error occurred setting the power scheme in the operating system.	no
Scheme Get API Failure	An error occurred while querying the power scheme in the OS.	no
Scheme Delete API Failure	An error occurred while deleting the power scheme in the OS.	no
Wake Mouse Failure	Mouse movement failed to wake client.	no
Wake Keyboard Failure	Keyboard use failed to wake client.	no
Wake USB Failure	Use of USB device (mouse, keyboard) failed to wake client. (Registry setting is required on Windows XP)	no
Wake Network Failure	Client did not wake because of failed network card settings.	no
Logging Config Failure	Failed to update the logging configuration.	no
Server Config Load Failure	Failed to load the Surveyor server config file.	no
Server Config ParseFailure	Failed to parse the Surveyor server config file.	no
Server Config Save Failure	Failed to save the Surveyor server config file.	no
EnergyWise Config Load Failure	Failed to load the EnergyWise proxy server config file (applies only to environments where client is configured for an EnergyWise domain).	no
EnergyWise Config Parse Failure	Failed to parse the EnergyWise proxy server config file (applies only to environments where client is configured for an EnergyWise domain).	no
EnergyWise Config Save Failure	Failed to save the EnergyWise proxy server config file (applies only to environments where client is configured for an EnergyWise domain).	no

**Table 10. Policy errors category**

Errors that prevent a PSTM rule from running. For example, PSTM fails to veto a power state change, terminate an application, or report that an application has terminated.
Event Types	Description	Normal event?
Script Failure	A PSTM script threw an exception.	no
Check Condition Failure	There was an error while checking for a PSTM condition.	no
Veto Failure	There was an error when the PSTM attempted to veto a state change as specified in a PSTM rule.	no
Application Terminate Failure	There was an error when the PSTM attempted to terminate an application as specified in a PSTM rule.	no
Application Detect Failure	There was an error when the PSTM attempted to report that an application was running.	no
Idle Timer Block Failure	There was an error when the PSTM attempted to block the idle timer (when PSTM rule specifies to stop transition if a particular application is running).	no

**Table 11. Service errors category**

Errors that cause the client service to stop running properly. For example, the client computer loses power abnormally; the service fails to parse or run a request from the power management service; performance counter for the idle timer missing or failed; errors that occur while querying the user or display state.
Event Types	Description	Normal event?
Service Crash	The client service terminated unexpectedly. This is detected the next time the service starts.	no
Abnormal Power Off	The client computer was turned off in an abnormal way. For example, a power outage or computer was unplugged. This is detected the next time the service starts.	no
Resume Power Failed	The client machine lost power after going into suspend. (Also detected at service start.)	no
Usage Query Failure	An error occurred while querying the state of user activity.	no
Display Query Failure	An error occurred while querying the state of display activity.	no
Scheduler Failure	An error occurred in the scheduler module.	no
PMP Message Parse Failure	Failed to parse a PMP (power management protocol service) message, such as a power state transition request.	no
PMP Message Dispatch Failure	Failed to execute a PMP (power management protocol) message, such as a power state transition request.	no
Device Query Failure	Failed while executing a device query. For example, to get a list of network adapters.	no
Performance Counter Missing	A performance counter that is used with the Surveyor idle timer is missing.	no
Performance Counter Failure	A performance counter that is used with the Surveyor idle timer failed.	no

**Table 12. Transition errors category**

Problems that occur when the API for a power state transition is called but returns a failure code; errors occurring while processing a power state transition; failure to dispatch a Wake on LAN magic packet; unexpected errors while trying to prevent narcolepsy (computer transitions to sleep while in use).
Event Types	Description	Normal event?
Sleep Failure	The sleep API was called, but it returned a failure code.	no
Shutdown Failure	The shutdown API was called, but it returned a failure code.	no
Hibernate Failure	The hibernate API was called, but it returned a failure code.	no
Sleep General Failure	An unexpected error occurred while processing a sleep request.	no
Shut Down General Failure	An unexpected error occurred while processing a shutdown request.	no
Hibernate General Failure	An unexpected error occurred while processing a hibernate request.	no
Wake on WAN Dispatch Failure	Failed to dispatch the Wake on WAN magic packet (UDP broadcast).	no
Narcolepsy Prevention Failure	There was an unexpected error while trying to prevent narcolepsy (condition in which the client transitions to a sleep state while still considered active).	no

**Table 13. EnergyWise power level category**

Events that occur in the setting or operation of any of the 11 EnergyWise power levels.
Event Types	Description	Normal event?
Set to Level 0 [1, 2, 3,...,10]	Client's EnergyWise level was set to zero [or to 1, 2, 3,...,10] through the Administrator console.	yes

See also

Topics under "Viewing diagnostic information from event logs" in the Surveyor 6 Administrator Guide.

Applies to

Product

Surveyor 6

Log in or register to post comments

Contact us for a free demo