Bug #30628 Timestamp on graph at initialization includes milliseconds

• Submitted: 24 Aug 2007 16:52
• Modified: 27 Aug 2007 18:33
• Reporter: Andy Bang
• Status: Won't fix
• Category: MySQL Enterprise Monitor: Server
• Severity: S3 (Non-critical)
• Version: 1.2.0
• OS: Any
• Assigned to: Assigned Account
• CPU Architecture: Any

[24 Aug 2007 16:52] Andy Bang

Description:
Very minor bug.  The timestamp on a graph on the Monitor tab includes milliseconds before agents have pinged in and supplied some data (16:00:00.000).  I'll attach an image showing this.  I *think* this is generated in the server, but I'm sure Oldag will assign to Josh if not.

How to repeat:
1) Start with a fresh deployment.
2) Go through first-time login.
3) Do not start any agents.
4) Look at graphs on Monitor tab -- they include milliseconds in the timestamp.

Suggested fix:
Make the timestamp just like the one you see after data shows up.  Actually, at this point wouldn't it almost be better to show something like "No data available"?

[24 Aug 2007 16:52] Andy Bang

Image of graphs on Monitor tab at startup

Attachment: GraphInit.png (image/png, text), 8.19 KiB.

[13 Mar 2014 13:36] Omer Barnir

This bug is not scheduled to be fixed at this time.