Search - Control Center

Monitoring

Using Control Center » Monitoring

In this section, we’ll be familiarized with how the Monitoring Module works. When opening the monitoring module on its initial state, you get the status dashboard: The status dashboard is intended to provide a quick overview of the current state of your…

Monitoring

Customization » Monitoring

Custom monitoring and editing monitoring jobs dbWatch has two types of monitoring jobs that can detect issues in the database instances. They are referred to as Engine jobs and “No-engine jobs”. Engine jobs are jobs that run inside the database engine,…

Repository management and monitoring

Installing and using additional modules » SQL Performance package » Repository management and monitoring

Introduction The SQL Performance package creates tables in the dbWatch schema/database on each database instance where the SQL Statistics job is installed and scheduled. The process combines two parts of dbWatch Control Center. The monitoring is used to schedule the…

Control Center Jobs

Using Control Center » Monitoring » Control Center Jobs

Jobs (older dbWatch versions Tasks and alerts) are the cornerstone of the dbWatch Monitoring module. Jobs perform the actual monitoring of the database instance. There are two types of Monitoring in dbWatch. The Basic and Standard monitoring. To see each monitoring…

Parameters

Using Control Center » Monitoring » Job concepts » Parameters

Most of the monitoring jobs will have parameters. This is used controllable thresholds to adjust the monitoring job behavior and to better align it with the database instance and the preferences of the DBA. This is an example from the “Agent jobs check”…

Adding an Oracle Instance

Using Control Center » Instance management » Adding an Oracle Instance

Oracle Prerequisites !1. Oracle databases need to have a listener process running and also allow for an external login with sysdba user or user with enough privileges. 2. You need a privileged user, such as sys as sysdba, another user with sysdba privileges or…

Instance details

Using Control Center » Monitoring » Instance details

When navigating to an individual database instance, you get the instance details overview: This dashboard is intended to give an overview of what monitoring jobs are installed and how they are performing. The top tabs let you switch between the instance details…

Adding a PostgreSQL Instance

Using Control Center » Instance management » Adding a PostgreSQL Instance

How to get here To open the “Add Instance Wizard”, click on the “Plus (+)” sign on the bottom left of the dbWatch Client. This will bring up the “Add Instance” wizard, which will guide you through the following steps. Select Instance Type and Input…

Instance Configuration

Using Control Center » Instance management » Instance Configuration

How to get here Instance Configuration can be accessed by going to Server > Server Configuration > Instance Configuration. Main view The instance configuration view consists of several parts. On the left side you see a tree are the list of your instances…

Using Control Center

In this section, we will cover the user interface, the different modules, and how they are used. When we start dbWatch Control Center we will by default start-up in the monitoring view: We have the top menu, where we find the configuration of client connections…

Architecture

Product Overview » Architecture

Architecture components The dbWatch installation consists of three components: dbWatch Monitor/Client serves as the front-end GUI dbWatch Server is the core business logic and central hub of the system dbWatch Framework contains stored objects in the registered…

Customization

dbWatch Control Center is designed to be customizable and much of the contents are developed inside the product In this section, we will go over how you can customize different parts of the product. To proceed, click on of the topics below: Customize dbWatch Views…

Installation variables

Customization » Monitoring » Editor for engine jobs » Installation variables

Installation variables are used if you want user input during job installation. It is mostly used for application-specific monitoring where the application schema or database can not be determined correctly by the job after installation and human input are…

Adding a SQLServer Instance

Using Control Center » Instance management » Adding a SQLServer Instance

How to get here To open the “Add Instance Wizard”, click on the “Plus (+)” sign on the bottom left of the dbWatch Client. Select Instance Type and Input Connection Details Specify the host and port number. dbWatch will attempt to…

Managing nodes

Using Control Center » Domain Configuration » Managing nodes

Nodes In the node configuration there are 2 editable fileds. The displayname and the approved checkbox. This is were you approve new Servers that want to join the domain. In addition you can see the type (currently server and/or domaincontroller) and id for the…

Adding a MySQL Instance

Using Control Center » Instance management » Adding a MySQL Instance

How to get here To open the “Add Instance Wizard”, click on the “Plus (+)” sign on the bottom left of the dbWatch Client. This will bring up the “Add Instance” wizard, which will guide you through the following steps. Select Instance Type and Input…

SQL Performance package

Installing and using additional modules » SQL Performance package

SQL Performance package SQL Performance module is an optional module in dbWatch Control Center that allows for historical monitoring and analysis of SQL Statements in the database instance. Currently supported platforms: MS SQL Server 2014 and newer Oracle 11g and…

Database operations philosophy

Product Overview » Database operations philosophy

The reasons for database operations The value of database operations comes from the value of the systems the databases support. . In a typical operation, the value of the managed systems is much greater than the resources used on the operations side. Running a…

Job concepts

Using Control Center » Monitoring » Job concepts

This section will try to explain more in-depth some of the concepts used in monitoring jobs in Control Center. There are currently two types of jobs, engine jobs, and no-engine jobs. The main difference between them is where processing occurs. Engine jobs do the…

No-engine jobs

Customization » Monitoring » No-engine jobs

No-engine jobs No-engine jobs are monitoring jobs that does not run in the database engine. No-engine jobs are jobs that run on the dbWatch Server, and typically run a SQL statement and process the result of this statement in javascript. Example code for different…

Job details

Using Control Center » Monitoring » Job details

When you click on one of the jobs in the job tree, you can see a more detailed job overview. The idea of this overview is to show current and historical state, configured parameters and how the job is behaving on other database instances. In the top left…

Changing Instance Group

Using Control Center » Instance management » Groups Configuration » Changing Instance Group

Changing a group can be done when you created an instance under a default group name and change it to another corresponding group. To change the groups base on your newly created group, you can check Group Configuration. Changing Group of an Instance Once a group has…

Database Farm Management Additional Resources

Additional Resources » Database Farm Management Additional Resources

Blogs For farm management, we have different blogs discussing this topic: From SQL Instance Management to Database Farm Management dbWatch Control Center for managing Database Farms Does managing database server farms differ from database instances? Tips: How you…

About dbWatch Control Center

dbWatch Control Center is a highly scalable software solution helping enterprises monitor and manage large numbers of database servers efficiently, providing total control over all aspects of operation, performance, and resource usage. dbWatch Control Center will give…

Jobs grouped by category

Using Control Center » Monitoring » Control Center Jobs » Jobs grouped by category

Jobs by category Jobs in Control Center are grouped by category to make it easier for users to locate the right monitoring job. The categories are: Availability Jobs that checks that the database and database related processes are functioning Capacity – Jobs…

Example architecture designs

Product Overview » Architecture » Example architecture designs

Basic setup The most basic setup is where a dbWatch Server service is configured with all functions in the same node, and the client is either local or installed on a separate computer. Example drawing: The pictured architecture is similar to the design and setup…

Troubleshooting issues in SQL Performance package

Installing and using additional modules » SQL Performance package » Repository management and monitoring » Troubleshooting issues in SQL Performance package

Graph issues with monitoring has been switched off If for some reason dbWatch Control Center has not been connected to a database instance running SQL Performance package for an extended time, you can get odd statistics errors in the graphs. It will look like a linear…

Category line chart

Customization » Management » Result types » Graphical » Category line chart

A category line chart example The specification for this chart SELECT rtrim(ltrim(instance_name)) "Type", cntr_value "Value" FROM sys.dm_os_performance_counters where counter_name like 'Lock Requests/sec%' and instance_name in ( select top 6…

Service groups

Using Control Center » Instance management » Service groups

In dbWatch you can organize instances in servicegroups Instances placed in the same servicegroup should provide a common service of some sort. For example this can be instances belonging to the same cluster. Servicegroups may also be placed inside other…

Privileges and actions map

Using Control Center » Domain Configuration » Privileges and actions map

Overview of actions and required privilege Instance is the specific database instance. Instance system is a predefined security group controlling the overall instance monitoring and management. Domain configuration is a predefined security group controlling the…

Job menus

Using Control Center » Monitoring » Job menus

Each job has a set of menus. They can be accessed if you right-click on a job. This gives you several options. “Run now” will trigger the job now, outside of the normal schedule. “Details” will open the job report, providing details about…

Definition Mapping

Troubleshooting Guide » Definition Mapping

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.…

The modules of Control Center

Using Control Center » The modules of Control Center

We have seven default modules available when you start dbWatch Control Center. This article will only introduce you to what these instances are and give a brief description of them. You need to be familiar with the navigation tree to better understand how these modules…

FAQs

Additional Resources » FAQs

In this section – you will find the frequently asked questions regarding the dbWatch. Do you offer an evaluation copy of your product? - Yes, we do offer a 30-day trial for a maximum of 25 database instances of any database platforms supported. We can also…

Properties

Customization » Monitoring » Editor for engine jobs » Properties

The properties section defines the main settings for the job. Once a job is created the “Task name”, “Company” and “Compatibility” is specified. “Task name” is the visible job name when you install a job or when its…

Editor for engine jobs

Customization » Monitoring » Editor for engine jobs

How to get here Example jobs We have some example jobs to make the development easier here. Edit Existing To edit an existing Task or Alert open the Task/Alert Editor by right clicking on any task or alert and select Edit task from the popup menu. Create new…

Tree navigation

Using Control Center » Monitoring » Tree navigation

On the left side of the dbWatch monitor, you will see a tree structure. There are 2 component that lets your group and filter instances. Top level of the tree, there is a “Grouping” panel. Below it is a quick text based filter. Grouping This is always…

Release notes

About dbWatch Control Center » Release notes

dbWatch Control Center (2023-04-27) Download Known bugs Problem with driver autodetection, so adding SQL Server 2005 and 2008, requires manually changing the JDBC driver during add instance dialogue to the 9.4.0 version of the driver. Problem may occur when…

Customize View using FDL

Customization » Monitoring » Customize View using FDL

Before proceeding to this section, you must be familiar with Farm Data Language. To give you an overview, Farm Data Language is a type of query dbWatch uses to read and display data to its user. Think of it as your query tool when using dbWatch. How to edit…

Platforms supported

About dbWatch Control Center » Platforms supported

Platforms supported for the main product. Current release supports the following platforms, versions, and setups: On-premise support Supports* Express edition, Standard edition, Standard edition one, Standard edition two, and Enterprise edition of the following…

Using SQL Performance package on MySQL

Installing and using additional modules » SQL Performance package » Using SQL Performance package on MySQL

Navigating to the SQL Performance package dashboard Once the SQL statistics job is installed and have collected data, you can navigate to the dashboard. It is located in the management interface for that database instance. The pictures and descriptions are from…

Email and SMS

Customization » Extensions and 3rd party integrations » Email and SMS

Configure In the dbWatch Monitor, go to the “Server”->”Server Extensions” menu. An item called “E-mail extension” should now be visible (v 5.2 or later). To configure the extension, select it and click “Configure”. You should now see the initial…

Main procedure SQL Server

Customization » Monitoring » Editor for engine jobs » Implementation » Main procedure SQL Server

We will use the “Test alert” as example code, as its only purpose is to generate alarms and warnings, but uses many underlying functions. We go through it in steps, and include the full routine at the end. For historical reasons some code will refer to…