Details
-
Type:
Improvement Request
-
Status:
New
-
Priority:
Minor
-
Resolution: Unresolved
-
Affects Version/s: 5.2.0
-
Fix Version/s: 5.4.1
-
Component/s: Monitoring
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||||
|---|---|---|---|---|---|
|
|
||||
A solution could be to add the listening port of the remote TCP transporter but we are not able to get it easily. The port that we can get is the client TCP port that is not the listening TCP port of the TCP transporter.
The only way is to implement a conversational protocol (ex: once connection is accepted, a command 'HELLO I am container-0' could be sent). This protocol should be implemented rewriting the TCP transporter as defined in PETALSESBCONT-437.