chore: database-based metrics to monitor processing engine#4383
Merged
Conversation
Signed-off-by: Lucas Pinheiro <lucas@superplane.com>
|
👋 Commands for maintainers:
|
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
Signed-off-by: Lucas Pinheiro <lucas@superplane.com>
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 237dfe0. Configure here.
Signed-off-by: Lucas Pinheiro <lucas@superplane.com>
WashingtonKK
pushed a commit
to WashingtonKK/superplane
that referenced
this pull request
Apr 27, 2026
…ehq#4383) We need more visibility into the amount of events and executions the workers are handling. Here, we add three things: 1. A generic `db.rows.affected.count` counter for DB operations. It uses table and operation (create | update | delete) as attributes, which allow us to slice things as we may need. This is mostly for overall insight into how much data we are handling. We use [gorm callbacks](https://gorm.io/docs/write_plugins.html#Callbacks) for this. 2. A `workflow_events.pending.count` gauge to check the number of current pending events. A high number here indicates degradation of the processing engine 3. A `workflow_node_executions.pending.count` gauge to check the number of pending executions. Similar to [2], high number here indicates degradation. --------- Signed-off-by: Lucas Pinheiro <lucas@superplane.com> Signed-off-by: WashingtonKK <washingtonkigan@gmail.com>
re-pixel
pushed a commit
to re-pixel/superplane
that referenced
this pull request
May 4, 2026
…ehq#4383) We need more visibility into the amount of events and executions the workers are handling. Here, we add three things: 1. A generic `db.rows.affected.count` counter for DB operations. It uses table and operation (create | update | delete) as attributes, which allow us to slice things as we may need. This is mostly for overall insight into how much data we are handling. We use [gorm callbacks](https://gorm.io/docs/write_plugins.html#Callbacks) for this. 2. A `workflow_events.pending.count` gauge to check the number of current pending events. A high number here indicates degradation of the processing engine 3. A `workflow_node_executions.pending.count` gauge to check the number of pending executions. Similar to [2], high number here indicates degradation. --------- Signed-off-by: Lucas Pinheiro <lucas@superplane.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We need more visibility into the amount of events and executions the workers are handling. Here, we add three things:
db.rows.affected.countcounter for DB operations. It uses table and operation (create | update | delete) as attributes, which allow us to slice things as we may need. This is mostly for overall insight into how much data we are handling. We use gorm callbacks for this.workflow_events.pending.countgauge to check the number of current pending events. A high number here indicates degradation of the processing engineworkflow_node_executions.pending.countgauge to check the number of pending executions. Similar to [2], high number here indicates degradation.