[ZBX-25458] Escape special caracters in organizations names in organization discovery in Meraki http template Created: 2024 Oct 25 Updated: 2025 Feb 07 Resolved: 2025 Feb 07 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Templates (T) |
Affects Version/s: | 6.0.35, 7.0.5, 7.2.0alpha1 |
Fix Version/s: | 6.0.39rc1, 7.0.10rc1, 7.2.4rc1, 7.4.0alpha1 |
Type: | Problem report | Priority: | Minor |
Reporter: | Andrew Biba | Assignee: | Andrew Biba |
Resolution: | Fixed | Votes: | 1 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified |
Issue Links: |
|
||||
Team: | |||||
Story Points: | 1 |
Description |
Right now special symbols are not escaped in the organization names. In result, discovery fails because organization name writes into hostname witch are not supported any special characters. The most obvious way is to add a code, that would be replacing the special chars in name, but it could be resulting a collision. Second way to change a discovered host name value to something other so avoid using special chars their. for example change the Host name from {#NAME} to meraki-organization-{#ID}. second way seems more stable and preferable Also add filtration of organization on script level to reduce api requests and avoid pulling data about filtered orgs. |
Comments |
Comment by Andrew Biba [ 2025 Feb 04 ] |
Available in:
|