feat(event): Add experimental v2 high usage events enpoints to API #3163
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
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
6 times, most recently
from
b1b116e to
13bd70c
Compare
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
2 times, most recently
from
41527cf to
1b63f2f
Compare
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
2 times, most recently
from
1094ff0 to
a4bb2c1
Compare
vincent-pochet
changed the title
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
2 times, most recently
from
ac84e88 to
0d0d0a1
Compare
vincent-pochet
changed the title
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
8 times, most recently
from
3ce9c08 to
41a1517
Compare
vincent-pochet
force-pushed
the
misc-high-usage-endpoint
branch
from
41a1517 to
afb1bd9
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.
Context
In the path to "high usage" feature, we need to open a new API end-point to allow receiving a large amount of events
Description
This PR add a two routes
POST /api/v2/events/high_usagePOST /api/v2/events/batch_high_usageBoth routes just format and push the payload into the event Kafka topic, without validation, evaluating custom expressions or handling post processing.
The post processing will happen later on a dedicated service/process