Hit Zabbix API (1.8, 2.0)

I'm not sure if I want to evaluate or criticize it.

What is Zabbix API

Most of the work that can be done on the Web can be done programmatically.

However, not all can be done.

Web items cannot be deleted via the Zabbix API.

Web items are like this (although I haven't researched them yet) https://www.zabbix.com/documentation/2.0/manual/web_monitoring/items

Basically, it seems that the lowest line is that you can add hosts and items for monitoring around numerical values, and you can do that. It seems that it is impossible to steal the UI like a widget gadget.

document

Click here for the official

• 1.8
• 2.0

Here is the stray

• Linkage with external tools using Zabbix API
• I have compiled information for those who are starting Zabbix API

At first glance it seems easy. However, the corner case hurts my head a little.

Basically

Exchange with JSON.

• Define a user who allows API access with Web API
• Get credential by exchanging JSON with that username and password
• Put the credential in JSON and request and get the data on it

It's simple. Of course, JSON runs around the traffic live, so it may be better to make https mandatory in production.

In addition, it is troublesome to build that JSON, so there is a library as it is. In Python, I ported Zabbix API, which is about Ruby. __ Well __

https://github.com/gescheit/scripts/tree/master/zabbix

No, it was mentioned that there are no major ones on the introduction site, and that multiple Zabbix APIs are called. It doesn't seem to be a package level.

Oh, I got a typo

Problems encountered

It is the end of the branches and leaves.

• 1.8 is considered to be in draft stage. I can't complain so much no matter what happens
• API configuration is different between 1.8 and 2.0
• The official documentation is messy. 1.8 is very crude
• Official documentation is a liar
• Totally unfriendly, especially with an error number of 1.8

That said, 1.8 is currently in stable use, so you can expect the API to work reasonably well. It's good!

Specifically, this is the problem

• 1.8 is API version and returns 1.3.
• What is the exact same error message for insufficient arguments and duplicate key_ on the server side (duplicate registration is not possible) ...
• It's amazing that the example in the world says "I feel like I'm crazy even with 2.0!" And the example depends entirely on 1.8 ... (Of course, it doesn't work with 2.0)
• There aren't many examples where everyone is satisfied with the example of getting an item and creating it (this part behaves differently between 1.8 and 2.0).

Postscript: I found this. An example in which the document says that boolean is accepted, but the actual situation is 1/0. It is expected that there are quite a few bugs like this. http://www.zabbix.jp/node/2261

I published an example

https://github.com/dmiyakawa/zabbix_api_examples

I would like to call it a general-purpose library, but first of all, since the main tool is very flexible, there is no point in generalizing it unless the direction is clear, and it is suspicious that there are parts where the architecture is different between 1.8 and 2.0. It seems to be quite difficult considering that the error message, which seems to be the only source of information at the time of the error, is broken at the end. The Zabbix API (Ruby?) Guy is good enough in that sense. There is no point in hiding it anymore. interfaceid or something annoying

Is it better to think of an abstraction level that suits your purpose? Also, I think it's good to have know-how about what individual error messages can actually mean.