Hi,
Looking at Zabbix for a major institution, however I see that it needs a few new features before we can use it. I'm interested in developing those new features but I would like to know how you core zabbix developers what this type of development.
What I'm looking at are dynamic tables, lots of snmp and other statistics too are table based and change dynamically. Look at the process table, or file system mount table, network interface tabel etc..
We need a way to gather data and select data with in that set dynamically.
Like this:
Network interface table -> consist of one or more rows of: interface name, mac address, ip address, packages sent, packages recived, mtu .... and so forth and so on..
What we need is to be able to spec, the table and then collect all the data that that table has furthermore if the number of rows goes up or down we need to either stop or start collecting data for that row. Like if we add a new disk on a client well then we automatically need to collect data for that disk.
I envision this as snmp to begin with, that we give a table OID and that we collect all the data for that table. That we later on select what rows to graph or alert on.
The question to the zabbix devloper is how they want to spec a table, how do they want to collect the data, and how do they want to feed that data into the DB? I can go a head and do this all by my self but I rather want to know how you want this done.. i.e. the flow of data and how you want it arranged in the DB..
Cheers O
Looking at Zabbix for a major institution, however I see that it needs a few new features before we can use it. I'm interested in developing those new features but I would like to know how you core zabbix developers what this type of development.
What I'm looking at are dynamic tables, lots of snmp and other statistics too are table based and change dynamically. Look at the process table, or file system mount table, network interface tabel etc..
We need a way to gather data and select data with in that set dynamically.
Like this:
Network interface table -> consist of one or more rows of: interface name, mac address, ip address, packages sent, packages recived, mtu .... and so forth and so on..
What we need is to be able to spec, the table and then collect all the data that that table has furthermore if the number of rows goes up or down we need to either stop or start collecting data for that row. Like if we add a new disk on a client well then we automatically need to collect data for that disk.
I envision this as snmp to begin with, that we give a table OID and that we collect all the data for that table. That we later on select what rows to graph or alert on.
The question to the zabbix devloper is how they want to spec a table, how do they want to collect the data, and how do they want to feed that data into the DB? I can go a head and do this all by my self but I rather want to know how you want this done.. i.e. the flow of data and how you want it arranged in the DB..
Cheers O
Comment