Author Topic: Advances and suggestions for reporting and monitorization in eBox  (Read 2326 times)

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1375
  • Karma: +17/-0
    • View Profile
    • Sixstone's blog
Dear community,

As you may know, eBox Technologies is the company behind eBox Platform and eBox Control Center development, the latter being a solution that enables management and monitoring of different eBox servers from a central point. In our aim to provide a series of value added subscription services (to fund eBox Platform development, among other things), we are going to introduce a new service for those who need customized reports and alerts to prevent them from future hassles. We have started off the job as you may see here [1].

However, we would like to improve this service with your help. We believe that the following information could be the most relevant to define how to improve:

  • Knowing which monitoring data is useful for you, for example, the network statistics of your eBox.
  • What are the numbers you look for when you have a report for a service. For instance, in HTTP proxy service, I look for the top blocked domains.
  • We would like to know which service you like to include in reporting and what information you need.

In a nutshell, from what you see in the report file, what information do you miss or is superfluous?

Any other suggestion is welcomed.

We will grant a yearly subscription for eBox Control Center or eBox Reporting Service (according to your interest) to those community members whose contributions we believe having been the most helpful.

Best regards,

[1] http://people.ebox-technologies.com/~quique/reports-128.pdf
My secret is my silence...

Zentyal Cloud Software Architect

alvinquah

  • Zen Warrior
  • ***
  • Posts: 128
  • Karma: +0/-0
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #1 on: March 17, 2010, 04:44:04 »
Hi Sixstone,

how do we configure the report to have top domain visited and blocked like the one you have posted as attachment in this thread? Thanks

dangerbock

  • Zen Apprentice
  • *
  • Posts: 28
  • Karma: +0/-0
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #2 on: March 17, 2010, 10:38:43 »
I don't know if is possible at this time but would be great to have:

- Network traffic/speed/errors on each ETHx and by TAPx
- Network traffic/speed/errors report by time of the day
- Network traffic/speed by Service

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1375
  • Karma: +17/-0
    • View Profile
    • Sixstone's blog
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #3 on: March 17, 2010, 07:06:52 »
how do we configure the report to have top domain visited and blocked like the one you have posted as attachment in this thread? Thanks

Just enable HTTP proxy logs in eBox Platform for a month or so and then run the report from eBox Control Center to group called 'all'.

Cheers,
My secret is my silence...

Zentyal Cloud Software Architect

Saturn2888

  • Zen Hero
  • *****
  • Posts: 707
  • Karma: +1/-0
    • View Profile
I want a fancy looking report that's a page in size I can read or have e-mailed to me. I really care about network traffic used, any problems, which 3 processes used up the most system resource, what the peak load was and why, and maybe something from Traffic Shaping about what it actually did.

Rafael Muylaert

  • Zen Apprentice
  • *
  • Posts: 32
  • Karma: +0/-0
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #5 on: January 11, 2011, 02:36:38 »
I guess SMART monitoring for the hard disks would be important

Escorpiom

  • Board Moderator
  • Zen Hero
  • *****
  • Posts: 664
  • Karma: +16/-1
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #6 on: February 21, 2011, 09:17:55 »
Well, I don't know if this has been brought up already - but for http traffic I monitor the proxy. At this moment it has become a little difficult to monitor because with Dansguardian enabled all traffic is logged as localhost.
I look for users and their habits. I do not restrict bandwidth, but if there are users hogging it all (either http or other services) then this kind of info will be useful.
So in short: Traffic monitor per user based on service.

Cheers.
Marcus' Rule:
Blanks & capitals = avoid it and you'll avoid problems...

c4rdinal

  • Zen Samurai
  • ****
  • Posts: 317
  • Karma: +4/-0
    • View Profile
As admin I'm always looking for the following in info:

Report Details > Host
 - Bandwidth Utilization / Usage Statistics
 - Firewall Detection Events
 - Proxy Filter Statistics (Violations Events, Permitted Site Events)

Report Details > Network
 - Attack Events (Time | Violation ID | User | Server | Port)
 - Bandwidth Utilization / Usage Statistics

jsalamero

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1419
  • Karma: +43/-1
    • View Profile
Most of that information is available on the reports you get from Zentyal Cloud.

graylion

  • Zen Apprentice
  • *
  • Posts: 32
  • Karma: +0/-0
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #9 on: September 23, 2011, 05:33:27 »
IOPS vs max IOPS of storage system

sixstone

  • Zentyal Staff
  • Zen Hero
  • *****
  • Posts: 1375
  • Karma: +17/-0
    • View Profile
    • Sixstone's blog
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #10 on: September 23, 2011, 10:38:45 »
Hi there,

The I/O operations per second graphic is already available using Zentyal Cloud Enterprise subscription.

But thanks for the suggestion!
My secret is my silence...

Zentyal Cloud Software Architect

albatroz

  • Zen Monk
  • **
  • Posts: 68
  • Karma: +1/-0
    • View Profile
Re: Advances and suggestions for reporting and monitorization in eBox
« Reply #11 on: November 09, 2011, 09:59:33 »
Zafa services Dashboard panel
There shoud be a panel in the dashboard that could show if any
of the Zarafa services has stopped. Allowing a restart if necessary.