OpenTelemetry Protcol (OTLP) identity integration #180
Merged
LorenzoTettamanti merged 32 commits intoCortexFlow:0.1.5from Feb 8, 2026
Merged
OpenTelemetry Protcol (OTLP) identity integration #180LorenzoTettamanti merged 32 commits intoCortexFlow:0.1.5from
LorenzoTettamanti merged 32 commits intoCortexFlow:0.1.5from
Conversation
…. Remove duplicated code in metrics module
…pace implementation. Added a small doc in the conntracker/main.rs file
…ed.Improved map handlers code
…otel daemonset with otel agent and collector
…removed useless conversion from u8 to 64 with .into() for state variable
…te. .update identity kubernetes manifest with the otel env variables.
…ntity (VethLog) data structure
…"loop" pattern. Code cleaning
LorenzoTettamanti
added
enhancement
LorenzoTettamanti
added
ebpf
…n map_handlers.rs
…ed send_tracked_veth_requests function in api/requests.rs
…rs in the identity service
…s for PacketLog, VethLog and TcpPacketRegistry
…dentity crate to the common crate. Added BufferType enum to list different buffers readers. Added buffer_type module in cortexbrain common (experimental)
…d VethEvent protobuffer message type
…ed representation for the VethLog structure. changed dev_addr type from [u32;8] to [u8;6] (see https://wiki.osdev.org/Address_Resolution_Protocol). Added unit tests to check VethLog structure bytes size. Changed "actual program" to "kernel_symbol" in the load_program function
…ame instead of relying on the declaration order during the startup
…the veth event in the agent api
This was
linked to
issues
Feb 5, 2026
Collaborator
|
@LorenzoTettamanti can you check I think the refactoring in common crate broke metrics build 
Command to reproduce |
Collaborator
|
OTLP is working as expected identity 
otlp collector 
otlp agent 
|
siddh34
approved these changes
Feb 8, 2026
Collaborator
|
@LorenzoTettamanti things are working fine! |
Member
Author
|
@siddh34 i'm merging the changes |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Related issues: #181 #158 #174 #182
Changes
This PR introduces several core changes to simplify the current codebase and avoid unnecessary duplication.
Key changes:
cfcli install blocklist[[Enhancement][Cli]: Add command to repair/create the blocklist configmap #181]cfcli monitoring vethto list the monitored virtual ethernet interfaces [[Enhancement][Cli] Add a command to see the tracked veth #182]Notes
NOTE:
We no longer need to attach the BPF programs to all virtual Ethernet interfaces to trace network packets. We can leverage the role of the bridge interfaces (see the image below) to directly trace the TCP packets without dynamically attaching the programs to all the veth interfaces. Up to now, I've implemented this idea, and I haven't noticed a significant change in the behaviour. I'm open to discussing a better implementation of all the logic, as this will for sure need more tests to confirm the idea presented above. I will also suggest not to remove the veth tracing logic completely because that can be useful to debug the system and can enhance the context information.