Oracle is a widely used relational database management system
(RDBMS). Developed by Oracle Corporation, Oracle RDBMS offers a robust
solution for storing, retrieving, and managing structured data. It
follows the relational model, where data is organized in tables composed
of rows and columns. Oracle provides advanced features such as data
integrity, ACID transactions, multi-platform support, and scalability.
Additionally, it offers a powerful query language called SQL (Structured
Query Language) for performing data manipulation and retrieval
operations. With its extensive adoption in the industry and its ability
to handle large volumes of data, Oracle is often used in
mission-critical applications and corporate environments that require
high availability, security, and performance.

How to Monitor Oracle on the One Platform

To set up monitoring for Oracle on the platform, follow these steps:

1. Go to the product application where you want to add Oracle as a dependency in the platform.

2. Click on the “Products” menu and select the desired product card.

3. Then, click on the name of the specific application where you want to configure Oracle monitoring.

4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

5. To add an already registered dependency, type the name of the
   dependency in the search field and select it when it appears in the
   list.

6. If Oracle is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

 

Click “Add” and a modal will
appear allowing you to name the database and select the Environment. In
the “Check type” field, choose the option “DB,” and in the “Method”
field, select “Oracle.” After selecting the method, a field for the
Healthcheck URL will appear.

 

Below is an example of string for Oracle:

ex: USER/PASSWORD@HOST:PORT/DATABASE/ as SYSDBA

 

Note: For security reasons, it is not permitted to enter an IP in the
healthcheck field. To monitor an IP, you need to enter it in a secret
and use it in healthcheck

Neo4j is a highly scalable and flexible graph-oriented database, specifically designed to store, query and manipulate complex relational data. It uses a graph data structure, consisting of nodes, relationships, and properties, to represent and store relationships between data. This approach allows Neo4j to be highly efficient at finding and analyzing connections between data, making it ideal for use cases involving social networks, recommendations, complex data analysis, and pattern discovery. With its Cypher query language, Neo4j offers an expressive and intuitive syntax for performing powerful graph queries. Furthermore, its scalable and distributed architecture allows it to handle large volumes of data and support demanding workloads. Neo4j is widely used in various industries, including finance, computer science, bioinformatics and logistics, where the representation and analysis of complex relationships is essential.

How to monitor Neo4j on One Platform

1 – In the side menu, click on Services Hub

2 – In the Database category, click on the Neo4j card

3 – You will be directed to the Neo4j configuration page, fill in the fields

4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

• Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
• Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
• Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
• Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
• Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
• Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings

5 – Click on CREATE MONITORING 

Neo4j is a highly scalable and flexible graph database, specifically designed to store, query, and manipulate complex relational data. It uses a graph data structure, consisting of nodes, relationships, and properties, to represent and store the connections between data. This approach allows Neo4j to be highly efficient in searching and analyzing data connections, making it ideal for use cases involving social networks, recommendations, complex data analysis, and pattern discovery. With its Cypher query language, Neo4j offers an expressive and intuitive syntax for performing powerful graph queries.  Additionally, its scalable and distributed architecture allows it to handle large volumes of data and support demanding workloads. Neo4j is widely used in various industries, including finance, computer science, bioinformatics, and logistics, where the representation and analysis of complex relationships are essential.

How to Monitor Neo4j on the One Platform

To set up monitoring for Neo4j on the platform, follow these steps:

1. Go to the product application where you want to add Neo4j as a dependency in the platform.

2. Click on the “Products” menu and select the desired product card.

3. Then, click on the name of the specific application where you want to configure Neo4j monitoring.

4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

5. To add an already registered dependency, type the name of the
   dependency in the search field and select it when it appears in the
   list.

6. If Neo4j is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

 

Click “Add” and a modal will
appear allowing you to name the database and select the Environment. In
the “Check type” field, choose the option “DB,” and in the “Method”
field, select “Neo4j.” After selecting the method, a field for the
Healthcheck URL will appear.

 

 

Below is an example of string for Neo4j:

ex: bolt://HOST:PORT@USER/PASSWORD

Note: For security reasons, it is not permitted to enter an IP in the healthcheck field. To monitor an IP, you need to enter it in a secret and use it in healthcheck

MySQL is a related database management system widely used across the world. It is known for its simplicity, performance and reliability. MySQL offers a range of features, including full SQL support, the ability to handle large volumes of data, scalability, and ACID (Atomicity, Consistency, Isolation, and Durability) transaction support. It is often used in web applications, content management systems, e-commerce systems, and many other data storage scenarios. MySQL is an open source solution, but it is also offered as a managed service by cloud providers, making it easier to deploy and manage MySQL databases across different environments.

How to monitor MySQL on One Platform

1 – In the side menu, click on Services Hub

2 – In the Database category, click on the MySQL card

3 – You will be directed to the MySQL configuration page, fill in the fields

4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

• Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
• Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
• Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
• Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
• Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
• Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form to create the team, then click on the button for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings

5 – Click on CREATE MONITORING 

MySQL is a widely used relational database management system worldwide. It is known for its simplicity, performance, and reliability. MySQL offers a range of features, including full SQL support, the ability to handle large volumes of data, scalability, and support for ACID transactions (Atomicity, Consistency, Isolation, and Durability). It is commonly used in web applications, content management systems, e-commerce systems, and many other data storage scenarios. MySQL is an open-source solution but is also offered as a managed service by cloud providers, making it easier to deploy and manage MySQL databases in different environments.

How to Monitor a MySQL DB on the One Platform

To set up monitoring for MySQL on the platform, follow these steps:

1. Go to the product application where you want to add MySQL as a dependency in the platform.

2. Click on the “Products” menu and select the desired product card.

3. Then, click on the name of the specific application where you want to configure MySQL monitoring.

4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

5. To add an already registered dependency, type the name of the dependency in the search field and select it when it appears in the list.

6. If MySQL is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

Click “Add” and a modal will appear allowing you to name the database and select the Environment. In the “Check type” field, choose the option “DB,” and in the “Method” field, select “MySQL.” After selecting the method, a field for the Healthcheck URL will appear.

Below is an example of string for Postgres:

e.g., USER:PASSWORD@tcp(HOST:PORT)/DATABASE

Note: For security reasons, it is not permitted to enter an IP in the healthcheck field. To monitor an IP, you need to enter it in a secret and use it in healthcheck

1 – In the side menu, click on Services Hub

2 – In the Monitoring category, click on the Monitoring via API card

3 – You will be directed to the Monitor configuration form via API, fill in the fields

4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

• Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
• Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
• Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
• Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
• Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
• Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form

to create the team, then click on the button for the new team to appear in the list

***Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings

5 – Click on CREATE MONITORING 

6 – On the resources screen, click the button and select the option API Hits and Failures

7 – If you have not created the token for Hits/Failures, click here and follow steps “8”, “9” and “10”, if you have already, skip to step “11”

8 – Select the API tab

9 – Click on the button To add a new token, choose the Hits/Failures type and fill in the desired name. Click on Generate Integration Token.

10 – a curl will appear, and with it you will be able to generate a token valid for 300 seconds

11 – Copy the hit and failure Curl’s (remember to replace “<token>” with the token generated in step “10” to curl)

12 – It must generate hits/failure with an interval less than or equal to the interval configured in step “3”, so the monitoring will have the status “operational” (if it receives a hit) or “not operational” (if it receives failure). If the platform does not receive any hits/failures within this interval, the monitoring will have the status “pending”

 

Note: Our application has a rate limit of 5 requests per second. This means that each IP can make a maximum of 5 requests to the server in a period of 1 second. If this limit is exceeded, additional requests will be temporarily blocked.

At OnePlatform we have 2 levels of aggregators to facilitate the organization and management of different monitoring, Product and Application.

In the Product we can include one or several Applications, which in turn, we can include a Main Resource and multiple Dependences

 

Configuring a product on OnePlatform

1 – Select Product, located in the side menu

2 – The Product screen will open where we can manage the products already created

3 – To create a new product, click on the + NEW PRODUCT button and fill in the Name and, if desired, a description, then click on CREATE PRODUCT

4 – Opening the product, we have the resilience matrix, with status information about the applications linked to this product and their dependencies (to add an application to a product, see the steps below)

5 – To edit or delete a product, click the button on the right

Configuring an application on One Platform

1 – Select Application, located in the side menu

2 – The Applications screen will open where we can manage applications already created

3 – To create a new application, click on + NEW APPLICATION, fill in the fields:

• Display Name -> Choose the application name
• Choose Product -> Choose a product to include this application (optional)
• Choose Monitoring Main -> Choose which monitoring (Resource) will be the main of this application
• Choose Dependences -> Choose one or more resources to be added to the application as a dependency (optional)

Click on CREATE APPLICATION

4 – Opening the application, we have a panel with information about the Main Resource and Dependences (if added)

5 – To edit or delete an application, click the button on the right

MongoDB is a popular NoSQL database designed to store data in flexible document format similar to JSON. It offers high scalability and performance, allowing you to distribute data across multiple servers and run complex queries. Its replica set architecture ensures high availability and data durability. With support for indexing and advanced queries, MongoDB is commonly used for applications that require schema flexibility and management of unstructured or semi-structured data.

How to monitor MongoDB on One Platform

1 – In the side menu, click on Services Hub

2 – In the Database category, click on the MongoDB card

3 – You will be directed to the MongoDB configuration page, fill in the fields

4 – If you want, you can configure automatic incident opening. In the Open automatic incident section, fill in the fields:

• Severity -> Choose between “SEV-1 – Critical”, “SEV-2 – High”, “SEV-3 – Moderate”, “SEV-4 – Low”, “SEV-5 – Informational” or “Not Classified”;
• Check Interval in seconds -> This is the interval at which checking will take place (this interval cannot be less than the number of failures x the Interval configured in the monitoring form;
• Failures to open automatic incident -> It is the number of failures necessary to open the automatic incident;
• Check Interval in seconds -> This is the interval in which checking will take place (this interval cannot be less than the number of hits x the Interval configured in the monitoring form;
• Hits to close automatic incident -> It is the number of hits needed to close the automatic incident;
• Responders -> These are the teams that will be notified if there are incidents in this monitoring, and you can add one or multiple teams;

If necessary, you can create a team by clicking + RESPONDER, you will be directed to the form to create

to create the team, then click on the button for the new team to appear in the list

**Don’t forget to activate the Enable to set up automatic incidents opening toggle to save the automatic incident opening settings

5 – Click on CREATE MONITORING 

MongoDB is a popular NoSQL database designed to store data in flexible document formats similar to JSON. It offers high scalability and performance, allowing data to be distributed across multiple servers and executing complex queries. Its replica set  architecture ensures high availability and data durability. With support for indexing and advanced queries, MongoDB is commonly used for applications that require schema flexibility and management of unstructured or semi-structured data.

How to Monitor MongoDB on the One Platform

To set up monitoring for MongoDB on the platform, follow these steps:

1. Go to the product application where you want to add MongoDB as a dependency in the platform.

2. Click on the “Products” menu and select the desired product card.

3. Then, click on the name of the specific application where you want to configure MongoDB monitoring.

4. Look for the section called “External Dependencies,” usually located just below the latency graph of the application.

5. To add an already registered dependency, type the name of the dependency in the search field and select it when it appears in the list.

6. If MongoDB is not yet registered as a dependency, click on the green button with a plus (+) symbol to add a new dependency.

Click “Add” and a modal will
appear allowing you to name the database and select the Environment. In the “Check type” field, choose the option “DB,” and in the “Method” field, select “MongoDB.” After selecting the method, a field for the Healthcheck URL will appear.

Below is an example of string for MongoDB:

ex: mongodb://HOST:PORT

Note: For security reasons, it is not permitted to enter an IP in the healthcheck field. To monitor an IP, you need to enter it in a secret and use it in healthcheck.