Great report Hardik, informative and brief, thanks. For the record on this list, since we didn't share our thought process here: We definitely want to see Elasticsearch supported as a timeseries DB for openwisp-monitoring, as it should be more practical to use in high-availability setups in which OpenWISP needs to scale horizontally to support more load than influxdb. At the moment influxdb does not have an open source implementation of HA but only a commercial one and we need to find a good open source alternative for the OpenWISP Community to use.
F. On Fri, Jul 17, 2020 at 9:14 AM Hardik Jain <[email protected]> wrote: > *13 July, 2020 - 17 July, 2020* > > *PRs open for review:* > > - [feature] Add Monitoring Checks section in Device Admin > <https://github.com/openwisp/openwisp-monitoring/pull/148> > <https://github.com/openwisp/openwisp-monitoring/pull/162> > - [fix] Create new models Chart, AlertSettings, fixes migrations > <https://github.com/openwisp/openwisp-monitoring/pull/150> > - [feature] Add an Alert Settings section in device admin (blocked by > above PR) <https://github.com/openwisp/openwisp-monitoring/pull/150> > - > [docs] Document metrics stored in influxdb (images need to be updated) > <https://github.com/openwisp/openwisp-monitoring/pull/92> > > *Currently working on:* > > - [timeseries] Add initial support for elasticsearch > <https://github.com/openwisp/openwisp-monitoring/pull/164> > > Progress so far: > > 1. Index Lifecycle Management > > <https://www.elastic.co/guide/en/elasticsearch/reference/master/index-lifecycle-management.html> > works perfectly and is much more efficient than Delete by Query > > <https://www.elastic.co/guide/en/elasticsearch/reference/master/docs-delete-by-query.html> > as it's handled by elasticsearch and we don't need to run a task in the > background. Retention can be done not only on the basis of *time *but > also *size of data* (and of course their combo). We also get multiple > options like shrinking shards, making index read-only, force merge and so > on. I have tested it and it works great. > 2. We also chose *elasticsearch-dsl* over *elasticsearch-sql *for > querying due to current limitations > > <https://www.elastic.co/guide/en/elasticsearch/reference/current/sql-limitations.html> > of the latter (noting for future reference :) ). > 3. The elasticsearch client that can be used in openwisp-monitoring is > almost prepared what remains is *top fields* and *improving queries.* > 4. Besides that some changes would be needed to avoid redundancies in > code thus reducing the number of requests made, new tests and docs. > > *Working next on issue:* > > - [alert settings] Add way to specify global defaults > <https://github.com/openwisp/openwisp-monitoring/issues/106> > > Best regards, > Hardik Jain > :) > >> -- > You received this message because you are subscribed to the Google Groups > "OpenWISP" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web, visit > https://groups.google.com/d/msgid/openwisp/0d7ecaa4-76c3-4530-9a9b-85b8226ffd36n%40googlegroups.com > <https://groups.google.com/d/msgid/openwisp/0d7ecaa4-76c3-4530-9a9b-85b8226ffd36n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- You received this message because you are subscribed to the Google Groups "OpenWISP" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/CAERYH6W8FY8Rf3T-3uT5Eym%2B68AGcbcN5uyZqPjK0O3w7V1_CQ%40mail.gmail.com.
