Is this a question, feature request, or bug report?

Bug report

Please describe the issue you observed

• What did you do?

  Added both build.timestamp and lastupdatenanos to a Custom Chart with the Unit set to Duration.

• What did you expect to see?

  The build.timestamp metric should be 10 positive integer digits, representing a Unix timestamp, e.g. 1528682075––which is the behavior of lastupdatenanos.

• What did you see instead?

  build.timestamp is measured in seconds, but is processed as if it were measured in nanoseconds, so it's divided by 1E9, resulting in it displaying only 1 positive integer digit, e.g. 1.5

This issue applies to all metrics that are collected in seconds:

• build.timestamp
• gcbytesage
• intentage
• security.certificate.expiration.ca
• security.certificate.expiration.node
• sys.uptime