This repository was archived by the owner on Sep 3, 2025. It is now read-only.
add signal statistics support per signal#5852
Merged
aliciamatsumoto merged 4 commits intomainfrom Mar 21, 2025
Merged
Conversation
whitdog47
approved these changes
Mar 21, 2025
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
Extends the logic introduced in #5837 to additionally provide signal statistics per signal instance in addition to per entity type / entity id
Service Layer
Extends existing
get_signal_statsfunction to optionally include a signal id parameterApi
Adds new GET endpoint
/signals/{id}/statsto complement/signals/stats