Global analytics #2

New Issue

tudor.stanciu · 2022-12-01T01:11:11+02:00

tudor.stanciu commented

2022-12-01 01:11:11 +02:00

Purpose

The purpose of this feature is that an administrator can see the global analytics of the system:

How many requests were made on each route.
How many times a route/application/API has been uniquely accessed.
Where did each request (Country/City) come from. Information is extracted on IP basis: https://ipregistry.co/

On each route/application in Reverse Proxy will be displayed the map with the regions from which it is accessed (similar to Kutt or Umami).

All the development will be configurable:

It will be able to be enabled/disabled globally
Partial elements will be able to be enabled/disabled. Example: Registering only the number of accesses or only the location.

Track

The server will extract and write in the database gross information about requests:
Number of accesses
Client IP
Client browser/device, etc
The API will turn this information into useful data for the user. It will integrate with IPRegistry, will extract data on the location based on the IP, etc, and will serve them towards frontend.
The frontend component will display the analytics in an easy-to-read form only to an user who has enough rights. The other applications in which I have analytics can be used as an inspiration. The simplest are Kutt and Umami.
(Check the kutt-analytics-example.png attachment)

### Purpose The purpose of this feature is that an administrator can see the global analytics of the system: * How many requests were made on each route. * How many times a route/application/API has been uniquely accessed. * Where did each request (Country/City) come from. Information is extracted on IP basis: https://ipregistry.co/ On each route/application in Reverse Proxy will be displayed the map with the regions from which it is accessed (similar to Kutt or Umami). All the development will be configurable: * It will be able to be enabled/disabled globally * Partial elements will be able to be enabled/disabled. Example: Registering only the number of accesses or only the location. ### Track * **The server** will extract and write in the database gross information about requests: * Number of accesses * Client IP * Client browser/device, etc * **The API** will turn this information into useful data for the user. It will integrate with IPRegistry, will extract data on the location based on the IP, etc, and will serve them towards frontend. * **The frontend** component will display the analytics in an easy-to-read form only to an user who has enough rights. The other applications in which I have analytics can be used as an inspiration. The simplest are Kutt and Umami. (Check the kutt-analytics-example.png attachment)

kutt-analytics-example.png

53 KiB

tudor.stanciu added the

enhancement

label 2022-12-01 01:11:11 +02:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: tudor.stanciu/reverse-proxy-frontend#2