# Grafana Cloud Metrics

Published articles for Grafana Cloud Metrics.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## How to monitor Cypress tests with Grafana Cloud

DevFeed: [How to monitor Cypress tests with Grafana Cloud](<https://devfeed.tech/articles/how-to-monitor-cypress-tests-with-grafana-cloud-8589.md>)

Original publisher: [Read original article](<https://grafana.com/blog/how-to-monitor-cypress-tests-with-grafana-cloud/>)

Author: Rajesh Mahalingaswamy

Published: 2026-09-12T11:22:06.456390Z

Content type: tutorial

Language: en

Sources: [Grafana Labs blog on Grafana Labs](<https://devfeed.tech/sources/grafana-labs-blog-on-grafana-labs.md>)

Topics: [Grafana](<https://devfeed.tech/topics/grafana.md>), [Node.js](<https://devfeed.tech/topics/node-js.md>), [ci](<https://devfeed.tech/topics/ci.md>)

Tags: [analytics](<https://devfeed.tech/tags/analytics.md>), [cypress](<https://devfeed.tech/tags/cypress.md>), [grafana](<https://devfeed.tech/tags/grafana.md>), [grafana-alloy](<https://devfeed.tech/tags/grafana-alloy.md>), [grafana-cloud](<https://devfeed.tech/tags/grafana-cloud.md>), [grafana-cloud-metrics](<https://devfeed.tech/tags/grafana-cloud-metrics.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [logs](<https://devfeed.tech/tags/logs.md>), [metrics](<https://devfeed.tech/tags/metrics.md>), [monitoring](<https://devfeed.tech/tags/monitoring.md>), [node-js](<https://devfeed.tech/tags/node-js.md>), [observability](<https://devfeed.tech/tags/observability.md>), [prometheus](<https://devfeed.tech/tags/prometheus.md>), [traces](<https://devfeed.tech/tags/traces.md>)

### AI overview

A tutorial for monitoring Cypress test results by converting them to Prometheus metrics, pushing them through a Pushgateway, scraping them with Alloy, and forwarding them to Grafana Cloud Metrics.

### Source excerpt

If your Cypress suite has tests that fail more often or run slower, you know it can be hard to figure out the pattern from a single job. It could be one spec that slowed down, or a single test that fails, or maybe the entire suite is trending slower. The root cause could be a bug in the app, or a flaky test, or something else. Your terminal output and CI log will tell you what happened on a single run, but that doesn't help you spot any larger trends--especially since you lose that data as soon as the job finishes. Thankfully, Cypress, a front-end automated test framework built for web applications, already exposes everything you need through its plugin hooks. After each spec finishes, Cypress hands you a results object with pass and fail counts, per-test durations, and states. You just need to turn that into metrics and ship it somewhere durable. In this post, you'll learn how to monitor your Cypress tests by converting those results into Prometheus metrics inside a Cypress hook, pushing them to a Prometheus Pushgateway, and letting Alloy scrape the gateway and forward everything to Grafana Cloud Metrics--using nothing but the free tiers. By the end you'll have a pipeline running with the following architecture: What you'll need This walkthrough runs everything alongside your existing Cypress project. Before you start, make sure you have: A Cypress project (this example uses Cypress 14.x) with a cypress.config.js you can edit A Prometheus Pushgateway. Cypress runs are short-lived batch jobs, so they can't be scraped directly--the Pushgateway holds the metrics between runs so a scraper can pick them up. Set up a Prometheus Pushgateway in your infrastructure Alloy, our open source collector we use to scrape the Pushgateway and remote-write to Grafana Cloud A Grafana Cloud account. The free tier includes Grafana Cloud Metrics and a Prometheus remote-write endpoint. If you don't have an account, you can sign up here Your Grafana Cloud remote-write URL, numeric user ID, an