Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Aggregation in the bridge #27

Open
norro opened this issue Nov 16, 2021 · 1 comment
Open

Aggregation in the bridge #27

norro opened this issue Nov 16, 2021 · 1 comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed

Comments

@norro
Copy link
Contributor

norro commented Nov 16, 2021

Allow bridge to be configured to aggregate diagnostic status messages before sensing a diagnostic array.
E.g. aggregate for a certain duration (publishing array with fixed rate), or aggregate until status for a defined set of diagnostic tasks was received.

Depends on #26, might become more relevant with #16.

@norro norro added enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed labels Nov 16, 2021
@bjv-capra
Copy link
Collaborator

I've also noticed this, what do you think about having a map of diagnostic arrays configured at startup when the lookup table is loaded. AFAIK, the diagnostic array is per updater_id. Thus, we'd need to have a diagnostic array per updater_id and fill it up when the tasks arrive, and as you suggested, wait for X time and send what the map had at that time.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants