one more issues:
- not evry device has a
lanIP
for example
{'name': NAME', 'serial': '1234567890', 'mac': '50:a3:1e:17:20:11', 'networkId': NETWORKID', 'productType': 'appliance', 'model': 'MX64', 'address': 'Germany, 'lat': 40.2., 'lng': 20.1, 'notes': '', 'tags': [], 'wan1Ip': '192.168.178.20', 'wan2Ip': None, 'configurationUpdatedAt': '2023-03-04T20:43:45Z', 'firmware': 'Not running configured version', 'url': 'https://n229.meraki.com/xxxxxxx'}
this leeds to the traceback
File "/omd/sites/cmk22/local/lib/python3/cmk/special_agents/agent_cisco_meraki.py", line 176, in query
piggyback=str(device[_API_NAME_DEVICE_LAN_IP]),
~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^
_API_NAME_DEVICE_LAN_IP: Final = "lanIp"
- piggyback data by IP-address
not shure if this is a good idea, As mentioned above not every device has a lanIP. The second issue with this, normaly you have the devices inventorized by name not by IP. I am not entierely shure how the piggyback works, but in my case I got a lot of devices by IP address. I think it would be better to use the device name as every system has one. Or make this configurable.
- cisco_meraki_org_device_info works, but wrong path
The device info plugin puts the basic device infos in the inventory. So far so good. but the data belong in my opinion not under -> Software -> Applications but more or less under Hardware.
Here I am missing OrgID/Name and product type. The address (City, ZIP, …) would also be nice here.
A inventory view to search all this data would be nice.