[GSoC 20] OpenWISP Monitoring Module

180 views
Skip to first unread message

Hardik Jain

unread,
May 15, 2020, 9:53:08 AM5/15/20
to OpenWISP
11 May, 2020 - 15 May, 2020

PRs Merged :

PRs Open for Review:
Working next on issues:

On a personal note, I learnt many new and exciting things so thanks all the mentors for reviewing my work, pointing to useful resources.
Hope, to keep learning and improving :)

Best Regards,
Hardik Jain
:)

Hardik Jain

unread,
May 22, 2020, 10:30:17 AM5/22/20
to OpenWISP

Hardik Jain

unread,
May 29, 2020, 10:37:41 AM5/29/20
to OpenWISP

Hardik Jain

unread,
Jun 5, 2020, 9:55:01 AM6/5/20
to OpenWISP

Hardik Jain

unread,
Jun 19, 2020, 9:45:43 AM6/19/20
to OpenWISP

Hardik Jain

unread,
Jun 26, 2020, 9:29:27 AM6/26/20
to OpenWISP

Hardik Jain

unread,
Jul 3, 2020, 10:57:31 AM7/3/20
to OpenWISP

Federico Capoano

unread,
Jul 4, 2020, 4:33:17 PM7/4/20
to OpenWISP
I reviewed most PRs, merged what I could.

In the next week we should focus on two things:

1. get what is in the "in-progress" column of the board merged in the dev branch
2. have a call to discuss what is in the "next" column, if you have something ready to show regarding the timeseries DB we can take advantage so you can demo the prototypes by sharing your screen
    we can do this in the second half of the week, please make sure to have something to show, the charts for the ping metric for example.
    at the moment both me and Pablo are leaning towards Elasticsearch. I also have an actual real world installation where we could start using it very soon. 

Best regards
Federico Capoano

--
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 openwisp+u...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/openwisp/b68223dd-2bfe-4608-84bd-cb9267285df3o%40googlegroups.com.

Hardik Jain

unread,
Jul 17, 2020, 10:14:34 AM7/17/20
to OpenWISP
13 July, 2020 - 17 July, 2020

PRs open for review:
    Currently working on:
            Progress so far:
    1. Index Lifecycle Management works perfectly and is much more efficient than Delete by Query 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 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:

    Federico Capoano

    unread,
    Jul 17, 2020, 2:21:09 PM7/17/20
    to OpenWISP
    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.

    --
    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 openwisp+u...@googlegroups.com.

    Hardik Jain

    unread,
    Jul 24, 2020, 11:07:40 AM7/24/20
    to OpenWISP
    20 July, 2020 - 24 July, 2020

    PRs open for review:
    Currently working on:
    Besides tests the elasticsearch client is now fully ready with abstraction complete (optimizations needed).
    * Aggregations have been used prominently to generate chart data.
    * Support for top_fields has been added, had to modify existing structure to make it abstract enough.
    * Tests on travis is currently taking around 80s (corresponding tests on influxdb take place in 25s, so improvement needed).

    Optimizations we can do:
    1) disable _source and _all as we are primarily using aggregations so might not actually need it. Benefits include lesser space being used thus lesser resources consumption as mentioned here (https://www.elastic.co/blog/elasticsearch-as-a-time-series-data-store)
    2) Refresh indices after every write (by default index is refreshed every second, works well in practical case but not during tests.)
    3) Don't delete indices between tests but rather only the data (might save time taken in creation of indexes, putting mappings and templates)

    I did find few more optimizations but we might not be able to use it.
    Maybe we can create a separate issue for this to keep things simple and easier to review :)

    Also, as I put it up yesterday on IM, if mentors are free then we can have a meet sometime early next week, so I can explain the structure  better (Queries, Mappings, Settings, Aggregations, etc. used) and display the prototype (fully integrated now ;) )

    Hardik Jain

    unread,
    Jul 31, 2020, 11:14:39 AM7/31/20
    to OpenWISP

    Hardik Jain

    unread,
    Aug 7, 2020, 10:19:28 AM8/7/20
    to OpenWISP

    Hardik Jain

    unread,
    Aug 14, 2020, 10:46:47 AM8/14/20
    to OpenWISP

    Hardik Jain

    unread,
    Aug 21, 2020, 11:13:38 AM8/21/20
    to OpenWISP

    Hardik Jain

    unread,
    Aug 28, 2020, 10:39:12 AM8/28/20
    to OpenWISP
    24th August, 2020 - 28th August, 2020

    PRs Merged:
      PRs Ready for Review:
      Next:
      Google Summer of Code wraps up this week and it was a very great learning experience for me.
      I think we added some great features to the monitoring module which should be helpful to multiple users.
      Though few improvements as listed in the backlog column and resolving an issue with Elasticsearch (which will be a big add-on)
      remained and I hope to work upon them and continue contributing to OpenWISP and open source in general.

      Thanks a lot Federico, Pablo, Noumbissi, Ajay, Gagan and whoever helped me to improve knowing or unknowingly.
      It wouldn't had been this great a journey without you all 😊.

      Thanks & Regards
      Hardik Jain
      :)

      Hardik Jain

      unread,
      Sep 16, 2020, 11:21:33 AM9/16/20
      to OpenWISP
      Hi everyone,
      I recently shared my experience of working this summer on OpenWISP Monitoring (as a project included in Google Summer of Code) in a medium blog.
      Besides sharing my experience, the blog can act us a guide to all the cool features contained in openwisp-monitoring.

      Regards,
      Hardik Jain
      :)
      Reply all
      Reply to author
      Forward
      0 new messages