ref(crons): Fix N+1 query in MonitorSerializer by removing is_muted property #103693
+126
−50
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.
Removes the computed property Monitor.is_muted and replaces it with a standalone
is_monitor_muted(monitor) function for better clarity and to fix an N+1 query
issue in MonitorSerializer.
The serializer now efficiently computes mute status for multiple monitors in a
single pass by checking if any environment is unmuted, rather than calling the
property on each monitor individually which would trigger separate queries.
Changes: