Check out the three functions available to users on a team:

Member Permissions:

• Organization-wide read-only.
• Example: A member can view data, but cannot create, edit, or delete any content.

Admin Permissions Without Team Membership:

• Permissions to create, edit, or delete, except associated products and items.
• Example: An admin can modify organization settings and manage users, but cannot change product details without being associated with a corresponding team.

Admin Permissions With Team Membership (Member):

• If you are an admin in the organization and a member of a team, you have limited permissions regarding products.
• Example: An admin is also a member of a team that is associated with a product. He cannot change product information unless he is an admin or owner on that specific team.

Admin Permissions With Team Membership (Admin or Owner):

• If admin in the organization and admin or owner in a team associated with the product, you have full permissions for mutations in the product and related items.
• Example: An admin is also an owner of a team that manages a product. It can make any mutations like releasing an update or discontinuing the product.

Owner Permissions on Team Associated with the Product:

• Complete freedom to carry out reading and mutation actions in all aspects of the organization.
• Example: The org owner has complete permission over the entire org without needing to be a member of the team.

If the user is added or removed from a team, or their Role is changed both in the team and in the org, these changes only take effect after they log in to OnePlatform again.

Below is a diagram representing the actions described above:

On the resource screen is where we find many

1 – Monitoring status -> Here we have the current status of the resource, the existing statuses are Operational, Not Operational and Pending

2 – On/off switch -> Key to turn resource monitoring on and off

3 – Healthcheck URL -> It is the endpoint that is being monitored, in some types of resources it is the connection string

4 – Checkpoint -> It is the agent that is being used to monitor the resource

5 – Last Check -> This is the time of the last check carried out by the agent

6 – View Metrics -> Opens a dashboard with the resource’s metrics

7 – Maintenance window -> Configures a window in which the resource will undergo maintenance, find out more

8 – Opening hours -> Configure the time when the monitoring will be on, find out more

9 – Edit/Delete -> Here we can edit the resource settings or delete

10 – MTBF (Main Time Between Failures) -> This metric shows the average time between resource failures

11 – MTTA (Main Time To Acknowledge) -> This metric shows the average time for each acknowledgment

12 – MTTRecovery (Main Time To Recovery) -> This metric shows the average time for resource recovery

13 – Uptime -> Shows the health of the resource in several pre-defined periods

14 – Error Budget -> Here you can view and inform the percentage of the Error Budget, used according to your needs

TCP (Transmission Control Protocol) is fundamental to the internet network. This protocol ensures that information packets reach their destination correctly and securely. By doing so, we can manage and define data between devices before they reach their destinations.

How to monitor TCP on One Platform

1 – In the side menu, click on Services Hub

2 – In the Monitoring category, click on the  TCP card

3 – You will be directed to the via TCP configuration form, 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 

TCP (Transmission Control Protocol) is fundamental to the internet
network. This protocol ensures that information packets reach their
destination correctly and securely. By doing so, we can manage and
define data between devices before they reach their destinations.

To monitor TCP in the One Platform:

1. Go to the product application where you want to add TCP as a dependency.

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

3. Next, click on the name of the specific application you want to work with.

4. Under “External Dependencies,” located just below the latency graph, you can add or search for an already registered dependency.

5. To search for a dependency, enter its name in the search field.

6. To add a new dependency, click on the green button with a plus (+) symbol.

From there, you can configure the settings and details for monitoring
TCP, including specifying the IP address or hostname, and other
relevant parameters.

When you click “Add,” a modal will
appear. In this modal, you will name your dependency and choose the
Environment. In the “Check type” field, select the option “Others,” and
in the “Method” field, choose “TCP.” After selecting the method, a field
for the Healthcheck URL will appear.

 

Check below the example strings for TCP:

example: 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

SQS (Simple Queue Service) is a
fully managed message queue service provided by Amazon Web Services
(AWS). It allows developers to send, store, and receive messages
asynchronously between components of distributed applications. SQS is
highly scalable and fault-tolerant, ensuring that messages are processed
reliably and in order. Producers send messages to queues, and consumers
retrieve them for processing. SQS offers two types of queues: Standard
Queue and FIFO Queue, which differ in their message delivery and
ordering capabilities. The SQS service is flexible and can be easily
integrated with other AWS services, such as EC2, Lambda, and SNS. It is
particularly used in distributed scenarios, microservices, batch
processing, email notifications, and other use cases where reliable and
asynchronous communication between components is required. With its
fully managed nature, developers can focus on business logic without
worrying about the underlying message queue infrastructure.

How to Monitor SQS on the One Platform:

To set up monitoring for SQS on the One Platform, follow these steps:

1. Go to the product application where you want to add SQS as a dependency.
2. Click on the “Products” menu, select the desired product card, and
   then click on the name of the application you want to configure.
3. Scroll down to “External Dependencies,” located just below the latency graph.
4. Here, you can either add a new SQS dependency or search for an existing one.
5. To add a new dependency, click on the green button with a plus (+) symbol. A modal will appear.
6. In the modal, provide a name for your SQS queue and choose the Environment.
7. In the “Check type” field, select the option “Queue,” and in the “Method” field, choose “SQS.”
8. After selecting the method, a field for “Healthcheck URL” will appear.

 

When you click on “Add,” a modal will appear. In this modal, you will
name your queue and choose the Environment. In the “Check type” field,
select the option “Queue,” and in the “Method” field, choose “SQS(AWS).”
After selecting the method, a field for “Healthcheck URL” will appear.

 

In the “Queue size” field, enter the desired maximum queue size.

Here is an example of a string for SQS:

ex: ACCESS_KEY:SECRET_ACCESS_KEY/AWS-REGION@TEST-QUEUE

 

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

SQL Server is a relational database management system developed by Microsoft. It is commonly used in business environments and offers a wide range of features for storing, querying and manipulating data. SQL Server supports the SQL language and is known for its scalability, reliability, and performance. It provides advanced features such as ACID (Atomicity, Consistency, Isolation, and Durability) transaction support, integration with Microsoft’s .NET development platform, business intelligence (BI) support, data replication, disaster recovery, and enhanced security. Additionally, SQL Server offers multiple editions to meet the specific needs of different organizations, from small businesses to large corporations. SQL Server can also be deployed on-premises or as a managed cloud service, providing flexibility in choosing hosting infrastructure.

How to monitor SQL Server on One Platform

1 – In the side menu, click on Services Hub

2 – In the Database category, click on the SQL Server card

3 – You will be directed to the SQL Server 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 

SQL Server is a relational database management system developed by
Microsoft. It is commonly used in enterprise environments and offers a
wide range of features for data storage, querying, and manipulation. SQL
Server supports the SQL language and is known for its scalability,
reliability, and performance. It provides advanced features such as
support for ACID transactions (Atomicity, Consistency, Isolation, and
Durability), integration with Microsoft’s .NET development platform,
business intelligence (BI) support, data replication, disaster recovery,
and enhanced security.

Furthermore, SQL Server offers various editions to cater to the
specific needs of different organizations, from small businesses to
large corporations. It can be deployed either on-premises or as a
managed service in the cloud, providing flexibility in choosing the
hosting infrastructure.

How to Monitor A SQL Server on the One Platform

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

1. Go to the product application where you want to add SQL Server 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 SQL Server 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 SQL Server 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 “SQL Server.” After selecting the method, a field for the
Healthcheck URL will appear.

 

Below is an example of string for SQL Server:

ex: sqlserver://USER:PASSWORD@HOST?database=DB

 

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

Apache Solr is an open-source
enterprise search platform built on Apache Lucene. It provides advanced
search, indexing, and data analysis capabilities, allowing organizations
to find relevant information quickly and efficiently. Solr supports a
wide range of features, including full-text search, geospatial search,
faceting, search suggestions, filtering, result highlighting, and more.
It can handle large volumes of data, offering horizontal scalability to
meet growing storage and processing needs. With a RESTful API and
various integration capabilities, Solr is user-friendly and can be
easily integrated into existing applications and systems. It is widely
used in various industries such as e-commerce, media, government, and
healthcare to provide fast and accurate search over large volumes of
data. Solr is a popular choice for organizations looking to deploy a
powerful, flexible, and highly customizable search solution.

To monitor Solr in the One Platform:

1. Go to the product application where you want to add Solr as a dependency.

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

3. Next, click on the name of the specific application you want to work with.

4. Under “External Dependencies,” located just below the latency graph, you can add or search for an already registered dependency.

5. To search for a dependency, enter its name in the search field.

6. To add a new dependency, click on the green button with a plus (+) symbol.

 

When you click “Add,” a modal will
appear. In this modal, you will name your dependency and choose the
Environment. In the “Check type” field, select the option “Search
Engine,” and in the “Method” field, choose “Solr.” After selecting the
method, a field for the Healthcheck URL will appear.

Check below the example strings for Solr:

example: http://HOST:PORT/solr/gettingstarted/admin/ping

 

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

Sidekiq is a popular library for background job processing in Ruby on Rails applications. It uses Redis as a backend to store and manage the job queue, providing efficient and scalable processing. Sidekiq allows developers to define asynchronous tasks that will be executed in the background, freeing the main thread to handle other requests. It supports advanced features such as job scheduling, prioritized queuing, and failure retention, ensuring reliability and error recovery. With its simple and easy-to-use interface, Sidekiq has become a popular choice for handling time-consuming tasks or tasks that do not require an immediate response, thereby improving the user experience.

 

How to monitor Sidekiq on One Platform

 

1 – In the side menu, click on Services Hub

2 – In the Queue category, click on the  Sidekiq card

3 – You will be directed to the Sidekiq configuration form, 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 

Sidekiq is a popular library for background job processing in Ruby on
Rails applications. It uses Redis as a backend to store and manage the
job queue, providing efficient and scalable processing. Sidekiq allows
developers to define asynchronous tasks that will be executed in the
background, freeing the main thread to handle other requests. It
supports advanced features such as job scheduling, prioritized queuing,
and failure retention, ensuring reliability and error recovery. With its
simple and easy-to-use interface, Sidekiq has become a popular choice
for handling time-consuming tasks or tasks that do not require an
immediate response, thereby improving the user experience.

To monitor Sidekiq in the One Platform:

1. Go to the product application where you want to add Sidekiq as a dependency.
2. Click on the “Products” menu, then click on the desired product
   card, and finally, click on the name of the application you want.
3. Under “External Dependencies,” located just below the latency graph,
   you can add or search for an already registered dependency. To search
   for a dependency, type its name in the search field. To add a new one,
   click on the green button with a plus symbol (+).

When you click on “Add,” a modal will appear. In this modal, you will
name your queue and choose the Environment. In the “Check type” field,
select the option “Queue,” and in the “Method” field, choose “Sidekiq.”
After selecting the method, a field for “Healthcheck URL” will appear.

 

 

In the Queue size field, enter the maximum desired queue size. Select
“Skip SSL Validation” to ignore the existence of the SSL certificate.
In the Busy Size, Scheduled Size, and Connected Clients fields, fill in
according to the desired number to trigger alerts for incidents.

Check the example string for Sidekiq below:

Example: http://example.com/sidekiq/stats

 

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