Change Details

{F36975194}Due to amount of incoming events from the upstream we've got and increase of the internal and external traffic. Also it's visible by the size of the compressed topics in kafka clusters. It's pretty expected, but the traffic flows can be optimized, for example via enable gzip compression on different levels. Attached there is a screenshot for the traffic hops in internal NAT gateway. **ToDo**: - analyze the reasons of traffic increase - prepare a dashboards which will show us thin&and thick places for the whole traffic journey - optimize the traffic flows by enabling the compressions where it's feasible, or propose alternative solutions.

Due to amount of incoming events from the upstream we've got and increase of the internal and external traffic. Also it's visible by the size of the compressed topics in kafka clusters. It's pretty expected, but the traffic flows can be optimized, for example via enable gzip compression on different levels. Attached there is a screenshot for the traffic hops in internal NAT gateway - {F36975194}. **ToDo**: - analyze the reasons of traffic increase - prepare a dashboards which will show us thin&and thick places for the whole traffic journey - optimize the traffic flows by enabling the compressions where it's feasible, or propose alternative solutions.

{F36975194}Due to amount of incoming events from the upstream we've got and increase of the internal and external traffic. Also it's visible by the size of the compressed topics in kafka clusters. It's pretty expected, but the traffic flows can be optimized, for example via enable gzip compression on different levels. Attached there is a screenshot for the traffic hops in internal NAT gateway - {F36975194}. **ToDo**: - analyze the reasons of traffic increase - prepare a dashboards which will show us thin&and thick places for the whole traffic journey - optimize the traffic flows by enabling the compressions where it's feasible, or propose alternative solutions.