In collector/corosync/parser.go line 154
There is a bug in the regexp when parsing corosync-cfgtool -s output:
re := regexp.MustCompile(`(?m)(?P<prefix>RING|Link) ID (?P<number>\d+)\s+(?P<id>id|addr) \s*= (?P<address>.+)\s+status \s*= (?P<status>.+)`)
corosync-cfgtool outputs a tab character after "id" and "status", so the regexp with an additional space after id/status will not match. Without the spaces in front of "\s" the regexp will work.
...(?P<id>id|addr)\s*= (?P<address>.+)\s+status\s*=...
In collector/corosync/parser.go line 154 There is a bug in the regexp when parsing corosync-cfgtool -s output:
re := regexp.MustCompile(`(?m)(?P<prefix>RING|Link) ID (?P<number>\d+)\s+(?P<id>id|addr) \s*= (?P<address>.+)\s+status \s*= (?P<status>.+)`)
corosync-cfgtool outputs a tab character after "id" and "status", so the regexp with an additional space after id/status will not match. Without the spaces in front of "\s" the regexp will work....(?P<id>id|addr)\s*= (?P<address>.+)\s+status\s*=...