Petals ESB Container

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

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: New
Priority: 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

Depends

This issue depends on:
PETALSESBCONT-464 The key of incoming TCP-Transporter monitoring metrics is not distinctive enough

Activity

Ascending order - Click to sort in descending order

Hide

Permalink

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

People

Assignee:

Pierre Souquet

Reporter:

Pierre Souquet
Watchers:

0

Dates

Created:

Mon, 7 Jan 2019 - 17:30:50 +0100

Updated:

Thu, 13 Apr 2023 - 17:00:13 +0200