API Monitoring

You can monitor usage of the Earth Engine API by Cloud Project from the Cloud Console. Specifically, the metrics page shows basic metrics including traffic (number of requests), errors and latency (per API method, response code or credentials). The quotas page shows the amount of stored assets in bytes and the number of read requests for the assets. The credentials page shows which credentials (for example service accounts) have been used to access the API.

Consumption Monitoring (Beta)

In addition to the standard API metrics described above, Earth Engine consumption metrics (Beta) are available to track your project's use of Earth Engine resources.

Find the metrics in the Cloud Console by going to Monitoring > Metrics Explorer from the left side navigation menu. Click equalizer SELECT A METRIC and choose one of the Earth Engine metrics to add it to the chart. Note that you may need to adjust the time range and aggregation method to observe data for your project.

Earth Engine metrics are split into compute usage metrics (as EECU-seconds) and storage metrics. You can get more insights on your compute usage by further breaking down into types as described in the following table.

Workload Tags

Workload tags are labels for monitoring specific computations within Earth Engine. Use setDefaultWorkloadTag to bind all computations in the script to a default workload tag unless one is explicitly set with ee.data.setWorkloadTag, in which case the default is overidden. These methods set the workload_tag label to specific computations and export tasks. You can then monitor and track individual computations in the Cloud Console. Workload tags can be viewed in the Cloud Console by going to Monitoring > Metrics Explorer, for Resource & Metric select EARTH ENGINE CLOUD PROJECT - USED EECUS, then group by workload_tag. Learn more about creating and managing labels in Cloud Monitoring on this page.

For example, to monitor the EECUs used for an image computation and/or and export:

// Cloud masking function.
function maskL8sr(image) {
  var qaMask = image.select('QA_PIXEL').bitwiseAnd(parseInt('11111', 2)).eq(0);
  var saturationMask = image.select('QA_RADSAT').eq(0);

  // Apply the scaling factors to the appropriate bands.
  var opticalBands = image.select('SR_B.').multiply(0.0000275).add(-0.2);
  var thermalBands = image.select('ST_B.*').multiply(0.00341802).add(149.0);

  // Replace the original bands with the scaled ones and apply the masks.
  return image.addBands(opticalBands, null, true)
      .addBands(thermalBands, null, true)
      .updateMask(qaMask)
      .updateMask(saturationMask);
}

// Set a default workload tag.
ee.data.setDefaultWorkloadTag('landsat-compositing')
var collection = ee.ImageCollection('LANDSAT/LC08/C02/T1_L2')
                     .filterDate('2020-01-01', '2021-01-01')
                     .map(maskL8sr);
var composite = collection.select('SR_B.').median();
print(composite);

// Set a new workload tag.
ee.data.setWorkloadTag('export-jobs');
Export.image.toAsset(composite);
ee.data.resetWorkloadTag(); // Reset to landsat-compositing

ee.data.resetWorkloadTag(true); // Reset back to empty

import ee

# Authenticate, then initialize with your Cloud Project.
ee.Initialize(project='your-project')

# Set a default workload tag.
ee.data.setDefaultWorkloadTag('landsat-compositing')
composite = ee.ImageCollection('LANDSAT/LC08/C02/T1_L2').filterDate(
    '2020-01-01', '2021-01-01').median()

# Set a workload tag for export.
ee.data.setWorkloadTag('export-jobs')
ee.batch.Export.image.toAsset(composite).start()
ee.data.resetWorkloadTag()

# Alternatively, use a workload tag with with.
with ee.data.workloadTagContext('export-jobs'):
  ee.batch.Export.image.toAsset(composite).start()

In this example, all computations are annotated via the landsat-compositing tag (set as default), and the export gets its own workload tag since ee.data.setWorkloadTag is called before running it. Use ee.data.resetWorkloadTag to set back to the default tag or to set the default tag back to an empty string.

Learn more about monitoring using the Cloud Console from these guides.