add new pump type "hybrid" to send analytics data to MDCB #80
Assignees
Labels
Comments
This was referenced Sep 27, 2018
buger
pushed a commit
to TykTechnologies/tyk
that referenced
this issue
Oct 4, 2018
Another potentially better approach for TykTechnologies/tyk-pump#80 This approach allows to move some re-usable part of RPC without changing RPC server side. if it works then it cancels #1922 and TykTechnologies/tyk-sink#51 The idea is to do `rpc.Connect(...)` where we supply connection info, a couple of call backs for emergency mode and map of rpc funcs definitions to add to RPC client dispatcher. Then we can create `rpc.Purger` with all needed fields and run `PurgeLoop` with some ticker.
Merged
buger
pushed a commit
that referenced
this issue
Oct 7, 2018
added changes for #80 the same idea - just specify new `"hybrid"` pump in config and will start purging analytics to RPC stack.
|
Verified |
19 tasks
18 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This requires to add new pump type "hybrid" which would re-use tyk's RPC layer to send analytics data to MDCB.
Also, we should add new option in tyk to disable sending analytics to via RPC so tyk and tyk-pump won't clash processing analytics data.
The text was updated successfully, but these errors were encountered: