--- title: Meet the Firestore Emulator Requests Monitor | daily.dev description: The Firestore Emulator now includes a Requests Monitor accessible from the Emulator UI in the latest Firebase CLI, letting developers see client requests to... canonical: https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5 twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Meet the Firestore Emulator Requests Monitor | daily.dev og:description: The Firestore Emulator now includes a Requests Monitor accessible from the Emulator UI in the latest Firebase CLI, letting developers see client requests to... og:url: https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5 og:image: https://api.daily.dev/og/posts/JyNro5QJ5.png og:image:alt: Meet the Firestore Emulator Requests Monitor og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Meet the Firestore Emulator Requests Monitor **[Firebase](https://daily.dev/sources/firebase-blog)** · 5 min read · 0 upvotes · 0 comments ## Summary The Firestore Emulator now includes a Requests Monitor accessible from the Emulator UI in the latest Firebase CLI, letting developers see client requests to their local Firestore Emulator in real time, including method, path, and Firebase Security Rules evaluation. Each request appears as a row with a checkmark for allowed rules and highlights for denials or errors, and clicking a request opens an evaluation details view showing the local security rules alongside the resource and request.resource fields to help debug why a request was allowed or denied. Only client requests are shown; admin requests and dependent document fetches (like get() or exists() calls) are not included, and rules on the details page are read-only snapshots requiring edits to the firebase.rules file. The feature supports any client platform (Android, iOS, web) and is recommended for use during local development, prototyping, and unit/integration testing before deploying to production. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### How do I see which Firestore Security Rules are allowing or denying my requests during local development? The Firestore Emulator's Requests Monitor, available in the Emulator UI under the Requests tab with the latest Firebase CLI, shows each client request in real time with a checkmark for allowed requests and highlights for denials or errors. Clicking a request opens an evaluation details view showing the current security rules alongside the request's resource and request.resource fields. _Developers debugging Firestore security rules can track emulator tooling updates like this on daily.dev._ ### Does the Firestore Emulator Requests Monitor show admin SDK requests or dependent document fetches from security rules? No, only client requests appear in the Requests Monitor table. Admin SDK requests bypass security rules entirely and are excluded, and when rules depend on other documents via get() or exists(), only the main request is shown, not the dependent fetches, even though those fetches count toward quota and billing in production. _Teams relying on Firestore emulation for testing can keep up with these tooling limitations via daily.dev._ ## Similar posts on daily.dev - [Testing Firestore security rules without touching production](https://daily.dev/posts/testing-firestore-security-rules-without-touching-production-hniqyzuq6) · All Things Open · 1 upvotes · 0 comments --- Tags: [#testing](https://daily.dev/tags/testing), [#firebase](https://daily.dev/tags/firebase), [#firestore](https://daily.dev/tags/firestore) [View this post on daily.dev](https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Meet the Firestore Emulator Requests Monitor","url":"https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5"},"datePublished":"2026-08-23T12:19:32.089Z","dateModified":"2026-08-23T12:28:06.025Z","description":"The Firestore Emulator now includes a Requests Monitor accessible from the Emulator UI in the latest Firebase CLI, letting developers see client requests to...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"testing,firebase,firestore","timeRequired":"PT5M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"Meet the Firestore Emulator Requests Monitor"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/meet-the-firestore-emulator-requests-monitor-jynro5qj5#faq","mainEntity":[{"@type":"Question","name":"How do I see which Firestore Security Rules are allowing or denying my requests during local development?","acceptedAnswer":{"@type":"Answer","text":"The Firestore Emulator's Requests Monitor, available in the Emulator UI under the Requests tab with the latest Firebase CLI, shows each client request in real time with a checkmark for allowed requests and highlights for denials or errors. Clicking a request opens an evaluation details view showing the current security rules alongside the request's resource and request.resource fields. Developers debugging Firestore security rules can track emulator tooling updates like this on daily.dev."}},{"@type":"Question","name":"Does the Firestore Emulator Requests Monitor show admin SDK requests or dependent document fetches from security rules?","acceptedAnswer":{"@type":"Answer","text":"No, only client requests appear in the Requests Monitor table. Admin SDK requests bypass security rules entirely and are excluded, and when rules depend on other documents via get() or exists(), only the main request is shown, not the dependent fetches, even though those fetches count toward quota and billing in production. Teams relying on Firestore emulation for testing can keep up with these tooling limitations via daily.dev."}}]} ```