Conversation
|
|
||
| ## CLI | ||
|
|
||
| When using the CLI, the operator is not involved, which means you can use it without installing NetObserv as a whole. It uses a special mode of the eBPF agents that embeds FLP. |
There was a problem hiding this comment.
There was a problem hiding this comment.
Yes sounds good. Note that the collector is not involved for the metrics generation. That could be mentionned too
There was a problem hiding this comment.
| When using the CLI, the operator is not involved, which means you can use it without installing NetObserv as a whole. It uses a special mode of the eBPF agents that embeds FLP. | |
| When using the CLI, the operator is not involved, which means you can use it without installing NetObserv as a whole. It uses a special mode of the eBPF agents that embeds FLP. | |
| Flows and Packets captures will deploy both agents and collector. | |
| Metrics captures will only deploy agents. |
There was a problem hiding this comment.
Maybe that's something I missed .. how does metrics work when using the kubectl plugin ? The readme mentions only a make target for capturing metrics. If I run oc netobserv flows ... can I get metrics as well?
There was a problem hiding this comment.
nvm I've checked the PR, it's explained: $ ./build/oc-netobserv metrics --enable_pktdrop="true" --enable_dns="true" --enable_rtt="true"
next question: README says that's only for openshift, but what if I have prometheus without openshift? I guess I can still have the metrics, it's just the charts that I won't get, correct?
There was a problem hiding this comment.
Yes if you have a ServiceMonitor you will have the metrics
But the configmap in openshift namespace will be ignored
|
|
||
| - An [eBPF agent](https://github.com/netobserv/netobserv-ebpf-agent), that generates network flows from captured packets. | ||
| - It is attached to any/all of the network interfaces in the host, and listens for packets (ingress+egress) with [eBPF](https://ebpf.io/). | ||
| - Packets are aggregated into logical flows (similar to NetFlows), periodically exported to a collector, generally FLP. |
There was a problem hiding this comment.
Should we mention the packet capture here ?
That may come in the operator too in the future
Co-authored-by: Julien Pinsonneau <91894519+jpinsonneau@users.noreply.github.com>
Co-authored-by: Julien Pinsonneau <91894519+jpinsonneau@users.noreply.github.com>
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: jotak The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2 participants
This doc is very old and needs a refresh!
I'd move to mermaid charts, like what we have in the agent, which makes it easier to update.