In general /metrics is just a snapshot at that point in time - starting with 3.6, we'll be leveraging prometheus more to collect these metrics for operators. If you are running an alpha / nightly OpenShift cluster on 3.6.0-alpha.2 or later, you can try out the new Prometheus example in github.com/openshift/origin at examples/prometheus/prometheus.yaml. That gathers from nodes and apiservers today - in the future we would like to gather from the controllers and other infrastructure components as well.
On Mon, Jun 26, 2017 at 10:23 PM, Srinivas Naga Kotaru (skotaru) < [email protected]> wrote: > Hi > > > > What is the difference of running a dedicated Prometheus server Vs using > metrics exposed by oc get –raw metrics? If both are same in terms of > accuracy, available information, does it make sense to run again another > Prometheus server and pull cluster metrics? > > > > Am trying to setup some metrics for etcd health and its read, write, > latency, throughput > > > > > > -- > > *Srinivas Kotaru* > > _______________________________________________ > dev mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/dev > >
_______________________________________________ dev mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/dev
