PDF Reports

[fjrial]

Hi Luciano,[*]hosts in graphs are not the ones selected

This is happening to me too.. I didn't realized before because I was trying to get a report based on only one host..

I'm on the same opinion of alixen, Thanks for your work, this is a nice and desirable feature, but, nowadays, it's not for production.. I also have a dev-machine with 1.8.2 where I'm testing and will test any version that you do.

[exkg]

Hi Guys,

Sorry about this delay ... we have worked a lot here

So, many tanks to all people that done tests and report something for us.

This version was the very first one and (without doubts) have bugs a lot.

For sure we will work hardly to fix some bugs and to have this feature inside oficial versions.


Tanks all.


[]s,
Luciano

[walterheck]

This looks like a very nice feature, but it really needs to be ported to 1.8.3, any news on progress on that?

With all these great patches lying around that don't get picked up by zabbix, i can't help but wonder how opensource this project actually is

[richlv]

this specific patch is very nice, but it depends on crontab entries.
a "zabbix-way" would be a server scheduled report functionality. but in that case, if it's implemented in the frontend, server would be dependent on the frontend, which is bad. on the other hand, reimplementing graph drawing and other reporting capabilities in the server would be overkill.

so i'd call this case a slight bit of perfectionism coupled with optimal solution searching, which ends up learning from implementations like this patch and - hopefully - coming up with The Solution.

i hope exkg can appreciate (if not understand) these bursts of perfectionism

[walterheck]

Richlv: Thanks for that explanation. It makes a lot of sense what you are saying and I fully agree with your reasoning.

There's just one small problem here: customer demand I think a lot of people here are looking for this functionality, and if we have a vote to ask if a cronjob is an 'accaptable sacrifice' to make in order to have this kind of functionality I know I will vote +1

[alixen]

Hi,

Richlv, since this reporting is based on PHP frontend, it doesn't make sense to use zabbix server for it since it can be on a different server.

Also, we don't need realtime scheduling with 1 second resolution for reports
One minute granularity as provided by cron is more than adequate.
cron is an old and reliable task scheduler, any Unix sysadmin knows it.
So use it, don't try to reinvent the wheel.

It is more important to spend time building a good report generator than a task scheduler.

Regards,
Alixen

[exkg]

So ... my two cents:

We can use ZABBIX Triggers (date and time functions) to schedule this tasks.

Actually we have Maintenance Periods in ZABBIX GUI that already depends on ZABBIX Server ... or am I wrong ?

We can help in 'GUI things' (php, queries, etc), use CRON to trigger scheduled reports, and more. But I agree that we (ZABBIX users) need this feature a lot. And more ... I Think that we can start with a (simple) CRON Job and future more think in better ways.

But ... (always have 'but') we are a little bit confused about how 'Maintenance Periods' works to 'mark' a host/group. We are trying to use same way/method ... but we can't undestand.


[]s,
Luciano

[richlv]

I think a lot of people here are looking for this functionality, and if we have a vote to ask if a cronjob is an 'accaptable sacrifice' to make in order to have this kind of functionality I know I will vote +1

i agree with that... partially
but it is dangerous to forget about long term maintainability and usability. if this feature is implemented, implementation not considered good enough and removed in next version - that would be even worse...

[richlv]

Actually we have Maintenance Periods in ZABBIX GUI that already depends on ZABBIX Server ... or am I wrong ?

depends on what you mean by... depends
pretty much everything that is configured by frontend needs server at some point to work. on the other hand, requiring frontend for the server is not a good thing.

i'm sure there is a good approach to this problem, i'm just not sure what is it

[richlv]

Richlv, since this reporting is based on PHP frontend, it doesn't make sense to use zabbix server for it since it can be on a different server.

this implementation is
the question is whether such an approach is the best

Also, we don't need realtime scheduling with 1 second resolution for reports
One minute granularity as provided by cron is more than adequate.

of course, i completely agree on that.
maybe the answer indeed is to have zabbix frontend automatically configure cron - but that solution has not been implemented yet and shown to work

[alixen]

Hi,

of course, i completely agree on that.
maybe the answer indeed is to have zabbix frontend automatically configure cron - but that solution has not been implemented yet and shown to work

We already do a few modifications in system configuration when Zabbix is installed (/etc/init.d/zabbix*, php.ini,..). Adding a script in /etc/cron.d/ that looks like:

0 * * * * zabbix /usr/bin/zabbix_reports.php

is quite easy.

It would setup a script that is scheduled every hour.
This script will then manage actual scheduling of reports depending on their frequency.

Another solution would be to let zabbix frontend directly manipulate its own crontab via crontab -e command. It will need less development since all actual scheduling will be done by cron but more testing.

Regards,
Alixen

[richlv]

having frontend manage cron entries would be much better, because then it would be both more efficient and flexible. i'd also expect that to be harder to develop properly

[RohrbaGe]

Source code

Hi,

were do I get the source code.
The link is not working anymore


Regards

[exkg]

Oopsss!!!!

It's ok now ... try again


[]s,
Luciano

[RohrbaGe]

The link works now,

but the installation failed.

I get now zabbix page anymore.

I´m running on Suse 11.3 64 bit, Zabbix 1.8.3


I think the install script has run, also the db patch.

Any tip where to search?

Ro