The Resource Monitoring Center is designed to facilitate the efficient visualization and management of different resource states. This guide provides an overview of the available filtering functionalities to optimize monitoring.

In resource monitoring, filters are used to efficiently visualize and manage different states of resources. Below are the available filter categories:

  • All: Displays all resources regardless of their status.
  • Inactive: Shows only inactive resources.
  • Operational: Filters and displays only operational resources.
  • Pending: Lists resources that are pending, awaiting some action or decision.
  • In Maintenance: Displays resources that are currently undergoing maintenance.
  • Not Operational: Shows resources that are not operational.

Each filter allows you to focus on specific resources, facilitating management and tracking as needed. 
In addition to filtering resources by status, you can also view them based on different time intervals. The available period options are:

  • All: Shows resources from all periods.
  • Last Day: Displays resources that have had activities in the last 24 hours.
  • Last Week: Filters resources with activities in the last week.
  • Last Month: Lists resources that were active in the last month.
  • Last Year: Shows resources that have had activities in the last year.

These time filters help analyze trends and changes in resource usage over different periods, facilitating decision-making and strategic planning. 

The Custom Range option offers maximum flexibility by allowing you to set a specific date and time interval for resource monitoring. Here’s how to use it:

  • Start Date: Select the start date and time of the interval.
  • End Date: Choose the end date and time of the interval.

After setting the desired parameters:

  • Click on Apply Time Range to apply the filter.
  • If you wish to cancel the selections made, click on Cancel.

This functionality is ideal for precise and detailed analysis, allowing you to track activities in specific periods tailored to your needs. 

Teste grátis por 14 dias

Observation:

All of the following steps must be done after External
Integration has already been configured by the ElvenWorks team. Request
integration via chat on the platform or on the website.

 

1. First click on integrations in the left side menu

 

2. In the search bar, search for “webhooks”, click on the card that appears

 

3. Click “New” to add a new webhook

 

4. Fill in the fields as shown in the image below and click “Save”

 

5. To add the webhook to a monitoring, click on “Monitors” in the left side menu and choose the monitoring you want or create a new one.

 

6. On the monitoring edit screen, add the webhook created in the “Notify your team” field

 

7. Test the integration by clicking “Test Notifications” at the end of the editing screen

 

8. Choose the type of notification and click “Run Test”

 

9. An incident must be created on One Platform notifying the chosen team at the time of the integration request

 

Done! Your 1P+Datadog integration is configured.

Teste grátis por 14 dias

Observation:

All of the following steps must be done after External
Integration has already been configured by the ElvenWorks team. Request
integration via chat on the platform or on the website.

 

1 – In AWS we must create a lambda, in the services menu by lambda, then Create Function:

 

 

When creating the lambda, we must inform the name and Runtime. By default, Node.js 16x is used.

 

 

After filling in the fields above, click on CREATE FUNCTION.

2- After accessing the created lambda, in code source replace the default with the one provided by the Elvenworks team.

Default: 


 

Click deploy, after entering the provided code.

3- Access the SNS service:

 

After accessing the service, access topics and then create topic:

Select the Standard option, with a name of your choice.

 

 

After that click on Create topic

4 – When creating the topic, the next step is to associate the created lambda. To do this, scroll the mouse cursor to the end of the page and click on Create Subscription.

 

Select the topic created, in protocol choose AWS Lambda and in the endpoint select the one created for the integration. After that click on Create subscription.

5 – After creating the SNS topic, we must configure it in Cloudwatch.

 

When accessing the cloudwatch service, the next step is to create the alert by clicking on “Create alarm“.

Select the metric you want to monitor, in the example below we are monitoring the CPU Utilization metric:

Define the conditions according to your operation

Click next for the next step.

 

6- Configure actions, we must configure the notification for the three statuses:

  • In Alarm
  • OK
  • Insufficient data

Everyone must send it to the topic created on SNS, as per the example:

Click next for the next step and name the created alert

Check if the alert and conditions were created correctly and click Create alarm to finish. After that, all Cloudwatch alerts should appear on One Platform.

Teste grátis por 14 dias

1 – In the side menu, click on Services Hub


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


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



Teste grátis por 14 dias

1 – In the side menu, click on Services Hub


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


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



Teste grátis por 14 dias

gRPC is a modern and high-performance framework that represents an evolution of the traditional Remote Procedure Call (RPC) protocol. At the application level, gRPC simplifies the messaging system between clients and backend services.

How to monitor gRPC on One Platform

1 – In the side menu, click on Services Hub

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

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

Teste grátis por 14 dias

gRPC is a modern and high-performance framework that represents an
evolution of the traditional Remote Procedure Call (RPC) protocol. At
the application level, gRPC simplifies the messaging system between
clients and backend services.

To monitor gRPC in the One Platform:

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

 

 

Check below the example strings for gRPC:

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

Teste grátis por 14 dias

The Latency and Deployments Graph is one of the features available on
the platform, along with other metric applications, for performance
monitoring and the impact of deployments. This graph displays the
response time between the platform’s agent and the application through a
route determined by the health check URL. Additionally, it showcases
the performance of deployments on the timeline, allowing for monitoring
the application’s impact after a change.

By default, the graph shows data from the last 24 hours. In the top
right corner, you can find tools to modify data collection, such as
adjusting the verification interval and the option to remove any
fluctuations necessary for more specific analysis.


 

Other functionalities of the graph:

Selection Zoom: With this feature enabled, you can
select a portion of the graph and isolate a specific interval. The plus
(+) and minus (-) buttons are complementary and provide overall zoom for
the graph.

Panning: By using the hand-shaped feature, you can
have a panoramic view of the graph, panning horizontally to view past or
future time intervals.

Reset Zoom: Symbolized as a house, this feature is
used to adjust the graph’s zoom to the default last 24 hours view.
Clicking it will automatically reset the zoom.

More: Represented with three lines, this action
gives you the option to export the data present in the graph in three
formats: SVG, PNG, and CSV.

Deployments Graph:

When your development team releases a change to a service, it’s
crucial to monitor that application constantly to understand if there is
an improvement or deterioration in its performance.

By inserting a deployment in your product’s application on the
platform, the graph records the day and time when the change was made,
allowing you to identify if there was any impact on the response time
after the release.

The deployment records are also saved in the applications’ timeline, along with incident notifications.

Teste grátis por 14 dias

The Google Cloud Platform (GCP) Pub/Sub service is a highly scalable and reliable real-time messaging and publish-subscribe system. It allows distributed applications to exchange data and events asynchronously, where producers publish messages to topics and consumers subscribe to these topics to receive corresponding messages. GCP Pub/Sub ensures reliable message delivery, even in cases of high load or transient failures. Additionally, it offers advanced features such as rate control, message filtering, and integration with other GCP services such as Cloud Functions, Dataflow, and BigQuery. With its distributed and scalable architecture, GCP’s Pub/Sub service is suitable for scenarios that require real-time message exchange, large-scale data ingestion, event streaming, and distributed systems integration.

How to monitor PubSub on One Platform

1 – In the side menu, click on Services Hub



2 – In the Queue category, click on the  PubSub (GCP) card



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


Teste grátis por 14 dias

Cloud Functions is a serverless computing service provided by Google Cloud Platform (GCP). It allows you to run your code in response to specific events without needing to manage servers or underlying infrastructure. With Cloud Functions, you can write functions in multiple programming languages, such as Node.js, Python, Go, and more. These functions can be triggered by GCP service events, such as changes to Cloud Storage buckets, messages received in Pub/Sub, or HTTP triggers. The service automatically scales the execution of its functions, ensuring that they respond quickly and reliably, even in times of high traffic. Cloud Functions also offers integration with other GCP services, allowing you to build scalable, responsive cloud applications, implement custom business logic, and automate tasks, all simply and efficiently.

How to monitor GCP Function on One Platform

1 – In the side menu, click on Services Hub



2 – In the Serverless category, click on the Function GCP card



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


Teste grátis por 14 dias
Scroll to Top