The level of access (full or limited) that the monitoring service has to the selected target.
Determine what happens when a SQL Sentry condition is met (i.e. send an email, log to database, execute PowerShell, etc.).
Event category applicable to customized alerting based on performance counter metrics, query results, or duration of events. Example: CPU > 90%.
Event category applicable to various activities carried out inside and outside of the SQL Sentry client. Example: Performance counter added, snooze status changed, watched flag changed, and more.
Describes the various states of an event object or associated performance counter (i.e. CPU > 90%).
Local client installed for SentryOne Monitor to configure the monitoring environment.
Allows the SQL Sentry components (such as the monitoring service) to be remotely managed when using the Enhanced Platform Installer (EPI).
The Environment Health Overview score view works by incorporating alerts and their associated severity to calculate the scores. A high health score (with a maximum of 100 possible) is an indicator of good health. The score for these views is based on the severity of all open alerts within the selected time period. The severity points are as follows: Info - 0 points, Low - 1 point, Medium - 3 points, High - 6 points, Critical - 9 points The weight of an open alert diminishes with its age. The score being presented is 100 minus the sum of the weighted value of open alerts. Closed alerts are not factored into the score.
The Enhanced Platform Installer allows for the automation of upgrades and deployments of the SQL Sentry platform with a command line interface experience.
Series of dependencies between events running on the same server or different servers.
A category of alerts applicable to events on watched targets. Examples: A deadlock occurred, there is blocking SQL, a SSAS command exceeded its maximum duration threshold, a Windows task failed, and more.
Any job, task, or other event type that can be managed using SQL Sentry.
Represents a unique instance of an event provider operating over a single event store connection. Examples include SQL Server Agent Jobs and Windows Tasks.
Event category applicable to connection status and error situations. Examples: A watched Azure SQL Database is online or offline (status changed from one to the other), a configured action failed to execute, and more.
SQL Sentry Access Level in which the monitoring service collects Windows level metrics and provides you with full access to the features of Performance Analysis.
Applicable to monitored event objects or associated performance counters.
Used to deploy SQL Sentry on a user's system.
Instance of SQL Server or SSAS, or an installation of SharePoint that exists on a Target in your environment.
Allows a resource intensive job to delay other jobs from executing until it completes.
Content menu option that opens another screen or tab in SQL Sentry to access additional information for the same time period selected on the current screen.
SQL Sentry Access Level in which the monitoring service doesn't collect performance counters, and access to the Windows Dashboard, Disk Activity tab, Disk Space tab, and Windows Processes tab are restricted.
The Windows service responsible for collecting data. Also reads configuration data from the SQL Sentry database.
A comprehensive snapshot of activity created by combining process-level data and trace events collected during a brief sample period.
Controls how often Actions are taken in response to met Conditions.
The installed client software application. It is used to visualize SQL Sentry data and configure monitoring service behavior.
A user that exists in SQL Sentry under Contacts > Users.
SentryOne Contact Group
A group of users that exists in SQL Sentry under Contacts > Groups.
Used to store data collected from the monitoring service and configuration information set by the client. The default name for the database is SQLSentry, but has been SentryOne in older releases.
SentryOne Monitor Cloud
A browser-based SQL Server performance monitoring product in a cloud solution.
Policies within SQL Sentry refer to settings and pairs of conditions and actions that are applied to groups, such as object groups. These policies are not related to Group Policy in Windows or Policy-Based Management in SQL Server.
SentryOne Portal On-Premises
A browser-based option for accessing your installed SQL Sentry software environment data that uses your existing SQL Sentry database. It replaces the previous mobile applications and Cloud Sync options.
SentryOne Portal Service
If using the self-hosted version of SQL Sentry Portal, this service runs on the machine where the portal is installed.
SentryOne Scalability Pack
Implements partitioned clustered columnstore indexing, In-memory OLTP, and additional optimizations to achieve maximum scalability and performance.
SentryOne Test _Assets Folder
The folder containing the content(s) for your assets at design time.
SentryOne Test _Output Folder
The folder containing the code that's generated from your group file, along with some other files.
SentryOne Test Actions
Test components that produce an outcome, and are needed to perform the test assertion. Information returned from actions are stored in resources, and actions often use assets or resources as part of their input.
SentryOne Test Annotations
Annotations allow meaningful descriptions to be assigned to tests and appear on the test management page for a test.
SentryOne Test Assembly Run Logs
Displays details about the test assembly runs within your testing environment.
SentryOne Test Assert
Test component that’s used to test the results of actions. Asserts compare the values in resource keys to each other, or to a static value entered into the Assert.
SentryOne Test Assertions
Assertions contain test validations that determine if a test passes or fails. Assertions run immediately after all execution tracks for the current test are complete, and compare expected data to actual data generated during the execution tracks. The results of these data comparisons dictate whether the test passes or fails.
SentryOne Test Asset
Items that the action needs in order to run (connection strings, queries, package references, etc.).
SentryOne Test Data Driven Testing
Data-driven testing allows you to repeat the same test many times, based on dynamic source data.
SentryOne Test Data Testing Dashboard Summary
The Summary displays graphical information about the tests completed in your environment for a quick at-a-glance overview.
SentryOne Test Design Area
Where you add your test elements. The area is divided into the different test flow steps and changes depending on whether a single test, or a test group is selected. Test elements are executed first from left to right, then top to bottom.
SentryOne Test Execution Details
View detailed statistics about the execution of a selected test assembly or object.
SentryOne Test Execution History
View detailed statistics about the execution of a test assembly within your testing environment.
SentryOne Test Execution Tracks
Contains the actual elements that compose the test. Each test can hold any number of tracks.
SentryOne Test Group Initialization Steps
The first step to run before any tests are actually executed. Group initialization steps execute only once at the beginning of the entire test group.
SentryOne Test Group Level Test Initialization Steps
This step executes once at the beginning of every test in the group before the actual test begins.
SentryOne Test Group Level Test Teardown steps
This step executes once at the end of every test execution in the group and configures everything that's needed to clean the test environment after each test completes.
SentryOne Test Group Teardown Steps
This step executes only once at the end of the entire test group and configures everything needed to clean the test environment once group execution completes.
SentryOne Test Groups
Test component that can contain assets, and multiple tests. Groups can manage the Group and Test Level Initialization, and Group and Test Level Teardown steps.
SentryOne Test Notification Engine
Used to create and manage test subscriptions and test actions.
SentryOne Test Project
A test project can contain assets and test groups.
SentryOne Test Recipe
A simple way to create tests based around smaller pieces of functionality that help you to get quickly started with testing.
SentryOne Test Remote Agent
A Windows service installed close to your data sources in the cloud or on premises that can be used to schedule and run tests remotely, and update your test results to the SentryOne Cloud.
SentryOne Test Resources
Items that are available only at runtime. Resources are referred to by their resource key (a string that uniquely identifies that resource). Resources are usually loaded by actions, and can be referenced by other actions or assertions.
SentryOne Test Test Initialization Steps
This executes once at the beginning of a single test and configures unique elements needed to prepare this test for execution.
SentryOne Test Test Teardown Steps
This step executes once at the end of a single test and configures unique elements that are needed to clean the test environment after test execution.
SentryOne Test Tests
Tests can contain assets and manage the Test Initialization Steps, Execution Tracks, Assertions, and Test Teardown Steps.
SentryOne Test Visual Studio Extension
Allows you to create tests that verify the quality of your data integrity in MSTest or NUnit frameworks. Implement tests without needing to write complex logic for key matching or data comparisons.
Service Configuration Utility
Used to configure monitoring service after installation and change service account information.
A logical groupings of targets, instances, SMTP servers, and Monitoring services within your SQL Sentry environment.
SQL Sentry Scheme Handler
Process used to route messages selected within emails to the SQL Sentry client.
Device that houses your data; whether it's a physical server, cloud installation, or APS appliance.
Allows you to create logical groups of devices for alerting, organizational, and display purposes. Target groups represent an intermediate level between the Site and Target. Conditions and settings at the target group level automatically propagate down to its associated Targets, Instances, and objects.
Devices that house your data; whether it's a physical server, cloud installation, or APS appliance.
Task Factory Connection Manager
The Connection Manager component stores the settings for a connection that’s used within your package, and creates the connection during the package runtime. Connection Managers store your ConnectionString to your component, and can be used in multiple packages.
Task Factory Destination
Destination Components are used to determine how your data sources upload data in the dataflow within your package.
Task Factory Error Row Handling
Specifies an action to take place when your component encounters an error within the package. Error Row Handling is available for select components within Task Factory.
Task Factory Source
Source Components store information for data sources that are used within your package, and include a connection string and source identifier.
Task Factory Task
Task components are used to perform a specified action within your package.
Task Factory Transform
Transform components allow you to make changes to the data sources in the data flow within your package. Use transforms to aggregate, merge, distribute, modify, perform lookup operations, and generate sample datasets in your package.
A web-based client to view SentryOne Cloud Monitor.
Monitor with SQL Sentry
Monitored by SQL Sentry.
SQL Sentry visual representation containing wedges of information.