Hello increasingly-active-rsyslog-list! I think we need to decide how to move forward with the testbench, whenever people find the time to work on it. The problem came from comments of this issue: https://github.com/rsyslog/rsyslog/issues/10
(check out the comments after the issue was closed) Basically, the general decision point is to see how we should handle rsyslog's integrations with various data stores. Whether that's Elasticsearch, MongoDB, MySQL, etc. So far, dealing with files was done by... wait for it... writing to actual files. This gets more complicated with DBs because you need to have the DB there. Installing it might take time and tons of dependencies. There are a couple of solutions mentioned in the GitHub issue, but I'm throwing a new one after a bit of thinking. Let's assume that the likes of Elasticsearch are already there, and make a list of "requirements" so that one can see what is assumed. The point is, if you don't have ES installed, you probably don't care about ES tests. So all tests about ES could, for instance, try and do a: curl localhost:9200 And if there's an error, or the version is too old, skip the test and print a warning. What do you think? Other suggestions? Best regards, Radu P.S. The point of starting this thread is, as you might see from GitHub, that I've worked on a few omelasticsearch tests, and I'd like to see what we need in order to get them into the main rsyslog testbench. Blindly assuming ES is there is a bit too much, as Rainer pointed out. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
