-
Notifications
You must be signed in to change notification settings - Fork 34
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
Change name in Zabbix to a description from Netbox #77
Comments
Hi! Can you give an example and some logging? The scenario that you are describing should be fixed with #58 . |
|
Thanks! After looking at it for a 2nd time there are a couple of characters that could be breaking the script. I'll check if i can add this to the list of exceptions, should be a pretty easy fix :) Can you copy / paste the line specifically with the warning message? That will allow me to identify any characters which i did not register in the exceptions list. |
@Winstonshead If you have the time to copy / paste that warning message then that would help me out a lot! Thanks in advance. |
I'll close this issue for now since its getting stale. You can always re-open this issue if you have more information. |
@TheNetworkGuy I'm so sorry, had too many work last time, here it is:
It's log after I renamed "V_Krasnoproletarskaya_9" to "Краснопролетарская 9" |
@Winstonshead No worries, that stuff tends to happen :) Thanks for your reply, i'll push it to the development branch on which i am currently working on! |
Before:
And after:
I just tested this and the host seems to work fine in Zabbix :) I'll post in this issue once the development branch has been pushed to the main branch! :) |
Oh, cool! I will test later, thank you very much |
Greetings!
I want to use some characters in device names in Netbox that cannot be used in host names in Zabbix, so I get an error, eventually the host is not added from Netbox.
I would like Zabbix to take the device description from Netbox and substitute it into the hostname field. How can I do this?
Thanks!
The text was updated successfully, but these errors were encountered: