Registry - Stats #3993
Open
Registry - Stats #3993
+1,334
−261
Conversation
This file contains 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
Riron
force-pushed
the
add/change-aggregate
branch
from
58b0292 to
e9695eb
Compare
Riron
force-pushed
the
add/change-aggregate
branch
from
e9695eb to
49cd553
Compare
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Contexte
Introduction d'un nouvel objet "ChangeAggregate".
L'idée est que ces objets aggrègent le nombre de changements effectués par un utilisateur, sur une compagnie, dans une durée de temps de 5min maximum.
Si des modifications sont faites à la suite, via plusieurs calls API par exemple, et espacés de moins d'1 min, toutes les statistiques des ces appels seront aggrégées dans un unique objet.
Si les appels sont faits avec plus d'1min d'écart entre eux, ou plus de 5min d'écart avec l'appel initial, alors un nouvel objet ChangeAggregate sera créé.
C'est ces nouveaux objets qui sont affichés sur la page statistiques API, et ce sont eux qui nous permettent également de calculer la somme des changements effectués sur un SIRET, par type d'import et source (API / File).
Démo
Ticket Favro
Titre
Checklist