Petals ESB Container

Incoming TCP Transporter monitoring metrics should return container name instead of container IP address

Details

  • Type: Improvement Request Improvement Request
  • Status: New New
  • Priority: Minor Minor
  • Resolution: Unresolved
  • Affects Version/s: 5.2.0
  • Fix Version/s: 5.4.0
  • Component/s: None
  • Security Level: Public
  • Description:
    Hide

    TCP Transporter metrics : 'getIncomingConnections' and 'getIncomingMessagesCount' return metrics which identify container solely by their IP address.

    These metrics should identify containers with their container name.

    Note: This could by a costly check to be done each time (on each message received or on each probe read), this change should be done with care.

    Show
    TCP Transporter metrics : 'getIncomingConnections' and 'getIncomingMessagesCount' return metrics which identify container solely by their IP address. These metrics should identify containers with their container name. Note: This could by a costly check to be done each time (on each message received or on each probe read), this change should be done with care.
  • Environment:
    -

Issue Links

Activity

Pierre Souquet made changes - Mon, 7 Jan 2019 - 17:31:17 +0100
Field Original Value New Value
Assignee Christophe DENEUX [ cdeneux ] Pierre Souquet [ psouquet ]
Fix Version/s 5.3.0 [ 10877 ]
Priority Minor [ 4 ]
Description TCP Transporter metrics : getIncomingConnections and getIncomingMessagesCount return metrics which identify container solely by their IP. (Or Ip:port if [PETALSESBCONT-464](https://jira.petalslink.com/browse/PETALSESBCONT-464) is solved)

These metrics should identify containers with their container name.
This could by a costly check to be done each time (each message received or each probe read), this change should be done with care.
TCP Transporter metrics : getIncomingConnections and getIncomingMessagesCount return metrics which identify container solely by their IP. (Or Ip:port if [PETALSESBCONT-464] is solved)

These metrics should identify containers with their container name.
This could by a costly check to be done each time (each message received or each probe read), this change should be done with care.
Pierre Souquet made changes - Mon, 7 Jan 2019 - 17:31:33 +0100
Link This issue depends on PETALSESBCONT-464 [ PETALSESBCONT-464 ]
Christophe DENEUX made changes - Wed, 16 Jan 2019 - 10:16:55 +0100
Summary incoming TCP Transporter monitoring metrics should return container name instead of "IP:Port" or "IP" Incoming TCP Transporter monitoring metrics should return container name instead of container IP address
Description TCP Transporter metrics : getIncomingConnections and getIncomingMessagesCount return metrics which identify container solely by their IP. (Or Ip:port if [PETALSESBCONT-464] is solved)

These metrics should identify containers with their container name.
This could by a costly check to be done each time (each message received or each probe read), this change should be done with care.
TCP Transporter metrics : '{{getIncomingConnections}}' and '{{getIncomingMessagesCount}}' return metrics which identify container solely by their IP address.

These metrics should identify containers with their container name.


Note: This could by a costly check to be done each time (on each message received or on each probe read), this change should be done with care.
Hide
Christophe DENEUX added a comment - Thu, 13 Apr 2023 - 17:00:13 +0200

Postponed to version 5.4.0 or upper

Show
Christophe DENEUX added a comment - Thu, 13 Apr 2023 - 17:00:13 +0200 Postponed to version 5.4.0 or upper
Christophe DENEUX made changes - Thu, 13 Apr 2023 - 17:00:13 +0200
Fix Version/s 5.4.0 [ 11131 ]
Fix Version/s 5.3.0 [ 10877 ]



People

Dates

  • Created:
    Mon, 7 Jan 2019 - 17:30:50 +0100
    Updated:
    Thu, 13 Apr 2023 - 17:00:13 +0200