| dbWatch 12 |
dbWatch Control Center |
Definition |
Changes |
| Tasks and Alerts |
Jobs |
Tasks provide statistics and growth rates for your database, which allows for better planning and performance analysis of how your system is behaving. Alerts provide alarms and warning that enables you to react to problems as quickly as possible. |
Basically tasks and alerts are just renamed to Jobs. Which still serves the same purpose. |
| DBWQL (dbWatch Query Language) |
FDL (Farm Data Language) |
FDL is a new and improved query language based on XPath language – you can now query across your database farm even if its across different database platforms. You can perform aggregation and determine the resource usage across your database farm. |
FDL is now part of the Farm Management Module. |
| |
Farm Management |
Farm management module a new feature wherein users can easily monitor the health of the whole database farm. Displays the summary of their performance, capacity and resource usage. |
New feature |
| Memory Reduction |
AMR |
An upgraded feature that will be included within the farm management module. This helps DBAs automate the memory utilization allocation of their database farm. |
Automatic Memory Reduction for SQLServer |
| AutoDiscover |
Database Discovery |
Database Discovery is now a part of the Farm management module which helps discover all database instances within a network range. |
|
| Standard Installation |
Basic Installation |
No packages or procedures are installed within the monitored instances. |
|
| Advanced Installation |
Standard Installation |
Packages and procedures installed within the monitored instances. Recommended way of monitoring the database instances. |
|
| dbWatch Server |
dbWatch Server |
The nerve center of the dbWatch infrastructure. Connects and manages all dbWatch engines installed within the monitored instances. |
|
| dbWatch Client |
dbWatch Client |
Provide the graphical user interface for the dbWatch user, with a highly intuitive and easy to use structure. |
|
| dbWatch Engines |
dbWatch Engines |
dbWatch uses an intelligent database schema inside the database, called dbWatch Engines, for monitoring each database instance. The dbWatch Engine employs two types of monitoring procedures – dbWatch Alerts for real-time alarms and warnings, and dbWatch Tasks for trend analysis and reporting. |
|
| dbWatch Extensions |
dbWatch Extensions |
Extensions are made for easy and seamless integration with your third party systems management tools and processes. |
|
The graph:
| Name |
Definition |
| Node |
A piece of data |
| Link |
data connecting nodes together |
| The graph |
The dbWatch model consists of nodes connected by links |
| Layer |
A piece of the graph that can be turned visible or not |
| Entity |
Addressable nodes in the graph. |
| Metadata |
Data describing Entities in the graph. Metadata can be entities. |
| Named service |
A node in dbWatch representing a service. Is usually connected to several connectors and other named services |
| Instance |
A named service describing a database instance |
| Driver |
The piece of software used by dbWatch to connect to something |
| Connector |
A node representing a configured driver |
| Connected service |
The service that a connector is communicating with |
Events
| Name |
Definition |
properties |
| Event |
Something that has happened or is happening. |
source, start, end |
| Sub event |
An event can contain other events. These are called sub events. |
| Event stream |
The sequence of events. |
| Issue |
A problematic event. |
severity, affected nodes |
| Severity |
Used to describe how problematic a given issue is. |
| Status |
A value describing the health of a node in the graph. Some statuses are aggregates of statuses of sub-nodes |
Jobs:
| Name |
Definition |
| Job |
A unit of work dbWatch can perform |
| Trigger |
A filter of the event stream that starts the execution of a job |
| Schedule |
A timed trigger |
| Compatibility |
An FDL expression describing where the job can be run |
| Installable |
A job that can be installed and configured in the graph |
| Status |
—Discuss— |
| Anchor |
The root node of the job execution. |
| Framework |
A piece of code installed on the connected service to enable the execution of jobs |
| Framework job |
A job relying on installed framework |
Domain
| Name |
Definition |
| Node / Processor / Engine / member??? |
A process managed by the domain. |
| Domain |
A shared configuration used by multiple nodes. A Domain is responsible for identity management and configuration management across its members. |
| Domain name |
The name of a domain. example ‘dbwatch.com’ |
Resources
| Name |
Definition |
| Resource |
A single file containing content for dbWatch |
| Feature |
A set of resources used for publication. A feature is published under a domain and signed by a member of said domain. |
| Archive |
An archive containing a set of features. An archive has name and version |
User / roles / access
| Name |
Definition |
| User |
A human using dbWatch |
| Role |
Granting a role to a user results in privileges. |
| |
|
Secure connect
← Issues and troubleshooting / Resetting dbWatch Control Center Admin Account →
Post your comment on this topic.