openshift-state-metrics has logic to generate metrics for builds/buildconfigs.  That logic will fail when the buildconfig (or any other collector component for that matter) capability is disabled and the api does not exist.

see:
https://github.com/openshift/openshift-state-metrics/blob/774cb2ff4b9e21c452650643528c6fa190c7885a/main.go#L65-L70
https://github.com/openshift/openshift-state-metrics/blob/774cb2ff4b9e21c452650643528c6fa190c7885a/pkg/collectors/build_config.go#L108-L136
https://github.com/openshift/openshift-state-metrics/blob/774cb2ff4b9e21c452650643528c6fa190c7885a/pkg/collectors/build.go#L175-L188

4.14

always

1.  oc logs -c openshift-state-metrics openshift-state-metrics-8d8965fc7-r6kcz -n openshift-monitoring | grep build.openshift

errors in the openshift state metrics container logs due to non-existent api endpoint

E1012 01:32:59.190721       1 reflector.go:138] github.com/openshift/openshift-state-metrics/pkg/collectors/builder.go:228: Failed to watch *v1.BuildConfig: failed to list *v1.BuildConfig: the server could not find the requested resource (get buildconfigs.build.openshift.io)
E1012 01:33:00.591096       1 reflector.go:138] github.com/openshift/openshift-state-metrics/pkg/collectors/builder.go:228: Failed to watch *v1.Build: failed to list *v1.Build: the server could not find the requested resource (get builds.build.openshift.io)

no errors in the log related to the missing build, buildconfig, or DeploymentConfig APIs