You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Feel free to extending the syntax of servers.yaml with additional optional parameters.
However, a couple of things regarding servers.yaml:
The (historical) reason it was created was that for some setups (e.g. mixture of emulated and real NFs), mixtures of k8s and VMs were used. What I got from our colleagues was a VM list in the format of servers.yaml.
The data in servers.yaml is currently used to map and group messages to "actors" for diagram generation
The port filtering is applied at the tshark stage to avoid generating huge PDML files (e.g. in the case user plane is present in a capture, the PDML file could be enormous)
It is however a bit "cumbersome" to have all the parameters in the command line. So a YAML-based config parameter input sounds definitely like an improvement in readability :)
Meybe it will be better to add port numbers to
servers.yaml
and not set its each time in command line, when we launch5g-trace-vizualizer
???The text was updated successfully, but these errors were encountered: