On Fri, 15 Sep 2017, Alex Gorbachev wrote: > Hi John, > > > On Fri, Sep 15, 2017 at 2:41 PM, John Spray <jspray@xxxxxxxxxx> wrote: > > On Fri, Sep 15, 2017 at 7:01 PM, Alex Gorbachev <ag@xxxxxxxxxxxxxxxxxxx> wrote: > >> In Jewel and prior there was a health status for MONs in ceph -s JSON > >> output, this seems to be gone now. Is there a place where a status of > >> a given monitor is shown in Luminous? > > > > Can you say which fields specifically you're missing? We still have > > the quorum/quorum_names bits that let you work out whether the mon > > cluster is up by comparison to the mon map. > > Old style: each mon shows if it's OK or not: > > "timechecks": { > "epoch": 968, > "round": 238, > "round_status": "finished", > "mons": [ > { > "name": "lab2-mon1", > "skew": 0.000000, > "latency": 0.000000, > "health": "HEALTH_OK" > }, > { > "name": "lab2-mon2", > "skew": 0.000650, > "latency": 0.000595, > "health": "HEALTH_OK" > }, > { > "name": "lab2-mon3", > "skew": 0.001890, > "latency": 0.000557, > "health": "HEALTH_OK" > } These time checks were moved to the 'ceph time-sync-status' command, which shows similar detail. Note that if there is a skew we also trigger a new-style health warning/error that shows up in ceph health and ceph -s. sage > > > > > > > I think we also used to have the clock skew data there, but I think we > > dropped it because it was kind of an obscure thing and didn't fit > > neatly into the new health checks format. > > > > John > > > >> > >> Thank you > >> -- > >> Alex Gorbachev > >> Storcium > >> _______________________________________________ > >> ceph-users mailing list > >> ceph-users@xxxxxxxxxxxxxx > >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com > -- > To unsubscribe from this list: send the line "unsubscribe ceph-devel" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html > > -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html