In-depth guides for all the event and calendar types, objects, sources, views, and event architecture in SentryOne software (SQL Sentry).
Earlier versions of SentryOne focused on agent jobs; however, this is no longer the case. SentryOne's current architecture enables monitoring and management of jobs, tasks, and status events.
An event object is any job, task, or event type that can be managed using SentryOne. There are two general types of event objects, including active and status event objects.
An event source represents a unique instance of an event provider operating over a single event store connection.
An event chains is a series of dependencies between events running on the same server or different servers.
Job queuing allows a resource intensive job to delay other jobs from executing until the job completes.
Calendar & List Views
The event calendar combines historical and future event data to present an accurate visual representation of your schedule.
The history filter allows you to define rules that control what types of events the monitoring service writes into event history concerning the monitored servers.
Custom Event Views
Custom Event Views tailor views to monitor specific activity across the SQL Server and enterprise.
Sample Views & Shared Resources
Sample views are modified to restrict event instances to utilize the same shared resources, such as a Network Attached Storage (NAS), Storage Area Network (SAN) device, or even a network segment.
Job Step / SSIS Logging
The SentryOne Event Calendar is capable of collecting and displaying extended step log data for SQL server agent job steps on the SQL server 2005 and above.
The Runtime Stats node displays an active event object's historical runtime information. The Runtime Stats graphs make it easy to identify runtime trends that can be indicators of or eventually lead to performance issues with the event or server.
When a certain event has failed, there are several ways the SentryOne client signals you to that fact.
Event conflicts often contribute to performance problems on a SQL server. The Conflict Viewer provides valuable insight into how event schedulers are contending with each other.