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 | |||||
|---|---|---|---|---|---|
|
|
||||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Christophe DENEUX [ cdeneux ] | Pierre Souquet [ psouquet ] |
| Fix Version/s | 5.3.0 [ 10877 ] | |
| Priority | Minor [ 4 ] |
| Summary | incoming TCP Transporter monitoring metrics should return instead of IP:Port instead of IP | incoming TCP Transporter monitoring metrics should return "IP:Port" instead of "IP" |
| Link | This issue blocks PETALSESBCONT-465 [ PETALSESBCONT-465 ] |
| Summary | incoming TCP Transporter monitoring metrics should return "IP:Port" instead of "IP" | The key of incoming TCP-Transporter monitoring metrics is not distinctive enough |
| Description |
TCP Transporter metrics : {{getIncomingConnections}} and {{getIncomingMessagesCount}} return metrics which identify container solely by their IP. This is insufficient, multiple containers can be reachable through different ports on a same IP.
These metrics should identify containers with an "<IP>:<port>" format. |
TCP Transporter metrics : {{getIncomingConnections}} and {{getIncomingMessagesCount}} return metrics which identify container solely by their IP. This is insufficient, multiple containers can be reachable through different ports on a same IP. |
| Component/s | Monitoring [ 10078 ] |
| Link | This issue depends on PETALSESBCONT-437 [ PETALSESBCONT-437 ] |
| Fix Version/s | 5.4.0 [ 11131 ] | |
| Fix Version/s | 5.3.0 [ 10877 ] |
| Fix Version/s | 5.4.1 [ 11240 ] | |
| Fix Version/s | 5.4.0 [ 11131 ] |
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.