| 2014-05-20 11:17:59 |
Gro-Anita Vindheim |
bug |
|
|
added bug |
| 2015-06-10 13:07:34 |
Morten Brekkevold |
nav: importance |
Undecided |
Wishlist |
|
| 2015-06-10 13:07:37 |
Morten Brekkevold |
nav: status |
New |
Triaged |
|
| 2015-06-10 13:07:43 |
Morten Brekkevold |
tags |
|
nav-ref |
|
| 2015-06-10 13:07:57 |
Morten Brekkevold |
tags |
nav-ref |
navref |
|
| 2016-01-12 08:18:27 |
Rune Kittelsen |
bug |
|
|
added subscriber Rune Kittelsen |
| 2016-02-16 12:47:13 |
John-Magne Bredal |
description |
For the wishlist...
Our management often ask for information like
"how many netboxes do we have in our network"
"How many switchports, and how many of those are in use"
"What kind of netboxes do we have, sort by vendor & model"
I would like NAV to save these data as carbon-datapoints.
This will make my management able too see trends without asking me once a month :) |
Because comments can't be edited, I will post the implementation notes above the original request.
This will be implemented as a NAV subsystem. This means that it is
started with the NAV command. The suggested name is 'stats'. The job
itself will run as a cron job.
The code itself will use the 'send_metrics' function to send collected
data to Carbon. This ensures correctness.
To make collection flexible, the collection parameters - what to
collect and where to send it - will be put in a configuration file
called 'stats.conf'. Each collection have a section. Each section has
two required options - the metric path and the SQL to run to get the
metric value to send. The metric timestamp will be fetched when the
metric is sent.
A new metric path prefix is created for these data - nav.stats.
The initial proposal is kinda light on specs but suggested paths for
the wishes are:
- "How many switchports, and how many of those are in use"
- nav.stats.ports.swithcports.active
- nav.stats.ports.switchports.all
- "What kind of netboxes do we have, sort by vendor & model"
- nav.stats.devices.<vendor>.<type>
- "how many netboxes do we have in our network" - sum of the above
Original request follows:
For the wishlist...
Our management often ask for information like
"how many netboxes do we have in our network"
"How many switchports, and how many of those are in use"
"What kind of netboxes do we have, sort by vendor & model"
I would like NAV to save these data as carbon-datapoints.
This will make my management able too see trends without asking me once a month :) |
|
| 2016-02-16 12:48:00 |
John-Magne Bredal |
description |
Because comments can't be edited, I will post the implementation notes above the original request.
This will be implemented as a NAV subsystem. This means that it is
started with the NAV command. The suggested name is 'stats'. The job
itself will run as a cron job.
The code itself will use the 'send_metrics' function to send collected
data to Carbon. This ensures correctness.
To make collection flexible, the collection parameters - what to
collect and where to send it - will be put in a configuration file
called 'stats.conf'. Each collection have a section. Each section has
two required options - the metric path and the SQL to run to get the
metric value to send. The metric timestamp will be fetched when the
metric is sent.
A new metric path prefix is created for these data - nav.stats.
The initial proposal is kinda light on specs but suggested paths for
the wishes are:
- "How many switchports, and how many of those are in use"
- nav.stats.ports.swithcports.active
- nav.stats.ports.switchports.all
- "What kind of netboxes do we have, sort by vendor & model"
- nav.stats.devices.<vendor>.<type>
- "how many netboxes do we have in our network" - sum of the above
Original request follows:
For the wishlist...
Our management often ask for information like
"how many netboxes do we have in our network"
"How many switchports, and how many of those are in use"
"What kind of netboxes do we have, sort by vendor & model"
I would like NAV to save these data as carbon-datapoints.
This will make my management able too see trends without asking me once a month :) |
Because comments can't be edited, I will post the implementation notes above the original request.
This will be implemented as a NAV subsystem. This means that it is
started with the NAV command. The suggested name is 'stats'. The job
itself will run as a cron job.
The code itself will use the 'send_metrics' function to send collected
data to Carbon. This ensures correctness.
To make collection flexible, the collection parameters - what to
collect and where to send it - will be put in a configuration file
called 'stats.conf'. Each collection have a section. Each section has
two required options - the metric path and the SQL to run to get the
metric value to send. The metric timestamp will be fetched when the
metric is sent.
A new metric path prefix is created for these data - nav.stats.
The initial proposal is kinda light on specs but suggested paths for
the wishes are:
- "How many switchports, and how many of those are in use"
- nav.stats.ports.switchports.active
- nav.stats.ports.switchports.all
- "What kind of netboxes do we have, sort by vendor & model"
- nav.stats.devices.<vendor>.<type>
- "how many netboxes do we have in our network" - sum of the above
Original request follows:
For the wishlist...
Our management often ask for information like
"how many netboxes do we have in our network"
"How many switchports, and how many of those are in use"
"What kind of netboxes do we have, sort by vendor & model"
I would like NAV to save these data as carbon-datapoints.
This will make my management able too see trends without asking me once a month :) |
|
| 2016-03-02 13:45:31 |
John-Magne Bredal |
nav: milestone |
|
4.4.3 |
|
| 2016-03-03 07:53:01 |
John-Magne Bredal |
nav: milestone |
4.4.3 |
4.5.0 |
|
| 2016-03-09 07:21:10 |
John-Magne Bredal |
nav: assignee |
|
John-Magne Bredal (john-m-bredal) |
|
| 2016-03-09 07:21:14 |
John-Magne Bredal |
nav: status |
Triaged |
Fix Committed |
|
| 2016-06-09 08:01:15 |
Morten Brekkevold |
summary |
"management statistics" should be implemented |
A new tool for generating Graphite metrics from PostgreSQL queries |
|
| 2016-06-09 10:50:58 |
Morten Brekkevold |
nav: status |
Fix Committed |
Fix Released |
|
