Antoine Cotten
Antoine Cotten
As shown in the dashboard below, the processing queue is always full under load because the event processors can't cope with the number of concurrent message receivers. This comes from...
We should spawn and terminate receivers dynamically based on the current amount of messages being processed (internal queue lengths should be a good indicator of this) to optimize costs generated...
ref. https://docs.aws.amazon.com/sns/latest/dg/sns-http-https-endpoint-as-subscriber.html
The SDK v2 is available and brings really nice improvements: https://aws.amazon.com/blogs/developer/aws-sdk-for-go-version-2-general-availability/
The multi-tenant adapters for the `Filter` and `Splitter` types are somewhat "improperly" implemented. Instead of reacting to changes to objects and updating their HTTP muxes accordingly, each HTTP request requires...
We currently track changes to multi-tenant receive adapters by attaching an event handler with a custom filter (`hasAdapterLabelsForType()`) to Deployment/KnService informers. The filtering occurs on a set of common labels...
The Synchronizer adapter should report the standard set of TriggerMesh metrics, similarly to what we did in triggermesh/triggermesh#660 and triggermesh/triggermesh#662: - [processing latency](https://github.com/triggermesh/triggermesh/blob/e076d967e7304017c692dc15388a9956cb0c0c7c/pkg/flow/adapter/transformation/adapter.go#L144) - [processing outcome](https://github.com/triggermesh/triggermesh/blob/e076d967e7304017c692dc15388a9956cb0c0c7c/pkg/flow/adapter/transformation/adapter.go#L148-L152) - ~dispatch latency and...
Opening this issue on behalf of @Mukesh9092 When the handler is inside `aws/common/src/handler.js`, it might be desirable that this directory structure is preserved in the generated image. It might also...
During a build, I witnessed the following error: ```json { "level":"error", "ts":1604588951.297186, "caller":"git/git.go:54", "msg":"Error running git [fetch --recurse-submodules=yes --depth=1 origin --update-head-ok --force master]: exit status 128 fatal: couldn't find remote...