At this moment, Eventstream has no support for ingesting messages via HTTP REST / Webhook (like an Azure Function HTTP trigger). The same goes for egress to an HTTP REST / Webhook endpoint. S...
See also this Fabric community discussion: https://community.fabric.microsoft.com/t5/Eventstream/Options-for-High-Frequency-Low-Latency-API-Ingestion/m-p/5136740#M770 There dynamic behaviour is expected so the latest call starts where the previous one ended via a (timestamp) parameter. This way, gaps in ingestion or overlap or an ingestion overload (when a burst of data is provided) can be prevented.
