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
Export Prometheus flow metrics with UE IP labels #375
Conversation
pfcpiface/telemetry.go
Outdated
ch <- uc.sessionLatency | ||
ch <- uc.sessionJitter | ||
ch <- uc.sessionTxPackets | ||
ch <- uc.sessionDroppedPackets | ||
ch <- uc.sessionTxBytes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ideally we should have separate interface for these, like we have one for PFCP layer metrics.
Overall split could be -
- PFCP protocol metrics - interface - how many messages, sessions etc
- PFCP fastpath metrics - interface - fastpath performance of the session/pdr, can benefit from more PFCP context
- Fastpath backend specific metrics - need not be interface, registered/exported in their own files - fastpath wide latency. jitter, packets, bytes, dropped, memory util etc
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I tried to implement that approach by creating a new collector. Seems to fit much better, no duplicate state needed.
This pull request has been stale for 30 days and will be closed in 5 days. Comment to keep it open. |
f6e33bf
to
e93ee9c
Compare
ee04d04
to
d031507
Compare
d031507
to
52c6dec
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
After discussion offline, I'm ok to merge it in this shape. We still would need to revise metrics APIs in future.
2c79d11
to
7cabef1
Compare
No description provided.