I tried turning off the node that reports the error and re-running the checks but it reported on a different node which on checking was the master.

I'm leaning towards just ignoring the warning and proceeding but if anyone (from elastic support or otherwise) can clear this up for me I'd be greatful!

---
NEW: Monitor These Apps!
elasticsearch, apache solr, apache hbase, hadoop, redis, casssandra, amazon cloudwatch, mysql, memcached, apache kafka, apache zookeeper, apache storm, ubuntu, centOS, red hat, debian, puppet labs, java, senseiDB