Hi Vasiliy, > Chassis info missed encap (useful) and options (may be useful).
Good point! Will add. > Also pid file and log file path not useful (i don't understand how this use > in monitoring), Here is the thinking on this one. The presence of pid file and the validation that the process listed in the pid file are process checks. If the process is 0, then it is down and one can monitor for that. Also, if the process ID of a subsystem (say OVN NB) changed, then it means that service was restarted. I guess the alert would be if a process is 0 or if the process ID changed, then alert. Per the log files. It happened on a number of occasions that a subsystem crashed, but its process was still running. One way of detecting something like that is watch for the log file being stale, i.e. log size does not increment. There are obviously other ways to monitor that. Also, any spike in log activity, i.e. sudden large increase in log file size, means something is happening and it worth looking into it. > also system run dir. May be to monitor disk space, but i'm confused. That's really informational. Kinda know where system dir is. Regards, Paul From: Vasiliy Tolstov <[email protected]> Sent: Wednesday, October 3, 2018 7:20 AM To: [email protected] Cc: Василий Толстов; [email protected] Subject: Re: [ovs-discuss] Prometheus Exporter for OVN ср, 3 окт. 2018 г. в 2:35, Paul Greenberg <[email protected]>: > > Hi Vasiliy, > > Thank you for the reply! I will take the conversation about the modifications > you mentioned into the repo. > > > I'm already have such splitting for libvirt exporter. > > Do you have the code published somewhere? Yes, post link to repo issue. > > What metrics do you consider the most valuable when it comes to OVN (not > OVS)? Are they implemented? > Chassis info missed encap (useful) and options (may be useful). Also pid file and log file path not useful (i don't understand how this use in monitoring), also system run dir. May be to monitor disk space, but i'm confused. -- Vasiliy Tolstov, e-mail: [email protected] _______________________________________________ discuss mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-discuss
