Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix usage of multiple stages with same name #333

Open
KalmanMeth opened this issue Nov 17, 2022 · 0 comments
Open

Fix usage of multiple stages with same name #333

KalmanMeth opened this issue Nov 17, 2022 · 0 comments

Comments

@KalmanMeth
Copy link
Collaborator

We saw an example with the following configuration:

pipeline:
- name: ingest_collector
- follows: ingest_collector
  name: transform_generic
- follows: transform_generic
  name: transform_network
- follows: transform_network
  name: extract_aggregate
- follows: transform_network
  name: extract_conntrack
- follows: extract_conntrack
  name: extract_aggregate
- follows: extract_aggregate
  name: encode_prom

The same stage (extract_aggregate) is specified twice as following 2 different stages. This was done to achieve the desired output, one with connection tracking and without.
Apparently this works because we now use channels as input, so a stage may receive from 2 different sources.
Not sure this is desired to be legal. We should probably have detected this and issued an error.
Ensure that things work as desgined, and provide the correct sequence of stages to achieve the desired outcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant