Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GNIP-68: Monitoring Frontend Analytics #4883

Closed
3 of 5 tasks
allyoucanmap opened this issue Sep 12, 2019 · 7 comments · Fixed by #4885
Closed
3 of 5 tasks

GNIP-68: Monitoring Frontend Analytics #4883

allyoucanmap opened this issue Sep 12, 2019 · 7 comments · Fixed by #4885
Labels
gnip A GeoNodeImprovementProcess Issue
Milestone

Comments

@allyoucanmap
Copy link
Contributor

allyoucanmap commented Sep 12, 2019

GNIP-68: Monitoring Frontend Analytics

Overview

With the improvements done to the Monitoring module backend, have been introduced new metrics and endpoints allowing us to potentially fetch and log seamlessly a lot more information about GeoNode usage.

The old fashioned Monitoring frontend was very limited, reporting just few numbers about hardware statistics and overall requests timings.

What we would like to have, is a brand new interface providing "Google Analytics" like dashboards to the Administrator, in order to have a clear idea about data usage statistics, active sessions and much more information available through the APIs.

E.g.:

image

image

Proposed By

  • Stefano Bovio (GeoSolutions S.A.S.)
  • Giovanni Scardapane (GeoSolutions S.A.S.)

Assigned to Release

This proposal is for GeoNode 2.10.1.

State

  • Under Discussion
  • In Progress
  • Completed
  • Rejected
  • Deferred

Motivation

As said before, we want to:

  1. Improve the old fashioned Monitoring Frontend
  2. Add Analytics stats to the Monitoring info pages

Proposal

The new interface will provide a sidebar with a menu allowing the Admin to easily recognize the Monitoring section

image

The "Monitoring" section will, basically, wrap the old interfaces, improved and adapted to work with the new endpoints

image

image

A new "Analytics" section will be added providing:

  1. Quick overview of the available Resources, along with counters of hits, unique visitors and anonymous sessions toward the selected time period

image

  1. Quick overview of the accessed resources per year

image
image
image
image

  1. Details view allowing to
  • Select the time period of interest

image

  • Report the detailed list of events catched
  • Show the users hits

image

  • Possibility to further filter the details against: Resources, Events

image

Backwards Compatibility

This is not compatible with versions older than 2.10.1.

Future evolution

This new Montoring client will be also a base for further developments and widgets as new endpoints and metrics will be developed on the backend.

Feedback

Voting

Project Steering Committee:

  • Alessio Fabiani: +1
  • Francesco Bartoli: +1
  • Olivier Dalang:
  • Paolo Corti: +1
  • Simone Dalmasso:

Links

@afabiani afabiani added this to the 2.10.1 milestone Sep 12, 2019
gioscarda pushed a commit to gioscarda/geonode that referenced this issue Sep 12, 2019
@t-book
Copy link
Contributor

t-book commented Sep 12, 2019

Thanks, @allyoucanmap looks great. Two comments:

  • Unsure if it's already inbuilt if not: it would be great to support an opt-out cookie for users who do not want to get tracked (GDPR)

  • Also regarding GDPR: When finished it would be nice to update docs / or README which data is tracked by monitoring app and how. (For example, IP Adress with last 3 numbers anonymized, etc.)
    This is the relevant info for all users who are forced to publish a complete privacy policy.

@t-book t-book added the gnip A GeoNodeImprovementProcess Issue label Sep 12, 2019
@afabiani
Copy link
Member

@t-book good catch, but not within this proposal, I would say. Even because only registered user names will be logged, and, in theory, they already accepted the privacy statement.
Moreover, the MONITORING is disabled by default. It must be explicitly enabled by an admin.

Nevertheless, we will envisage how much additional work must should be done to add the cookie or, probably, open a new issue to keep track of this.

@afabiani
Copy link
Member

Adding a bit more on this, for the time being, no private info is stored on the backend. Only counters associated to users sessions. No IP addresses at all.

@capooti
Copy link
Member

capooti commented Sep 12, 2019

+1 thanks!

@t-book
Copy link
Contributor

t-book commented Sep 12, 2019

@afabiani

but not within this proposal,

no worries first things first ;)

my +1 thanks for the great work.

@gannebamm
Copy link
Contributor

I am not part of the PSC but I like the proposal!
+1

afabiani pushed a commit that referenced this issue Sep 13, 2019
[Fixes #4883] monitoring frontend refactoring
@simod
Copy link
Member

simod commented Sep 13, 2019

+1

afabiani pushed a commit that referenced this issue Sep 13, 2019
[Backport 2.10.x] [Fixes #4883] monitoring frontend refactoring
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
gnip A GeoNodeImprovementProcess Issue
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants