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

audit Domain Metrics should be rolling and calculated per AuditEvent insertion #636

Open
1 task
amydevs opened this issue Nov 22, 2023 · 0 comments
Open
1 task
Labels
development Standard development r&d:polykey:supporting activity Supporting core activity

Comments

@amydevs
Copy link
Contributor

amydevs commented Nov 22, 2023

Specification

As metrics are implemented on a case by case basis for each metric, this may not apply to all metrics.

However, for:

  • averages
  • max
  • min
  • totals

Metrics should be stored in the database and updated per insertion of a related AuditEvent

Additional context

Tasks

  1. Implement rolling average/total for connection audit metrics.
@amydevs amydevs added the development Standard development label Nov 22, 2023
@CMCDragonkai CMCDragonkai added the r&d:polykey:supporting activity Supporting core activity label Aug 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
development Standard development r&d:polykey:supporting activity Supporting core activity
Development

No branches or pull requests

2 participants