<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Retention of averaged history data]]></title><description><![CDATA[<p dir="auto">Hello, is there a way to set NetXMS up to do summarization/averageing of historic data? For example, if I collect some data every 60 seconds (polling interval) and save that data for 10 days (retention period), is it possible to also keep hourly averages for 30 days and daily averages for 1 year? The system I am currently using offers option as shown in attached picture.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005125-history.png" alt="history.png" class="img-markdown  img-fluid" width="469" height="188" /></p>
]]></description><link>https://forum.netxms.org/topic/6501/retention-of-averaged-history-data</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 11:11:59 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6501.rss" rel="self" type="application/rss+xml"/><pubDate>Sun, 19 Apr 2020 16:05:07 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to Retention of averaged history data on Thu, 30 Apr 2020 02:10:35 GMT]]></title><description><![CDATA[<p dir="auto">You can build something similar inside NetXMS, but it requires more effort.</p>
<p dir="auto">You could create three DCIs: 60s DCI, 1h DCI, 1d DCI.<br />
The first one is a standard DCI, the other two are script DCIs.<br />
On their poll interval, the scripts DCIs pull the data from the standard DCI and calculate the average (there's a function GetAvgDCIValue that will do that for you).<br />
Set retention as required on each DCI.</p>
<p dir="auto">The result could look something like the attached screenshot (note that I do not have different retention enabled here - if you do, you'd see different part of the graph stop at some point).<br />
It is not quite the same as what you are looking at and it is certainly more complicated to setup than ticking a couple of checkboxes - but it is an option, should you require it.</p>
<hr />
<p dir="auto"><img src="/assets/uploads/files/smf/0000000005137-apcups.png" alt="apcups.png" class="img-markdown  img-fluid" width="1754" height="767" /></p>
]]></description><link>https://forum.netxms.org/post/27800</link><guid isPermaLink="true">https://forum.netxms.org/post/27800</guid><dc:creator><![CDATA[Tursiops]]></dc:creator><pubDate>Thu, 30 Apr 2020 02:10:35 GMT</pubDate></item><item><title><![CDATA[Reply to Retention of averaged history data on Mon, 27 Apr 2020 22:11:23 GMT]]></title><description><![CDATA[<p dir="auto">No such functionality is currently implemented. It could be a valid approach, but such averages tend to look differently then original data - e.g. spikes are smoothed. It could be possible to keep 3 values - min, max and average, but then it complicated the system and requires more development effort.<br />
Since storage is quire cheap these days, a simpler approach is just to store more data - with Postgres time scale DB it's possible to delete old data with minimal load onto the database.</p>
]]></description><link>https://forum.netxms.org/post/27786</link><guid isPermaLink="true">https://forum.netxms.org/post/27786</guid><dc:creator><![CDATA[Filipp Sudanov]]></dc:creator><pubDate>Mon, 27 Apr 2020 22:11:23 GMT</pubDate></item></channel></rss>