Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam. On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu wrote: Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
Ohh, indeed, I didn't noticed it until now, my bad.
Would you consider changing the default from 2 years to something more, like 10 years?
Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default.
Best regards, Tylla
On 2017-12-14 13:32, Adam Armstrong wrote:
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam.
On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Changing that to 10 years would make the RRDs significantly larger, probably. (i'd have to calculate it)
Changing a default like that would need better justification :)
The graph row is the 4 graphs displayed in tables and the like. It displays 4 graphs of day/week/month/year these are hardcoded. The graph browser options are too, but in a different place!
adam. On 2017-12-15 10:37:48, Attila Nagy tylla_at_memetic.org@tylla.hu wrote: Ohh, indeed, I didn't noticed it until now, my bad.
Would you consider changing the default from 2 years to something more, like 10 years?
Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default.
Best regards, Tylla
On 2017-12-14 13:32, Adam Armstrong wrote:
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam. On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu [mailto:tylla_at_memetic.org@tylla.hu] wrote: Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
We have just shy of 4 years of data in some of our RRDs right now. But that's as far back as when we first started using Observium.
According to the defaults.inc.php, the RRDs are scaled for 4 years of history at 1 day resolution.
I'm in an enterprise/government environment and we don't see much value in retaining the data longer than that. It does make some people surprised to see the rate of growth of things (some parts of our service appear to be taking on a logarithmic growth pattern).
However, we already run into problems of devices being upgraded/migrated and losing the historical data if somebody forgets to roll it over. Worse is when say a switch/router port gets repurposed for a new task and suddenly your transit graphs drop off, or increase accordingly... The longer that RRD holds data, the worse this effect will be.
Michael
On 16 Dec 2017, at 1:19 am, Adam Armstrong adama@observium.org wrote:
Changing that to 10 years would make the RRDs significantly larger, probably. (i'd have to calculate it)
Changing a default like that would need better justification :)
The graph row is the 4 graphs displayed in tables and the like. It displays 4 graphs of day/week/month/year these are hardcoded. The graph browser options are too, but in a different place!
adam.
On 2017-12-15 10:37:48, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Ohh, indeed, I didn't noticed it until now, my bad.
Would you consider changing the default from 2 years to something more, like 10 years?
Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default.
Best regards, Tylla
On 2017-12-14 13:32, Adam Armstrong wrote:
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam.
On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
observium mailing list
observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Someone should totally add a "reset RRD" button somewhere...
It is pretty irritating when you lose historical data for devices which are decommissioned/replaced. I tend to rename/disable those devices in the UI but keep them around frozen in time for the historical data.
adam. On 2017-12-16 21:14:51, Michael obslist@smarsz.com wrote: We have just shy of 4 years of data in some of our RRDs right now. But that's as far back as when we first started using Observium.
According to the defaults.inc.php, the RRDs are scaled for 4 years of history at 1 day resolution.
I'm in an enterprise/government environment and we don't see much value in retaining the data longer than that. It does make some people surprised to see the rate of growth of things (some parts of our service appear to be taking on a logarithmic growth pattern).
However, we already run into problems of devices being upgraded/migrated and losing the historical data if somebody forgets to roll it over. Worse is when say a switch/router port gets repurposed for a new task and suddenly your transit graphs drop off, or increase accordingly... The longer that RRD holds data, the worse this effect will be.
Michael
On 16 Dec 2017, at 1:19 am, Adam Armstrong wrote:
Changing that to 10 years would make the RRDs significantly larger, probably. (i'd have to calculate it)
Changing a default like that would need better justification :)
The graph row is the 4 graphs displayed in tables and the like. It displays 4 graphs of day/week/month/year these are hardcoded. The graph browser options are too, but in a different place!
adam.
On 2017-12-15 10:37:48, Attila Nagy wrote:
Ohh, indeed, I didn't noticed it until now, my bad.
Would you consider changing the default from 2 years to something more, like 10 years?
Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default.
Best regards, Tylla
On 2017-12-14 13:32, Adam Armstrong wrote:
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam.
On 2017-12-14 11:35:22, Attila Nagy wrote:
Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
observium mailing list
observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Well, I would say 4 years is kinda OK.
If I understand correctly these values ($config['rrd']['rra']) kick in every time when a new RRD gets created!? So if we're really into keeping long time history, then these values should be changed to whatever we may see fit/feasible and every new RRD would get created with these settings?
Tylla
On 2017-12-16 22:13, Michael wrote:
We have just shy of 4 years of data in some of our RRDs right now. But that's as far back as when we first started using Observium.
According to the defaults.inc.php, the RRDs are scaled for 4 years of history at 1 day resolution.
I'm in an enterprise/government environment and we don't see much value in retaining the data longer than that. It does make some people surprised to see the rate of growth of things (some parts of our service appear to be taking on a logarithmic growth pattern).
However, we already run into problems of devices being upgraded/migrated and losing the historical data if somebody forgets to roll it over. Worse is when say a switch/router port gets repurposed for a new task and suddenly your transit graphs drop off, or increase accordingly... The longer that RRD holds data, the worse this effect will be.
Michael
On 16 Dec 2017, at 1:19 am, Adam Armstrong adama@observium.org wrote:
Changing that to 10 years would make the RRDs significantly larger, probably. (i'd have to calculate it)
Changing a default like that would need better justification :)
The graph row is the 4 graphs displayed in tables and the like. It displays 4 graphs of day/week/month/year these are hardcoded. The graph browser options are too, but in a different place!
adam.
On 2017-12-15 10:37:48, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Ohh, indeed, I didn't noticed it until now, my bad.
Would you consider changing the default from 2 years to something more, like 10 years?
Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default.
Best regards, Tylla
On 2017-12-14 13:32, Adam Armstrong wrote:
The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that.
To see time periods other than the ones shown, you can click on a graph.
The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work.
adam.
On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu wrote:
Hi everyone!
I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years...
It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past.
Regards, Tylla
observium mailing list
observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Yup!
adam. On 2017-12-19 17:35:40, Attila Nagy tylla_at_memetic.org@tylla.hu wrote: Well, I would say 4 years is kinda OK.
If I understand correctly these values ($config['rrd']['rra']) kick in every time when a new RRD gets created!? So if we're really into keeping long time history, then these values should be changed to whatever we may see fit/feasible and every new RRD would get created with these settings?
Tylla
On 2017-12-16 22:13, Michael wrote:
We have just shy of 4 years of data in some of our RRDs right now. But that's as far back as when we first started using Observium. According to the defaults.inc.php, the RRDs are scaled for 4 years of history at 1 day resolution. I'm in an enterprise/government environment and we don't see much value in retaining the data longer than that. It does make some people surprised to see the rate of growth of things (some parts of our service appear to be taking on a logarithmic growth pattern). However, we already run into problems of devices being upgraded/migrated and losing the historical data if somebody forgets to roll it over. Worse is when say a switch/router port gets repurposed for a new task and suddenly your transit graphs drop off, or increase accordingly... The longer that RRD holds data, the worse this effect will be. Michael On 16 Dec 2017, at 1:19 am, Adam Armstrong adama@observium.org [mailto:adama@observium.org] wrote: Changing that to 10 years would make the RRDs significantly larger, probably. (i'd have to calculate it) Changing a default like that would need better justification :) The graph row is the 4 graphs displayed in tables and the like. It displays 4 graphs of day/week/month/year these are hardcoded. The graph browser options are too, but in a different place! adam. On 2017-12-15 10:37:48, Attila Nagy tylla_at_memetic.org@tylla.hu [mailto:tylla_at_memetic.org@tylla.hu] wrote: Ohh, indeed, I didn't noticed it until now, my bad. Would you consider changing the default from 2 years to something more, like 10 years? Under "hardcoded choice" you mean the graph timeline of "6h, 24h, 48h, 1w, 1M, 1Y, 2Y" which gets shown at the top on every graphs details page? If yes, than this would be mostly a cosmetic change, as the most used timespans are already covered and the long term data could be revealed manually. Maybe adding another "10 years" graph would be nice at the end to follow the change in default. Best regards, Tylla On 2017-12-14 13:32, Adam Armstrong wrote: The RRDs hold 2 years, I think. You'd need to recreate them with a different format to change that. To see time periods other than the ones shown, you can click on a graph. The choice of which graphs are displayed on a graph row is currently hardcoded into the code that generates the row, but it could probably be made configurable with a little work. adam. On 2017-12-14 11:35:22, Attila Nagy tylla_at_memetic.org@tylla.hu [mailto:tylla_at_memetic.org@tylla.hu] wrote: Hi everyone! I was wondering about whether there is a recommended/approved/tested/tolerated way or plan of creating multi-year history (RRD data)? To reformulate it, changing the day/week/month/year history into something like day/week/month/year/10years... It's not a show-stopper, but sometimes there is demand to show or analyze historical data for more than 1 year in the past. Regards, Tylla _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium] _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium] _______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
participants (3)
-
Adam Armstrong -
Attila Nagy -
Michael