Metric-specific properties (in yaml) are limited to metric_name, instrument, and unit:

We never document the value type (long or float) in yaml or markdown files.

As a result code generation cannot really generate metric definitions and we leave a wiggle room for instrumentation to decide on (and change) the value type.

Also, we manually include requirement level into md.

We should

• extend metric yaml schema to include
  • value type (and make it a part of stability guarantees)
    --requirement level-- moved to Deprecate db.jdbc.driver_classname attribute since it's not used #796
• update existing metric definitions in the spec