Interesting and we'll look at testing that, though we change the metric all the time, and normally need to pull lots of different values - seems here we are limited to the few inventory fields, but still interesting (I assume we can change the mapping and update all the fields).
But even if all are pulled into the inventory, how do I get a report on that field, especially for a group or with a LIKE, with sorts, etc. ? Seems SQL or some API call ?
We just have a full reporting engine connected to Zabbix (we use Scriptcase which is great for this) to pull all this, dozens of queries, reports, etc. that would take 10X the work to use the API.
Note we pull a lot more than this as we have custom GUIs, rule-based processing and ticketing engines, prediction engines on things like disk space, and more, too. Most of these are single host, which is more API friendly, though we've heard the API is slow, so we'll see.
We also have lots of custom SQL update tools, such as proxy migration tools that auto move hundreds of machines in various countries to new proxies due to routing and delays - a few lines of SQL does this easily; probably possible in the API (though without SQL hard to retain the home proxy; I guess we could store it in a profile field, though we use those for many things).
But even if all are pulled into the inventory, how do I get a report on that field, especially for a group or with a LIKE, with sorts, etc. ? Seems SQL or some API call ?
We just have a full reporting engine connected to Zabbix (we use Scriptcase which is great for this) to pull all this, dozens of queries, reports, etc. that would take 10X the work to use the API.
Note we pull a lot more than this as we have custom GUIs, rule-based processing and ticketing engines, prediction engines on things like disk space, and more, too. Most of these are single host, which is more API friendly, though we've heard the API is slow, so we'll see.
We also have lots of custom SQL update tools, such as proxy migration tools that auto move hundreds of machines in various countries to new proxies due to routing and delays - a few lines of SQL does this easily; probably possible in the API (though without SQL hard to retain the home proxy; I guess we could store it in a profile field, though we use those for many things).
Comment