This repository was archived by the owner on Feb 7, 2024. It is now read-only.
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.
Currently, you can use only the database (through the model) for the statistics storage. This can be quite unpleasant as MySQL is not so good as a time-series database when it comes to huge data ingestion. You might want to save them somewhere else, like Elasticsearch or InfluxDB.
To fix this, you may now define your own statistics driver that can store/delete data with any kind of database, leaving this customization to the user implementation. You can ingest the record and use it to build the statistic payload, or you can statically create new records or delete records.
For example, this is how the database driver looks: