REPO:
CMK-exchange/special_agents/ExtremeCloud-XIQ at main · bh2005/CMK-exchange
agent_xiq
Short Description
Special Agent for ExtremeCloudIQ (XIQ). Fetches devices, radio information, and
neighbors; prints summary and inventory sections on the main host; piggybacks
per-AP sections for APs managed by XIQ.
Installation
simple as mkp
Printed Sections
On the main host (H1):
<<<extreme_cloud_iq_login>>><<<extreme_cloud_iq_rate_limits:sep(124)>>><<<extreme_summary:sep(124)>>><<<extreme_device_inventory:sep(124)>>><<<extreme_device_neighbors:sep(124)>>>
On each AP piggyback host:
<<<extreme_ap_status:sep(124)>>><<<extreme_ap_clients:sep(124)>>><<<extreme_ap_neighbors:sep(124)>>><<<xiq_radio_information:json>>>
Piggyback Scope
Piggyback is emitted only for devices where:
device_function == "AP" AND managed_by == "XIQ"
(Currently filtered to connected APs.)
Token Cache & Rate Limits
- Access token cached for 1 hour under:
$OMD_ROOT/var/check_mk/special_agents/xiq/<main-host>.json - Re-login on
401responses - Backoff on
429(rate limiting) and rate-limit header extraction printed to section
Required Rule / Call Example
Setup → Agents → Other Integrations to invoke:
.. code-block:: bash
$HOME/local/lib/python3/cmk_addons/plugins/xiq/libexec/agent_xiq
–url “https://api.extremecloudiq.com”
–username “” --password “”
–host “”
–timeout 30
–proxy “http://proxy:8080”
–no-cert-check
Notes
- Ensure Python
requestsis available in the site environment. - If you see literal
<<<markers in the source you copied, make sure the final file contains plain ASCII markers<<<. - For piggyback hosts, make sure Piggyback data is enabled and hosts are created or auto-discovered.
- CEE only use DCD for Piggyback Hosts
What still needs to be done:
- Make expenses more consistent.
- Switch expenses to English.
- Create checkmans
and whatever other errors you find
(you can even keep those—free of charge 
or write me a PM ),
e.g., functions or checks that should be added.
Greetz Bernd
