Report plugin ''ReportIt" - v0.7.5a (released 23/12/11)

[browniebraun]

Nope, email support does only work for scheduled reports.
Is there a need for changing that?

Best regards
-Andreas-

[cspenpen]

Nope, email support does only work for scheduled reports.
Is there a need for changing that?

Best regards
-Andreas-

no, I just want to quickly to know what is the email content look like.
this is great plugin ! later days I'll share my template.

thanks again!

[cspenpen]

nothing..
sorry

[GlueGuy]

We've been using reportit for some time quite successfully. Perhaps too successfully. Thank you Andreas for such a great tool!

We have some 80 reports running now. Most are daily, with a few running weekly, and one or two running monthly. Our daily reports start at 5AM, and we have begun to notice that it impacts our RRD collection on the same server.

What we see is that from ~~ 5AM, until the daily reports finish that our RRD data collection is at least partially impacted; as some RRD data has "holes" in it during the report run (we are now doing something like 5,000 RRD files).

What is the suggested way to reduce this impact, as the amount of time that the reports take is unimportant relative to actually collecting the data?

Is there (perhaps) a way to "serialize" the reports such that only one runs at a time? Or is there a good way to reduce the priority of the reports so that RRDTOOL can not be interrupted?

[TheWitness]

We've been using reportit for some time quite successfully. Perhaps too successfully. Thank you Andreas for such a great tool!

We have some 80 reports running now. Most are daily, with a few running weekly, and one or two running monthly. Our daily reports start at 5AM, and we have begun to notice that it impacts our RRD collection on the same server.

What we see is that from ~~ 5AM, until the daily reports finish that our RRD data collection is at least partially impacted; as some RRD data has "holes" in it during the report run (we are now doing something like 5,000 RRD files).

What is the suggested way to reduce this impact, as the amount of time that the reports take is unimportant relative to actually collecting the data?

Is there (perhaps) a way to "serialize" the reports such that only one runs at a time? Or is there a good way to reduce the priority of the reports so that RRDTOOL can not be interrupted?

So, I've not used the plugin, but was planning on becoming familiar. Are you saying that the reports all fan out at once? Please confirm...

TheWitness

[TheWitness]

Nope, not parallel. However, you may be having other issues (memory / diskI/O) maybe...

[browniebraun]

Right.
ReportIt calculates everything in sequence.
By doing so, it will utilize one CPU core up to 100% for a short moment.

Regards
-Andi-

[suryantoro]

Hi,

Is it possible to run v0.7.2 on mysql 4.1.11-2 ?
Please advice.

Thanks in advance.

[manaf]

hello,
I have upgraded reportit plugin to v0.7.2 but I have a problem.
I see empty value when I try to generate report
what could be the problem?

[browniebraun]

Hi,

Is it possible to run v0.7.2 on mysql 4.1.11-2 ?
Please advice.

Thanks in advance.

I'm sorry, but MySQL 4 will no longer supported.

Best regards
-Andreas-

[browniebraun]

hello,
I have upgraded reportit plugin to v0.7.2 but I have a problem.
I see empty value when I try to generate report
what could be the problem?

Execute following commands using the MySQL CLI or e.g. phpMyAdmin:

Code: Select all

ALTER TABLE `reportit_measurands`
            ADD `data_type` SMALLINT NOT NULL DEFAULT '1',
            ADD `data_precision` SMALLINT NOT NULL DEFAULT '2';
ALTER TABLE `reportit_cache_measurands`
            ADD `data_type` SMALLINT NOT NULL DEFAULT '1',
            ADD `data_precision` SMALLINT NOT NULL DEFAULT '2';

Best regards
-Andreas-

[manaf]

hello,
I have upgraded reportit plugin to v0.7.2 but I have a problem.
I see empty value when I try to generate report
what could be the problem?

Execute following commands using the MySQL CLI or e.g. phpMyAdmin:

Code: Select all

ALTER TABLE `reportit_measurands`
            ADD `data_type` SMALLINT NOT NULL DEFAULT '1',
            ADD `data_precision` SMALLINT NOT NULL DEFAULT '2';
ALTER TABLE `reportit_cache_measurands`
            ADD `data_type` SMALLINT NOT NULL DEFAULT '1',
            ADD `data_precision` SMALLINT NOT NULL DEFAULT '2';

Best regards
-Andreas-

Everything is working fine now
Thank you

[suryantoro]

Okay, Thanks for the info.

[mens]

I just submitted a patch (against 0.7.2) on the sourceforge tracker page that allows multiple users (but not public) to access a page. It is based on the network-weathermap plugin.
details can be found here.

Comments are welcome

[GlueGuy]

Nope, not parallel. However, you may be having other issues (memory / diskI/O) maybe...

Perhaps. But it was impossible to tell. When the problem happens, even the SNMP polls to the server itself (localhost) would have gaps in the RRD data.

I changed the reportit cron job to run under "nice 10", which reduced the priority, and it seems to have mitigated the problem somewhat. The command is now:

nice -n 10 /usr/bin/php /var/www/html/plugins/reportit/runtime.php -d > /dev/null 2>&1

I still see the gaps in the graphs, but they are shorter duration.

I am now able to see what the load looks like. Backup starts at 1AM, then yum at 2AM. The reportit reports start at 5AM, and it looks like it increases the load significantly.