# Monitor - Logs should support a filter for the result code

**URL:** <https://community.hubspot.com/t/monitor-logs-should-support-a-filter-for-the-result-code/148865>\
**Category:** HubSpot Ideas\
**Tags:** design-manager-developer-tools\
**Created:** [April 30, 2026, 9:44am UTC](https://community.hubspot.com/t/monitor-logs-should-support-a-filter-for-the-result-code/148865 "2026-04-30T09:44:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![MarcelP1](https://d10pqhm3lwygmk.cloudfront.net/user_avatar/community.hubspot.com/marcelp1/32/88915_2.png) [@MarcelP1](https://community.hubspot.com/u/MarcelP1)\
**Post date:** [April 30, 2026, 9:44am UTC](https://community.hubspot.com/t/monitor-logs-should-support-a-filter-for-the-result-code/148865/1 "2026-04-30T09:44:33Z")

</div>

The developer tool for monitoring logs is the only way to access debug logs for serverless functions when migrating from 2025.1 to 2026.3.  
In the legacy projects it was possible to filter for status codes (1XX-5XX).

 ![MarcelP1_0-1777542205035.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/b/1/b19832129b1f8f71ddf068064bdb453b212c4f1a.png)

With the new “Developer Monitoring” this is no longer possible.

 ![MarcelP1_1-1777542228645.png](https://d2qpr2jzcazej7.cloudfront.net/original/3X/c/d/cd7517ae47be1ae5caebb83c57d9de9705dc3ecb.png)

Having this feature would re-enable developers to quickly track down issues.  
Best regards,  
Marcel

---

<div class="post-metadata">

**Author:** ![AHellmich](https://avatars.discourse-cdn.com/v4/letter/a/f9ae1b/32.png) [@AHellmich](https://community.hubspot.com/u/AHellmich)\
**Post date:** [August 10, 2026, 6:12pm UTC](https://community.hubspot.com/t/monitor-logs-should-support-a-filter-for-the-result-code/148865/2 "2026-08-10T18:12:57Z")

</div>

This is also a crucial functionality for our clients.