On Mon, Nov 13, 2017 at 11:46 PM, QI Fuli <qi.fuli(a)jp.fujitsu.com> wrote:
Hi, here is my second version of nvdimm daemon, It would be
if you could check it.
Change log since v1:
- Adding a config file(/etc/nvdimmd/nvdimmd.conf)
- Using struct log_ctx instead of syslog()
- Using log_syslog() to save the notify messages to syslog
- Using log_file() to save the notify messages to special file
- Adding LOG_NOTICE level into log_priority
- Using automake instead of Makefile
- Adding a new util file(nvdimmd/util.c) including helper functions needed
for nvdimm daemon.
- Adding nvdimmd_test program
This is a patch set of nvdimmd, a tiny daemon to monitor the features of over
threshold events. When an over thershold event fires, nvdimmd will output the
notification including dimm health status to syslog or a special file to
users' configuration. Users can choose the output format to be structured json
Here are out put samples.
- json format:
2017/11/10 11:15:03  log_notify: nvdimm dimm over threshold notify
- text format:
2017/11/10 16:21:53  log_notify: nvdimm dimm over threshold notify
Are these formats that services like Scribe and Fluent can consume?
I'd like to see a sample hook up to those applications.
I'm also wondering that since this will be a long running service that
may gain more functionality over time, if we should write it in a
language that does not have the security sharp edges of C.
I've been looking for an excuse to use the Go language on a project,
and this seems a good opportunity.
- The dimms to monitor should be filtered by namespace and region
Yes, I'd like to make this equivalent to 'ndctl list' in terms filtering.
- Add more information into the notify message
- Make nvdimmd_test an ndctl command or an option of ndctl inject-error
Yes, the test events should originate from "ndctl inject-error".