You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think all network export should probably be done from a separate process instead of creating sockets and contexts directly in the graph
We should refactor ami-export to support different protocols and refactor the export interface from the gui to the manager to support configuring options for these protocols, such as how many events/heartbeat to export and whether data should be batched or not.
Also the feedback to worker processes should happen over a different socket instead of using the same socket for ami-export so as not to unnecessarily send data to the workers that will just be thrown away anyway.
The text was updated successfully, but these errors were encountered:
I think all network export should probably be done from a separate process instead of creating sockets and contexts directly in the graph
We should refactor ami-export to support different protocols and refactor the export interface from the gui to the manager to support configuring options for these protocols, such as how many events/heartbeat to export and whether data should be batched or not.
Also the feedback to worker processes should happen over a different socket instead of using the same socket for ami-export so as not to unnecessarily send data to the workers that will just be thrown away anyway.
The text was updated successfully, but these errors were encountered: