A database monitoring system

Abstract

The present invention relates to a system (1) for making all databases (V) monitorable according to flexible rules; intervening to problems quickly by generating alarms during or before any problem; defining alarms specific for all environments or specific for certain groups; enabling the operating frequencies of alarms to be in different time intervals; incorporating new databases (V) into automatic monitoring without any external intervention by being built in an autonomous structure; and deploying alarm and monitoring definitions within seconds.

Description

[0001] A DATABASE MONITORING SYSTEM

[0002] Technical Field

[0003] The present invention relates to a system for making all databases monitorable according to flexible rules; intervening to problems quickly by generating alarms during or before any problem; defining alarms specific for all environments or specific for certain groups; enabling the operating frequencies of alarms to be in different time intervals; incorporating new databases into automatic monitoring without any external intervention by being built in an autonomous structure; and deploying alarm and monitoring definitions within seconds.

[0004] Background of the Invention

[0005] Today, in addition to Oracle Enterprise Manager, which is the monitoring tool of Oracle, the process of monitoring databases is carried out with custom monitoring tools. Even though Oracle Enterprise Manager is a capable product, it is insufficient in terms of custom alarm definitions and as it operates on an agent basis, it both requires deployment and has update management difficulties. In addition to these, the rate of false alarms is also quite high. The definition of alarms cannot be defined in line with specific targets or new alarms cannot be added. With the developed custom monitoring tool, the deficiencies of Oracle Enterprise Manager were tried to be eliminated, however, it is necessary to initiate a new product development process due to the fact that this product is written in an old programming language, the need for continuous maintenance and the low success in alarm reliability. For this reason, considering the studies and deficiencies included in the current technique, it is understood that there is a need for a system which enables the development of a new monitoring product that scans and updates inventory thereof on its own, by developing a highly accessible, autonomously operating and highly flexible architecture and by programming these developments with the current programming language Python and by combining Python code with the Procedure and SQL in Oracle.

[0006] The Chinese patent document no. CN115796918, an application included in the state of the art, discloses a real-time data supply system. The invention subject to the said Chinese patent document relates to the field of data processing and provides a real-time data supply method and device for a user portrait and a storage medium. According to the main scheme, the method comprises the steps that a basic data table is established, an OGG source end is deployed in an upstream system, an E process of the OGG source end is responsible for reading an archiving log of ORACLE and writing update. Importing a database into a train file, and a P process is responsible for monitoring changes of a local train file and pushing the update to a train file directory of a target end through a TCP / IP protocol; the target end R process monitors local trail file update, and then sends the update to the KAFKA; and the FLINK reads data in the KAFKA, and inserts the data into the basic data table by defining write-in and write-out streams. And data of recent ten minutes are taken from the transaction data according to the timestamp and are synchronized to a database, so that a user portrait system can inquire the data in real time.

[0007] Summary of the Invention

[0008] An object of the present invention is to realize a system developed for making all databases monitorable according to flexible rules; intervening to problems quickly by generating alarms during or before any problem; defining alarms specific for all environments or specific for certain groups; enabling the operating frequencies of alarms to be in different time intervals; incorporating new databases into automatic monitoring without any external intervention by being built in an autonomous structure; and deploying alarm and monitoring definitions within seconds.

[0009] Detailed Description of the Invention

[0010] “A Database Monitoring System” realized to fulfd the objective of the present invention is shown in the figure attached, in which:

[0011] Figure 1 is a schematic view of the inventive system.

[0012] The components illustrated in the figure are individually numbered, where the numbers refer to the following:

[0013] 1. System

[0014] 2. Electronic device

[0015] 3. Interface

[0016] 4. Server

[0017] V. Database

[0018] L. Linux Operating System

[0019] OG: Oracle Grid Cluster

[0020] G. Grid Infrastructure

[0021] OR. Oracle RAC Database

[0022] OE. Oracle Enterprise Manager

[0023] OBM. Operations Bridge Manager

[0024] The inventive system (1) developed for making all databases (V) monitorable according to flexible rules comprises at least one electronic device (2) which is configured to exchange data by using any remote communication protocol and to run at least one application thereon; at least one interface (3) which is configured to be run on the electronic device (2) and to enable the database (V) monitoring software to be developed with Python programming language thereon; at least one server (4) which is configured to establish connection with the electronic device (2) by using any communication protocol; and to establish communication with the interface (3) run on the electronic device (2) through this established connection; to enable the databases (V) to be monitored; to enable problems to be intervened quickly by generating alarms during or before any problem; to enable alarms to be defined specific for all environments or specific for certain groups; to enable the operating frequencies of alarms to be in different time intervals; to be built in an autonomous structure; to incorporate new databases (V) into automatic monitoring without any external intervention.

[0025] The electronic device (2) included in the inventive system (1) is configured to exchange data by using any remote communication protocol and to run at least one application thereon. The electronic device (2) is a device in the form of a desktop computer and / or portable computer. The electronic device (2) is configured to run the interface (3) thereon. The electronic device (2) is configured to establish connection with the server (4) by using any remote communication protocol included in the state of the art.

[0026] The interface (3) included in the inventive system (1) is configured to be run on the electronic device (2). The interface (3) is configured to enable the database (V) monitoring software to be developed with Python programming language thereon. The server (4) included in the inventive system (1) is configured to establish connection with the electronic device (2) by using any communication protocol included in the state of the art, and to establish communication with the interface (3) run on the electronic device (2) through this established connection. The server (4) is configured to run the Oracle Grid Cluster (OG) on the Linux operating systems (L); to add the monitoring software that is developed with the Python to Oracle Grid Cluster (OG) as a resource by accessing the interface (3); to enable it to operate in a highly accessible manner; and to enable instant service to be provided through the other node autonomously when a problem occurs in any node. The server (4) is configured to save the developed codes as procedures and functions in the Oracle RAC database (OR) installed on the Grid Infrastructure (G); to save the information collected from all databases on this database (V) and to enable alarms to be generated by processing; to enable the databases to operate in a highly accessible manner as they consist of 2 nodes; and to enable the repository database to provide service through the other node when a problem occurs in any node. The server (4) is configured to divide the engine of the developed programme into three parts as "Inventory Update", "Alarm Generation", "Database Status Control"; to control the databases defined on the Oracle Enterprise Manager (OE) during the inventory update phase; to receive the connection information of the databases having container structure and available here; to create the main inventory table of the monitoring tool by extracting various data belonging to the databases by connecting to the respective databases about these information; and to enable the current inventory to be updated by triggering the inventory update at any time of the day while automatically running it once a day. The server (4) is configured to control the alarms to be monitored by using the alarm definition table, the alarm threshold definition table and the inventory tables included in the repository database in alarm generation and alarms included in all databases (V) instantaneously; to feed the active alarm table and trigger alarm generation procedures if there is a situation that will cause an alarm in the metrics it collects; and to automatically trigger alarm generation in the background once a minute. The server (4) is configured to perform connection checks for all databases by using the inventory table during the database (V) status control; not to create an alarm if it can connect in a certain period of time, but to trigger the alarm procedure by creating an alarm for these databases in the active database (V) status table if it cannot connect in the specified time or if the database (V) is in an inaccessible state; and to operate by being automatically triggered in the background once a minute during the database (V) status control. The server (4) is configured to integrate the Blackout structure -which is another feature of Oracle Enterprise Manager- into itself, as it receives the inventory through the Oracle Enterprise Manager (OE); to perform Blackout definition before the maintenance work performed on the databases (V) on the Oracle Enterprise Manager (OE); to update the Blackout information of the databases (V) in its own inventory by detecting if a Blackout definition has been made on a database (V) via the monitoring software; and therefore to prevent unnecessary alarms from being generated in the databases (V) on which work is performed. The server (4) is configured to transfer alarms to the Operations Bridge Manager (OBM) in the event of alarm occurrence; to initiate the process of dealing by the relevant teams via the OBM; and to make alarm definitions via the tables on the repository database (V). The server (4) is configured to perform a front-end design by integrating the Qliksense product and to present some features such as summary information of the databases (V), active statuses and graph statuses on Qliksense by using the collected metrics. The server (4) is configured to develop an artificial intelligence-based recommendation engine that works with reinforcement learning methods by artificial intelligence according to the collection time intervals and threshold values of the periods determined in Artemis alarms of Active Session and Tablespace Early Warning alarms. The server (4) is configured to establish an optimization wherein reinforcement learning agents are managed that can dynamically change the way whereby Active Session and Tablespace Early Warning alarms that work with Large Language Models (LLMs) are collected.

[0027] Industrial Application of the Invention In the inventive system (1), the server (4) establishes connection with the electronic device (2) by using any communication protocol and establishes communication with the interface (3) run on the electronic device (2) through this established connection; enables databases (V) to be monitored; enables problems to be intervened quickly by generating alarms during or before any problem; enables alarms to be defined specific for all environments or specific for certain groups; enables the operating frequencies of alarms to be in different time intervals; is built in an autonomous structure; incorporates new databases (V) into automatic monitoring without any external intervention.

[0028] Within these basic concepts; it is possible to develop various embodiments of the inventive “A Database Monitoring System (1)”; the invention cannot be limited to examples disclosed herein and it is essentially according to claims.

Claims

CLAIMS1. A system (1) developed for making all databases (V) monitorable according to flexible rules; comprising at least one electronic device (2) which is configured to exchange data by using any remote communication protocol and to run at least one application thereon; at least one interface (3) which is configured to be run on the electronic device (2) and to enable the database (V) monitoring software to be developed with Python programming language thereon; and characterized by at least one server (4) which is configured to establish connection with the electronic device (2) by using any communication protocol; and to establish communication with the interface (3) run on the electronic device (2) through this established connection; to enable the databases (V) to be monitored; to enable problems to be intervened quickly by generating alarms during or before any problem; to enable specific alarms to be defined specific for all environments or specific for certain groups; to enable the operating frequencies of alarms to be in different time intervals; to be built in an autonomous structure; to incorporate new databases (V) into automatic monitoring without any external intervention.

2. A system (1) according to Claim 1; characterized by the electronic device (2) which is a device in the form of a desktop computer and / or portable computer; and is configured to exchange data by using any remote communication protocol and to run at least one application thereon.

3. A system (1) according to Claim 1 or 2; characterized by the electronic device (2) which is configured to run the interface (3) thereon.

4. A system (1) according to Claim 3; characterized by the electronic device (2) which is configured to establish connection with the server (4) by using any remote communication protocol.

5. A system (1) according to any one of the preceding claims; characterized by the interface (3) which is configured to be run on the electronic device (2).

6. A system (1) according to any one of the preceding claims; characterized by the interface (3) which is configured to enable the database (V) monitoring software to be developed with Python programming language thereon.

7. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to establish connection with the electronic device (2) by using any communication protocol, and to establish communication with the interface (3) run on the electronic device (2) through this established connection.

8. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to run the Oracle Grid Cluster (OG) on the Linux operating systems (L); to add the monitoring software that is developed with the Python to Oracle Grid Cluster (OG) as a resource by accessing the interface (3); to enable it to operate in a highly accessible manner; and to enable instant service to be provided through the other node autonomously when a problem occurs in any node.

9. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to save the developed codes as procedures and functions in the Oracle RAC database (OR) installed on the Grid Infrastructure (G); to save the information collected from all databases on this database (V) and to enable alarms to be generated by processing; to enable the databases to operate in a highly accessible manner as they consist of 2 nodes; andto enable the repository database to provide service through the other node when a problem occurs in any node.

10. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to divide the engine of the developed programme into three parts as "Inventory Update", "Alarm Generation", "Database Status Control"; to control the databases defined on the Oracle Enterprise Manager (OE) during the inventory update phase; to receive the connection information of the databases having container structure and available here; to create the main inventory table of the monitoring tool by extracting various data belonging to the databases by connecting to the respective databases about these information; and to enable the current inventory to be updated by triggering the inventory update at any time of the day while automatically running it once a day.

11. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to control the alarms to be monitored by using the alarm definition table, the alarm threshold definition table and the inventory tables included in the repository database in alarm generation and alarms included in all databases (V) instantaneously; to feed the active alarm table and trigger alarm generation procedures if there is a situation that will cause an alarm in the metrics it collects; and to automatically trigger alarm generation in the background once a minute.

12. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to perform connection checks for all databases by using the inventory table during the database (V) status control; not to create an alarm if it can connect in a certain period of time, but to trigger the alarm procedure by creating an alarm for these databases in the active database (V) status table if it cannot connect in the specified time or if the database (V) isin an inaccessible state; and to operate by being automatically triggered in the background once a minute during the database (V) status control.

13. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to integrate the Blackout structure -which is another feature of Oracle Enterprise Manager- into itself, as it receives the inventory through the Oracle Enterprise Manager (OE); to perform Blackout definition before the maintenance work performed on the databases (V) on the Oracle Enterprise Manager (OE); to update the Blackout information of the databases (V) in its own inventory by detecting if a Blackout definition has been made on a database (V) via the monitoring software; and therefore to prevent unnecessary alarms from being generated in the databases (V) on which work is performed.

14. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to transfer alarms to the Operations Bridge Manager (OBM) in the event of alarm occurrence; to initiate the process of dealing by the relevant teams via the OBM; and to make alarm definitions via the tables on the repository database (V).

15. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to perform a front-end design by integrating the Qliksense product and to present some features such as summary information of the databases (V), active statuses and graph statuses on Qliksense by using the collected metrics.

16. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to develop an artificial intelligence-based recommendation engine that works with reinforcement learning methods by artificial intelligence according to the collection time intervals and thresholdvalues of the periods determined in Artemis alarms of Active Session and Tablespace Early Warning alarms.

17. A system (1) according to any one of the preceding claims; characterized by the server (4) which is configured to establish an optimization wherein reinforcement learning agents are managed that can dynamically change the way whereby Active Session and Tablespace Early Warning alarms that work with Large Language Models (LLMs) are collected.

Images