Artem Glazychev

@srini38 Very happy about it! If you can collect the logs, that will be very cool. We are especially interested in the logs from the nsm-system and ns-nse-composition pods. It...

Logs from opentelemetry-collectior > v0.35.0: ``` Error: failed to get config: cannot unmarshal the configuration: error reading exporters configuration for "jaeger": 1 error(s) decoding: * '' has invalid keys: insecure...

Hello @U24543426, Thank you for appreciating! I think you are right that it is convenient to be able to configure this. 1. So, as you can see in the examples,...

@edwarnicke Could you please share your thoughts?

Also I guess we need to fix the prefix setting. For example, if we use: ``` - name: NSM_CIDR_PREFIX value: 1200::1:0/127, 1200::2:0/127 ``` that means: ``` ... point2pointipam.NewServer(1200::1:0/127), point2pointipam.NewServer(1200::2:0/127) ......

/cc @denis-tingaikin

For the custom interface name, you are absolutely right - I think this can be done quite simply. I can briefly explain: For the NSE (for example `cmd-nse-icmp-responder`) we set...

Thanks for reporting! So, we have the following problems: 1. Custom IP address for NSC and NSE 2. Custom interface name for NSE 3. Grouping CIDR prefixes Is that correct?...

Temporary solutions: 1. Disable `TestNSMGR_CloseHeal: With NSE expiration` 2. Disable `querycache`

Hi @BenAgai , There is currently no such functionality, but we can consider it. @edwarnicke Do you have any thoughts?