On Mon, Jul 23, 2018 at 8:24 PM, Maarten van Baarsel <mrten_glusterusers@xxxxx> wrote: > On 23/07/18 16:03, Pranith Kumar Karampuri wrote: > >> We want gluster's monitoring/observability to be as easy as possible going >> forward. As part of reaching this goal we are starting this initiative to >> add improvements to existing apis/commands and create new apis/commands to >> gluster so that the admin can integrate it with whichever monitoring tool >> he/she likes. The gluster-prometheus project hosted at >> https://github.com/gluster/gluster-prometheus is the direction in which we >> feel metrics can be collected and distributed from a Gluster cluster >> enabling analysis and visualization. >> >> >> As a first step we want to hear from you what you feel needs to be >> addressed. > > > Regarding monitoring; I would love to see in my monitoring that > geo-replication is working as intended; at the moment I'm faking georep > monitoring by having a process touch a file (every server involved in > gluster touches another file) on every volume and checking mtime on the > slave. > I'd like to request that if possible, you elaborate on how you'd like to see the "as intended" situation. What kind of data points and/or visualization would aid you in arriving at that conclusion? _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
