We have a Verbose stream option that filters out additional events such as storing uplinks (as.packages.storage.up.store).
Why do we need this? Who uses it, and when?
A useful option would be to filter on specific event types based on the context. Users can use this to only look for certain events (ex: Join Requests) and this can be very useful for debugging.
The Live data panel of a gateway and application overview can potentially have high volume of events from multiple end devices.
The Live data panel of individual end devices will have relatively fewer events since that view already gets a list of events filtered by the end device IDs.
Proposed Implementation
For the Live data panel of a gateway and an application, provide the following options to filter.
Message based
a. Join requests (*.join.*)
b. Upstream data (*.up.*)
c. Downstream data (*.down.*)
End device based: Filter per end device identifier.
In the future we can also consider filtering over JoinEUI or Device Address but that requires parsing the Data field. Let's keep this simple for now.
Contributing
[X] I can help by doing more research.
[ ] I can help by implementing the feature after the proposal above is approved.
[X] I can help by testing the feature before it's released.
Validation
[ ] The feature is tested in a staging environment.
Summary
Filter events in the live data view. This replaces https://github.com/TheThingsNetwork/lorawan-stack/issues/2231
Current Situation
We have a
Verbose streamoption that filters out additional events such as storing uplinks (as.packages.storage.up.store).Why do we need this? Who uses it, and when?
A useful option would be to filter on specific event types based on the context. Users can use this to only look for certain events (ex: Join Requests) and this can be very useful for debugging.
The
Live datapanel of a gateway and application overview can potentially have high volume of events from multiple end devices. TheLive datapanel of individual end devices will have relatively fewer events since that view already gets a list of events filtered by the end device IDs.Proposed Implementation
For the
Live datapanel of a gateway and an application, provide the following options to filter.*.join.*) b. Upstream data (*.up.*) c. Downstream data (*.down.*)In the future we can also consider filtering over JoinEUI or Device Address but that requires parsing the
Datafield. Let's keep this simple for now.Contributing
Validation
Code of Conduct