In a product discussion on our dashboards, we identified that we want to slightly change how we count pipeline ingress and egress. Specifically, we want to count import no longer as egress, and export no longer as ingress. The new definition should be as follows:
[!NOTE]
Ingress: Data leaving the source operator of a deployed pipeline except for operators interacting with a node's storage, e.g., export. This data is measured in bytes or events.
[!NOTE]
Export: Data leaving the source operator of a deployed pipeline that interacts with a node's storage, e.g., export. This data is measured in events.
[!NOTE]
Egress: Data entering the sink operator of a deployed pipeline except for operators interacting with a node's storage, e.g., import. This data is measured in bytes or events.
[!NOTE]
Import: Data entering the sink operator of a deployed pipeline that interacts with a node's storage, e.g., import. This data is measured in events.
### Definition of Done
- [x] Separate pipeline metrics accordingly.
- [x] Hide import and export metrics from the pipeline overview page.
In a product discussion on our dashboards, we identified that we want to slightly change how we count pipeline ingress and egress. Specifically, we want to count
import
no longer asegress
, andexport
no longer asingress
. The new definition should be as follows: