-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question on Readme instructions for installation. #4
Comments
Agree, sounds confusing. Yet I always user same user as one running zabbix-agent. |
Great, so is this ok if I skip step 2 and simply use the "zabbix" user ? |
In second step we created zabbix user in web-interface. He will be read data from DB hosts and create items check list in /usr/lib/zabbix/cache/items-*. |
Linux安装的zabbix.3.4.15版本,被监控端必须手动执行py脚本服务端才能展示数据。 |
This is active checks. |
Hello Lelik Thanks |
Unfortunately, I worked for a long time with oracle monitoring. And now I have no opportunity to test the script. |
Check step 7 and 8 - zabbix agent must have checks items:
|
I update the above file like this Please check is this ok? UserParameter=pyora-discovery[],/usr/lib/zabbix/externalscripts/pyora-discovery.py --address '192.168.10.10' $1 --database 'TEST1' $2 $3 |
No. |
it means no need to change any $ values? for your reference |
Yes. |
Hi. |
The period should not be less than 30 seconds because the timer process calculates this function only every 30 seconds. |
What is the zabbix version your using? |
The second step in the installation says: "Create zabbix api user with read permissions on group, where databases hosts will be."
We got confused regarding this zabbix api user, if this user must be created in oracle database we want to monitor or in the server running the scripts. We also don't know what is this "group" that this user must have read permission. Is this api user a simple linux user we must create in the server that holds the agent or another user created in oracle just like in the step 1.
Thanks in advance.
Marcelo.
The text was updated successfully, but these errors were encountered: