New Relic integrations with the Google Cloud Platform (GCP) include one that reports Google Firebase Realtime Database data to New Relic. This document explains how to activate the GCP Firebase Database integration and describes the data it reports.
Features
Firebase Realtime Database is Google Cloud's NoSQL cloud database that lets you store and sync data between users in realtime. New Relic Firebase Database integration collects I/O, network, storage, connection, and security-rule metrics for each database namespace.
Activate integration
To enable the integration, follow standard procedures to connect your GCP service to New Relic:
Polling frequency
New Relic integrations query your GCP services according to a polling interval that varies by integration. The polling frequency for Google Cloud Firebase Database is 5 minutes. The resolution is 1 data point every minute.
Workload Identity Federation
Find and use data
After you enable the integration, your Firebase Database resources appear as entities in the New Relic entity explorer. To see dashboards and manage services, go to one.newrelic.com > All capabilities > Infrastructure > GCP.
All Firebase Database metrics available in GCP Cloud Monitoring are collected as dimensional metrics in the Metric event type. Additional metrics beyond this table are collected automatically. See Google's Firebase Database metrics documentation for the complete list.
Entities
Metric data
Key metrics — Namespace
Metric name | Unit | Description |
|---|---|---|
| Percent | Fraction of I/O capacity in use by the database namespace. |
| Percent | Fraction of database load on the namespace, faceted by load type. |
| Bytes | Bytes of data persisted to disk by the database namespace. |
| Count | Number of responses sent or broadcast to clients from the database namespace. |
| Count | Number of outstanding connections to the database namespace. |
| Count | Number of API hits against the database namespace, faceted by type. |
| Count | Number of HTTPS requests received by the database namespace. |
| Percent | Fraction of time spent preparing and sending broadcasts to clients. |
| Bytes | Outgoing bandwidth used by the database namespace, including encryption and protocol overhead. |
| Bytes | Outgoing bandwidth excluding encryption overhead. |
| Bytes | Outgoing bandwidth excluding encryption and protocol overhead. |
| Bytes | Total outgoing bytes sent, aggregated and reset monthly. |
| Bytes | Monthly network limit for the database namespace. |
| Count | Number of Firebase Realtime Database Security Rule evaluations performed in response to write and read requests. |
| Bytes | Storage in use by the database namespace. |
| Bytes | Storage limit for the database namespace. |
For the complete list of Firebase Database metrics, see Google's Firebase Database metrics documentation.
Service account or user account
Find and use data
After activating the integration and waiting a few minutes (based on the polling frequency), data will appear in the New Relic UI. To find and use your data, including links to your and alert settings, go to one.newrelic.com > All capabilities > Infrastructure > GCP > (select an integration).
Data is attached to the following event type:
Entity | Event Type | Provider |
|---|---|---|
Namespace |
|
|
For more on how to use your data, see Understand and use integration data.
Firebase Database Namespace data
Metric | Unit | Description |
|---|---|---|
| Count | Fraction of database load, grouped by type. |
| Bytes | Bytes of data persisted to disk. |
| Count | Number of responses sent or broadcasted to clients. |
| Count | Fraction of I/O used. |
| Count | The number of outstanding connections |
| Count | The number of hits aginst your database grouped by type. |
| Count | Utilization of the time it takes to prep and send broadcasts to clients. |
| Count | Number of HTTPS requests received. |
| Bytes | The total outgoing bytes sent aggregated and reset monthly. |
| Bytes | The monthly network limit for the Firebase database. |
| Bytes | The outgoing bandwidth used by the database, including encryption and protocol overhead. |
| Bytes | The outgoing bandwidth usage without encryption overhead. |
| Bytes | The outgoing bandwidth usage without encryption nor protocol. |
| Count | The number of Firebase Realtime Database Security Rule evaluations performed in response to write and read requests. |
| Bytes | The storage limit for the Firebase database. |
| Bytes | The size of the Firebase database storage. |