-
Type: Story
-
Status: Resolved (View Workflow)
-
Priority: Medium
-
Resolution: Done
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: Deprecated - VOLTHA
-
Labels:
-
Story Points:5
Explore several possible improvements to affinity router logging:
- Add kafka logging support (see bbsim and kafka-topic-exporter as examples)
- Look into moving items to TRACE level to reduce logging noise.
- Look into finer-grained control, similar to ONOS, that could adjust levels of different groups of log message. See if an existing golang package supports this feature.
- Examine how frames are printed (currently a series of bytes printed as decimal?) and see if they can be printed in a way that's easier to use. See if it's possible to decode gRPC frames and print the fields.
- Ensure that source/destination addresses and other header information is present.
- As arouter has a configuration/control API, see if that can be extended to allow log levels to be adjusted dynamically.
- Log-level should be configurable from helm chart values.yaml