- Notifications
You must be signed in to change notification settings - Fork 1.3k
Closed
Labels
scope/frontendseverity/lowSeverity level for a bug. Applicable only for bug label.Severity level for a bug. Applicable only for bug label.status/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedstatus/confirmedA bug which actuality is confirmedA bug which actuality is confirmedtype/bugSomething isn't workingSomething isn't working
Description
Describe the bug (Actual behavior)
Metrics 'Port' field is too wide and is under the metrics 'Metrics type' field
Expected behavior
- Port field width should match the expected value length
- According to common practice it might be better to put it to the right of 'Metrics type' field. Since the server name is not shown. OR maybe shown the server name it will connect on the specified port number for additional clarity?
Set up
dac023e
the 'wizard' branch
Steps to Reproduce
- Set up the Kafka UI with a setting
DYNAMIC_CONFIG_ENABLED: true - Open dashboard and click 'Configure' for and existing cluster or 'Configure new cluster'.
- See the Metrics section, or add it, if it is missing.
Screenshots
Additional context
Metadata
Metadata
Assignees
Labels
scope/frontendseverity/lowSeverity level for a bug. Applicable only for bug label.Severity level for a bug. Applicable only for bug label.status/acceptedAn issue which has passed triage and has been acceptedAn issue which has passed triage and has been acceptedstatus/confirmedA bug which actuality is confirmedA bug which actuality is confirmedtype/bugSomething isn't workingSomething isn't working
