Observability
Keep your Salesforce org running without disruption
From Flow & Apex errors to org limits, catch issues before they cost your business
From Flow & Apex errors to org limits, catch issues before they cost your business
Use one centralized dashboard to detect & understand issues in your org - from Flow and Apex errors to API limits.
Address issues before they impact your org, keeping business-critical processes stable and avoiding downtime.
Use data trends to prioritize work, plan strategically, and show how your teams’ fixes directly impact org health.
Teams with observability tools are 50% more likely to catch critical bugs within a day and 48% more likely to fix them just as quickly."
When Salesforce errors go unnoticed, commercial teams are blocked and developers are constantly troubleshooting. Surface errors & impacted users in one dashboard to resolve issues, fast.
Understand and track your Salesforce org limits in one place. Monitor daily limits and get alerts before they’re hit — so critical processes keep running smoothly.
Start a free trial and see your org in a whole new way.
When you’re not actively monitoring the state of your org, you’re missing critical issues. That’s why Salesforce teams are adopting observability; not just for error logs, but for the insights, detailed data and context that explain not just what went wrong, but why. With that understanding, you can plan better, respond faster, and improve platform stability.
Gearset brings observability best practices to your Salesforce development, without the need for specialist setup or ongoing maintenance.
You can quickly set up observability jobs in Gearset in just a few clicks. Simply select the org you want to monitor, choose the org limits to track and display, and set your preferred threshold notification limits for warnings and critical alerts. Gearset will automatically configure the settings you need for Flow and Apex error monitoring. See our job setup documentation for more information.
With Gearset you can set up notifications for Microsoft Teams and Slack instead of relying on default Salesforce Flow or Apex exception emails. You can control what you get alerted about; create notification rules based on error content and/or volume of alerts within a time period. For example, a notification when a specific Flow errors more than 100 times within 5 minutes.
With Gearset you can set up notifications to be alerted in Microsoft Teams and Slack when your org limits are at your pre-set threshold. This way you can react fast and prevent downtime.
You can monitor up to two Salesforce orgs. If you need additional monitoring jobs, contact us via the in-app chat or email sales@gearset.com.
Gearset’s observability dashboard displays total errors, broken down into Flow errors and Apex errors, as well as total users impacted. You’ll see the most common Flow error types, top Flows with errors (including scheduled Flows), and top Apex classes with errors.
You can see the usage of your org limits such as API limits, platform events, storage limits and email limits.
As well as seeing a snapshot of the state of your org right now, you can also use the timeline view to analyze data trends and compare to previous time periods.
You can export the dashboard as a PDF report and quickly share it with other stakeholders.
We use the Salesforce REST API to access information about org limits. All org limits information is retrieved using a single API call.
Observability from Gearset can be purchased as part of your DevOps package or standalone. It costs $1 per standard Salesforce user, per month, with a minimum spend of $100 a month.
When an Observability subscription is purchased, it is freely available to all members of your Gearset team. A team member does not need a metadata licence to have access. You can invite additional users to your Gearset team to access the Observability features at no extra cost.
Gearset ingests Salesforce’s auto-generated error emails for both Flow failures and unhandled Apex exceptions, and consolidates them into a single view. For Flows, this means you can see the failed element, error message, and Flow interview details without having to dig through individual notifications. For unhandled Apex exceptions, Gearset extracts the exception details that Salesforce normally surfaces through debug logs and error emails, so developers can investigate and fix issues without trawling through raw log files.
By centralizing both Flow and Apex errors, Gearset makes it easier to monitor unhandled exceptions at scale and resolve issues faster.
The practice of observability is about giving Salesforce teams confidence that their code and configuration is performing as expected in production.
Whereas monitoring tools simply surface data, an observability solution helps you to identify trends and understand root causes. These insights help teams to decide what's a priority, and feed this into planning for future development cycles. When teams gain visibility, they can drive continuous improvement to org performance across the Salesforce development lifecycle.
For admins and developers, observability improves exception handling, with faster debugging and error resolution. For architects and platform managers, observability supports the design of scalable systems that anticipate failure, adapt to growth, and stay resilient under platform constraints. This ultimately minimizes downtime and ensures platform-wide stability.
You can’t disable Flow and Apex error email notifications from Salesforce directly. However with a Salesforce error monitoring solution like Gearset you can consolidate Flow and Apex code failures into one centralized hub, and configure real-time alerts in Slack or Teams, so you’re not buried in error emails anymore.
Beyond cutting down noise, centralizing your error monitoring gives you a complete audit trail of all errors occurring, so it’s easier to spot recurring problems, prioritize fixes, and share context with your team.
Get started with a free trial, or book a demo with one of our DevOps experts.