GCP PubSub Resource

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 


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