Zabbix Monitored Item ID Value Pull Request via Service Now API

[Adithiya Sankaran]

Hi Zabbix Community Members,

I'm in the Middle of a Zabbix POC for a Large Environment Monitoring where there will Multiple Zabbix Application Servers & Zabbix Proxy Servers for Monitoring 4000+ Devices Across 4 Data Centres Devices Combinations are Windows(VM + Physical Servers), Linux (VM + Physical Servers), vCenter Servers(ESXi Spread Across Multiple Clusters), Cisco Based Network Devices(Nexus 9000, 5000 & 2000), Fortigate Firewalls and Cisco Catalyst Switches & Routes, Storage Servers(Hitachi G200, HPE 3PAR, IBM A9000R) & FC Storage Switches(Brocade 6510 & 6520, Cisco 9148 SAN Switches As Well). Included Multiple Rack & Blade Servers from Cisco, HPE, Dell EMC, Huawei & Super Micro. Almost I've Onboarded 1000 Devices in Combination of Above all Mentioned. But For Ticketing We've Integrated the Zabbix with Service Now Ticketing & Performance Reporting to our Internal Customers for Validation. The Exact Issue that I'm Currently Facing is The Zabbix Monitored Items Getting Saved with Data Type as Numeric(unsigned) EX: Total RAM, Total CPU etc could not be fetched via Service Now API Call. Where as the other Monitored items like CPU Utilization in % etc are getting saved as Numeric(float) in Zabbix can be pulled via Service Now API Calls. So Exactly What is the Difference Between Numeric(Unsigned) & Numeric(Float).

Why Numeric(unsigned) does not respond to Pull Request in Service Now API? Have Any One Faced This Kind of Issue in Zabbix Integration with Third Party Software like Service Now etc.

[cyber]

It Is Absolutely Horrifying To Read Anything Written In Such Manner....

But maybe you can enlighten us, how SN does that API call? I am pretty sure, Zabbix is not to blame here, but some badly written queries on SN side are probably the issue...

[Adithiya Sankaran]

Hi Cyber, Sorry for the Messy Write Up Earlier and Delayed Response From My End. The Issue Related to the Service Now API is Now Resolved. My Service Now Team Made Changes in the API Method Earlier they Included a Wrong Parameter for Receiving Data via API Instead of Changing it According to the Datatype that Needs to Retrieved they Went with 0(Numeric Float) for All the API Calls Hence Could Not Pull the Data.


{
"jsonrpc": "2.0",
"method": "history.get",
"params": {
"output": "extend",
"history": 0, --- The Changes Needs to be made Here according to the Value Getting Save
"itemids": "42270",
"sortfield": "clock",
"sortorder": "DESC",
"limit": 100
},
"auth": "e1b9b39c6f3405d032244481c48c4e29",
"id": 1
}