Hi guys,
thank you for a feedback.
My small comments:
About operational data and custom intervals. All these are a Zabbix Server functionality, it is independent on Zabbix Agent features. Unfortunately, I have no control over that.
My Zabbix Agent does not support a scheduled or custom intervals for an active mode (like the new Agent2 is able), but support of these in a passive mode is performed entirely by Zabbix Server.
The only additional note:a custom or scheduled intervals does not cancel the "standard" intervals; so the usual "best practice" is to set a "standard" intervals into zero when you use another type of scheduling.
I'm worry that I do not quite understand the problem with subsystem monitoring. Do you monitor it using the as400.subsystem[...] metric? Do you receive the correct data in the Latest data screen?
What is the problem: incorrect data from the Agent or wrong trigger firing/restore? Could you like, please, provide a bit more details and your trigger formula.
Regarding the errors "MCH2804 not supervised for QGYOLMSG". It is strange for me - probably, there are some factors that I did not take into account.
camiespico, hab, whould you like to provide me a more details, please? Where do you see these errors - in the Agent log file, in the job log, message queue, Zabbix web-interface, other place?
Is the Agent log (usually "zabbix_agentd.log") clear or it contains some warnings/errors?
Does Zabbix Agent restart helps in this situation or not? What will occur if you clone the problem's item (for example, using different number in "maxlines" field)?
Regarding the future plans: I'm not planning any serious changes. The only plans are to publish v0.7.8 that has vary small bug fix and 2 small new features:
thank you for a feedback.
My small comments:
About operational data and custom intervals. All these are a Zabbix Server functionality, it is independent on Zabbix Agent features. Unfortunately, I have no control over that.
My Zabbix Agent does not support a scheduled or custom intervals for an active mode (like the new Agent2 is able), but support of these in a passive mode is performed entirely by Zabbix Server.
The only additional note:a custom or scheduled intervals does not cancel the "standard" intervals; so the usual "best practice" is to set a "standard" intervals into zero when you use another type of scheduling.
I'm worry that I do not quite understand the problem with subsystem monitoring. Do you monitor it using the as400.subsystem[...] metric? Do you receive the correct data in the Latest data screen?
What is the problem: incorrect data from the Agent or wrong trigger firing/restore? Could you like, please, provide a bit more details and your trigger formula.
Regarding the errors "MCH2804 not supervised for QGYOLMSG". It is strange for me - probably, there are some factors that I did not take into account.
camiespico, hab, whould you like to provide me a more details, please? Where do you see these errors - in the Agent log file, in the job log, message queue, Zabbix web-interface, other place?
Is the Agent log (usually "zabbix_agentd.log") clear or it contains some warnings/errors?
Does Zabbix Agent restart helps in this situation or not? What will occur if you clone the problem's item (for example, using different number in "maxlines" field)?
Regarding the future plans: I'm not planning any serious changes. The only plans are to publish v0.7.8 that has vary small bug fix and 2 small new features:
- possibility to monitor the History Log (in the same manner like a Message Queue);
- an additional configuration parameter "as400JobAsMessagePrefix" that allows to use the job name (in format: NUMBER/USER/JOBNAME) as a prefix for the message text.
Comment