---
schema_version: "1"
id: 5c02674447b3e29a4c693005b20e6c223360e0ce83b82dedd91855d5330252a2
title: Build with Events
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/platform/264-0-0/build_with_events.md
canonical_url: https://help.salesforce.com/s/articleView?id=platform.build_with_events.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 2c3cd5b6d4a4b601698e437a160b7fe5f11bb8fb8c639b8846c854a8d802f194
description: Monitor the performance of your event subscribers.
products:
  - Salesforce Platform
  - Security
release: "264"
---
# Build with Events

Monitor the performance of your event subscribers.

To monitor the performance of your event subscribers, scroll down to the Build with Events section of the Event Studio. Here you can see each Apex trigger, latency over the last one hour in seconds, last delivered event time, and status. We don’t show managed package triggers because they are not actionable. If the latency is above the recommended threshold, a small warning badge will appear next to the latency in seconds. This indicator means you should follow the advice given in [Apex Trigger Best Practices](https://developer.salesforce.com/docs/atlas.en-us.platform_events.meta/platform_events/platform_events_trigger_reco.htm) to try to reduce latency. The latency data is not real-time. It is based on usage metrics data and there can be a delay between the delivery activity and seeing it in the UI, especially if volumes are high. Clicking on a trigger takes you to a page that shows a graph depicting the subscriber’s performance over time. The graph shows average latency for the specific trigger and if it is parallelized, it shows one line averaging the latency of all partitions. The graph is blank if there was no delivery during that hour.