Skip to content

Blog: Subnet labels and external traffic#29

Open
jotak wants to merge 8 commits intonetobserv:mainfrom
jotak:subnet-labels
Open

Blog: Subnet labels and external traffic#29
jotak wants to merge 8 commits intonetobserv:mainfrom
jotak:subnet-labels

Conversation

@jotak
Copy link
Member

@jotak jotak commented Nov 10, 2025

found a "bug" while writing this blog: netobserv/flowlogs-pipeline#1127

@github-actions
Copy link

github-actions bot commented Nov 10, 2025

🚀 PR Preview for netobserv.io has been successfully deployed!
It's available at https://netobserv-io-blog-29-preview.surge.sh and will be removed when the PR closes.

Copy link
Contributor

@leandroberetta leandroberetta left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jotak very nice and useful blog post! thanks! I've just added some minor suggestions but looks good to me!


![Subnet labels by default](./subnet-labels-default.png)

Every time `flowlogs-pipeline` has to process a network flow, it checks if the IP belongs to any of the defined subnet, and if so, it associates the flow with the related label.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Every time `flowlogs-pipeline` has to process a network flow, it checks if the IP belongs to any of the defined subnet, and if so, it associates the flow with the related label.
Every time `flowlogs-pipeline` has to process a network flow, it checks if the IP belongs to any of the defined subnets, and if so, it associates the flow with the related label.

```

{#admon title="Info"}
In FlowMetrics, when there are several filters for the same key, those filters are OR'ed, ie. the match is satisfied if one at least is satisfied. Filters on different keys are AND'ed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
In FlowMetrics, when there are several filters for the same key, those filters are OR'ed, ie. the match is satisfied if one at least is satisfied. Filters on different keys are AND'ed.
In FlowMetrics, when there are several filters for the same key, those filters are OR'ed, i.e. the match is satisfied if at least one is satisfied. Filters on different keys are AND'ed.


## Going further: identifying the external workloads

All good so far, however this doesn't answer the question: where is this traffic flowing to (or from) ?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
All good so far, however this doesn't answer the question: where is this traffic flowing to (or from) ?
All good so far, however this doesn't answer the question: where is this traffic flowing to (or from)?

Copy link
Member

@memodi memodi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

blog looks good to me.
nice work @jotak , thanks.

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

Successfully merging this pull request may close these issues.

4 participants