Observability & Metrics
With hundreds to thousands of events going through your Inngest Apps, triggering multiple Function runs, getting a clear view of what is happening at any time is crucial.
The Inngest Platform provides observability features for both Events and Function runs, coupled with Event logs and a detailed Function Run details to inspect arguments and steps timings.
Function runs observability
The Functions list page provides the first round of essential information in one place with:
- Triggers: Events or Cron schedule
- Failure rate: enabling you to quickly identify a surge of errors
- Volume: helping in identifying possible drops in processing
Function metrics
Navigating to a Function displays the Function metrics page, composed of 7 charts:
All the above charts can be filtered based on a time range (ex: last 24 hours), a specific Function or App.
Let's go over each chart in detail:
Function Status
The Function Status chart provides a snapshot of the number of Function runs grouped by status.
How to use this chart?
This chart is the quickest way to identify an unwanted rate of failures at a given moment.
Failed Functions
The Failed Functions chart displays the top 6 failing functions with the frequency of failures.
How to use this chart?
You can leverage this chart to identify a possible elevated rate of failures and quickly access the Function runs details from the "View all" button.
Total runs throughput
The Total runs throughput is a line chart featuring the rate of Function runs started per app. This shows the performance of the system of how fast new runs are created and are being handled.
How to use this chart?
Flow control might intentionally limit throughput, this chart is a great way to visualize it.
Total steps throughput
The Total steps throughput chart represents the rate of which steps are executed, grouped by the selected Apps.
How to use these charts?
The Total steps throughput chart is helpful to assess the configuration of your Inngest Functions.
For example, a low Total steps throughput might be linked to a high number of concurrent steps combined with a restrictive concurrency configuration.
SDK request throughput
The SDK request throughput chart indicates the throughput at which SDK requests (or steps) are queued and executed, across all selected Apps.
How to use this chart?
This chart is a useful tool to evaluate in the requests sent by the Inngest Platform matches the number of steps created by Functions runs.
The SDK request throughput chart is also useful to evaluate the number of requests sent to your application over time.
Backlog
The Backlog highlights the number of Function runs waiting to processed at a given time bucket, grouped by the selected Apps.
How to use this chart?
This chart is useful to assess the Account Concurrency capacity of your account and to identify potential spikes of activity.
Account concurrency
The Account concurrency displays the concurrency usage in time, at the account level.
The red line illustrates the maximum concurrency capacity of the account.
How to use this chart?
This chart is useful to quickly identify is some increase in Backlog or drop in Total run throughput is linked to your account's concurrency capacity.
Each account gets a maximum concurrency capacity, computed by adding the total number of running steps across all applications.
Events observability
Events volume and which functions they trigger can become hard to visualize.
Thankfully, the Events page gives you a quick overview of the volume of Events being sent to your Inngest account:
Get more detailed metrics for a dedicated event by navigating to it from the list:
Events metrics and logs
The Event page helps quickly visualize the throughput (the rate of event over time) and functions associated with this event.
The event occurrences feature a “Source” column, which is helpful when an event is triggered from multiple Apps (ex, using different languages):
Clicking on a specific event will redirect you to its Logs.
The Event Logs view provides the most precise information, with the linked Function run and raw event data.
Such information, combined with the ability to forward the event to your Local Dev Server instance, makes debugging events much quicker:
