-
Notifications
You must be signed in to change notification settings - Fork 72
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
import template on 3.0.4 #5
Comments
Try to change the version in the template from 3.2 to 3.0.4, it should be compatible. |
Hi
I have already fone it but didn't work.
Marco Ferraz
Arquitetura Digital
[email protected]
MOB: 021 989863934
Em 16 de set de 2017 2:16 PM, Long Chen <[email protected]> escreveu:
Try to change the version in the template from 3.2 to 3.0.4, it should be compatible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub<#5 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AeasVrdn1t6n1rzuumuiJyGBkSKXmbJVks5sjAJTgaJpZM4PVI03>.
Esta mensagem, incluindo seus anexos, pode conter informacoes privilegiadas e/ou de carater confidencial, nao podendo ser retransmitida sem autorizacao do remetente. Se voce nao e o destinatario ou pessoa autorizada a recebe-la, informamos que o seu uso, divulgacao, copia ou arquivamento sao proibidos. Portanto, se você recebeu esta mensagem por engano, por favor, nos informe respondendo imediatamente a este e-mail e em seguida apague-a.
|
I had to update my Zabbix system to load this |
I had to remove all , <recovery_mode>, <recovery_expression>, <correlation_mode>, <correlation_tag>, <manual_close> and attributes in trigger definitions to make it import to Zabbix 3.0.11. All these are new features of 3.2 and not compatible with 3.0. |
There is this project that does exists : https://github.com/cavaliercoder/zabbix-template-converter |
Is there a version of template file for Zabbix 3.0.4? I tried to use this version but import function refuse becouse it not recognize the file version.
The text was updated successfully, but these errors were encountered: