Bug #58196 MEM: can't specify portnumber for notifications

• Submitted: 15 Nov 2010 9:57
• Modified: 15 Nov 2010 11:32
• Reporter: Daniël van Eeden
• Status: Not a Bug
• Category: MySQL Enterprise Monitor: Configuration
• Severity: S4 (Feature request)
• Version: 2.3.0.2036
• OS: Any
• CPU Architecture: Any

[15 Nov 2010 9:57] Daniël van Eeden

Description:
It's possible to set the hostname which is used in notification, but not the port number.

Setting:
"Settings" → "Global Settings" → "Server Hostname"  → "Hostname"

Description:
"This hostname overrides the operating system hostname for use in notifications."

We use MEM behind apache2 and mod_proxy. Apache is used as extra security layer, it can provide SSL/TLS with checking of client certificates, limit access to certain IP ranges and improve performance by using caching. The company policy is to put apache in front of almost any web service.

This works great except for the notifications which use the tomcat port 1080 instead of port 80 on which apache2 is listening.

How to repeat:
Setup MEM with tomcat port 1080 and apache2/mod_proxy on port 80 and send notifcations and check the port number in the notification

Suggested fix:
Add a setting to specify the port or make it possible to specify a host:port in the hostname setting.

[15 Nov 2010 11:02] Valeriy Kravchuk

Thank you for the feature request.

[15 Nov 2010 11:32] Mark Leith

There is already a separate field to take this in the settings page, directly below the Hostname field:

"Port
[...]
This port overrides the Apache Tomcat port for use in notifications."