starred/modoboa-modoboa

Fork 0

mirror of https://github.com/modoboa/modoboa.git synced 2026-04-27 18:05:58 +03:00

[GH-ISSUE #492] drilldown stats interface #475

New issue

Closed

opened 2026-02-27 11:11:57 +03:00 by kerem · 5 comments

kerem commented

2026-02-27 11:11:57 +03:00

Owner

Originally created by @patrickbenkoetter on GitHub (Dec 5, 2013).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/492

The stats interface should have a D3.js (?) enabled drilldown interface.

Originally created by @patrickbenkoetter on GitHub (Dec 5, 2013). Original GitHub issue: https://github.com/modoboa/modoboa/issues/492 The stats interface should have a D3.js (?) enabled drilldown interface.

kerem

2026-02-27 11:11:57 +03:00

closed this issue
added the
enhancement
label

kerem commented

2026-02-27 11:11:58 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 18, 2013):

Good idea. Would you keep using RRDtool? What do people use to store data when they build graphics using D3 ?

@tonioo commented on GitHub (Dec 18, 2013): Good idea. Would you keep using RRDtool? What do people use to store data when they build graphics using D3 ?

kerem commented

2026-02-27 11:11:58 +03:00

Author

Owner

@gleicon commented on GitHub (Dec 18, 2013):

Depends, I've been using redis if the volume is not bigger than half memory. I've worked on a metrics and stats lib in python in case you are looking for an abstraction to percentile and histogram. I can try my hand on it if you dont think the code requires too much modoboa internals knowledge.

On Dec 18, 2013, at 2:33 PM, Antoine Nguyen notifications@github.com wrote:

Good idea. Would you keep using RRDtool? What do people use to store data when they build graphics using D3 ?

—
Reply to this email directly or view it on GitHub.

@gleicon commented on GitHub (Dec 18, 2013): Depends, I've been using redis if the volume is not bigger than half memory. I've worked on a metrics and stats lib in python in case you are looking for an abstraction to percentile and histogram. I can try my hand on it if you dont think the code requires too much modoboa internals knowledge. > On Dec 18, 2013, at 2:33 PM, Antoine Nguyen notifications@github.com wrote: > > Good idea. Would you keep using RRDtool? What do people use to store data when they build graphics using D3 ? > > — > Reply to this email directly or view it on GitHub.

kerem commented

2026-02-27 11:11:58 +03:00

Author

Owner

@tonioo commented on GitHub (Dec 18, 2013):

Indeed, you may need to look a bit at the code before you can modify anything. I'm trying to improve the documentation when I think about it... You can take a look at the stats extension to see how the current graphics are presented.

I was planning to keep RRDtool for storage and just display graphics with D3 using JSON for communication but it may be a bad idea. I see many nosql databases but I just don't know which one would be appropriate. I just want something easy to install, integrate and with good performance.

@tonioo commented on GitHub (Dec 18, 2013): Indeed, you may need to look a bit at the code before you can modify anything. I'm trying to improve the documentation when I think about it... You can take a look at the stats extension to see how the current graphics are presented. I was planning to keep RRDtool for storage and just display graphics with D3 using JSON for communication but it may be a bad idea. I see many nosql databases but I just don't know which one would be appropriate. I just want something easy to install, integrate and with good performance.

kerem commented

2026-02-27 11:11:58 +03:00

Author

Owner

@gleicon commented on GitHub (Dec 18, 2013):

This is project I was talking about:

https://github.com/gleicon/pymetrics

In theory you could use any key/value storage to persist this data or keep it on rrd as you said. It depends on how this data grows overtime.

I've just picked redis b/c it has native data types as lists and scored sets, which helped to port my library from in memory python data types.

On Dec 18, 2013, at 7:08 PM, Antoine Nguyen notifications@github.com wrote:

Indeed, you may need to look a bit at the code before you can modify anything. I'm trying to improve the documentation when I think about it... You can take a look at the stats extension to see how the current graphics are presented.

I was planning to keep RRDtool for storage and just display graphics with D3 using JSON for communication but it may be a bad idea. I see many nosql databases but I just don't know which one would be appropriate. I just want something easy to install, integrate and with good performance.

—
Reply to this email directly or view it on GitHub.

@gleicon commented on GitHub (Dec 18, 2013): This is project I was talking about: https://github.com/gleicon/pymetrics In theory you could use any key/value storage to persist this data or keep it on rrd as you said. It depends on how this data grows overtime. I've just picked redis b/c it has native data types as lists and scored sets, which helped to port my library from in memory python data types. > On Dec 18, 2013, at 7:08 PM, Antoine Nguyen notifications@github.com wrote: > > Indeed, you may need to look a bit at the code before you can modify anything. I'm trying to improve the documentation when I think about it... You can take a look at the stats extension to see how the current graphics are presented. > > I was planning to keep RRDtool for storage and just display graphics with D3 using JSON for communication but it may be a bad idea. I see many nosql databases but I just don't know which one would be appropriate. I just want something easy to install, integrate and with good performance. > > — > Reply to this email directly or view it on GitHub.

kerem commented

2026-02-27 11:11:58 +03:00

Author

Owner

@tonioo commented on GitHub (Jan 24, 2014):

I think we could handle this feature in two steps:

Create a d3.js (or something else) frontend to display graphics and keep the RRD files (we can use the JSON export feature) because some installations may have a long historic and I don't want to deal with the migration yet
Replace RRD files with a custom storage engine (Redis or other)

The truth is I'm totally unfamiliar with d3.js (or more generally, frontends to display such graphics) and I would really appreciate some help.

Do you know someone? :)

@tonioo commented on GitHub (Jan 24, 2014): I think we could handle this feature in two steps: - Create a d3.js (or something else) frontend to display graphics and keep the RRD files (we can use the JSON export feature) because some installations may have a long historic and I don't want to deal with the migration yet - Replace RRD files with a custom storage engine (Redis or other) The truth is I'm totally unfamiliar with d3.js (or more generally, frontends to display such graphics) and I would really appreciate some help. Do you know someone? :)