|
Duplicate |
Team INT
[ZBX-24055] "HPE Primera by HTTP" template does not use customized port on some items Created: 2024 Feb 07 Updated: 2024 Apr 10 Resolved: 2024 Feb 12 |
|
| Status: | Closed |
| Project: | ZABBIX BUGS AND ISSUES |
| Component/s: | Templates (T) |
| Affects Version/s: | 6.4.11 |
| Fix Version/s: | 6.0.27rc1, 6.4.12rc1, 7.0.0beta2 |
| Type: | Incident report | Priority: | Minor |
| Reporter: | Oleksii Zagorskyi | Assignee: | Denis Rasikhov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Team: | Team INT |
||||
| Story Points: | 0.1 | ||||
| Description |
|
Template "HPE Primera by HTTP" has a macro {$HPE.PRIMERA.API.PORT} which is used by item: "HPE Primera: Service ping" net.tcp.service["{$HPE.PRIMERA.API.SCHEME}","{HOST.CONN}","{$HPE.PRIMERA.API.PORT}"] However the primary Mater item: "HPE Primera: Get data | hpe.primera.get.data" does not include that macro in the parameters for the script which means it's defaulting to (presumably) 443, despite that macro can define another port. Updating the Master item's "base_url" parameter to this (adding :{$HPE.PRIMERA.API.PORT} at the end):
{$HPE.PRIMERA.API.SCHEME}://{HOST.CONN}:{$HPE.PRIMERA.API.PORT}
allowed the item to successfully pull data. |
| Comments |
| Comment by Denis Rasikhov [ 2024 Feb 08 ] |
|
Fixed in:
|