When there are too many logs, we start a workflow that pauses the logs stream and asks for confirmation from the user. This is to:
prevent from getting too many logs from the API
warn the user about the limitation
It comes with some problems:
people don't like limitations
people don't like to answer questions
those questions are very hard to understand
All this workflow comes from the fact that the API is based on Pulsar. The index-as-a-service will help us tackle those limitations, but this is to be done in the long term.
This is also an experiment, but maybe this is not a good idea, and maybe we can find other alternatives.
When there are too many logs, we start a workflow that pauses the logs stream and asks for confirmation from the user. This is to:
It comes with some problems:
All this workflow comes from the fact that the API is based on Pulsar. The index-as-a-service will help us tackle those limitations, but this is to be done in the long term.
This is also an experiment, but maybe this is not a good idea, and maybe we can find other alternatives.