Hi!
Transformation scripts are very flexible - main limitation is what data you can access. First of all, all scripts run in strict sandbox environment, and cannot access any data outside of NetXMS server process. It is also possible to restrict script's access to data of nodes other then current (see http://wiki.netxms.org/wiki/SG:Security_Issues for explanation).
You can collect any data with NetXMS, it just matter of efforts you'll need to get them. There are few possible ways to get data:
1. SNMP - it is here out of the box, you can collect anything provided by SNMP. You can freely add new MIBs, but this is not necessary for data collection - only for MIB tree visualization for seemlier configuration.
2. agent extensions - you can develop your own sub-agents to provide application or device specific data (currently you have to do this in C, but later this year we will introduce support for sub-agents written in Java); if you can get your data with command line tools, you can integrate them into agent as external parameters or external parameter providers.
3. Application agents - we have small and simple "application agent" library which can be embedded into your application and provide internal data to NetXMS agenet.
4. SQL database - with ODBCQUERY sub-agent you can read data directly from SQL database.
We are trying to keep NetXMS as secure as possible. You have very flexible access right control; all access checks done in server, not in GUI nor API, so it's not possible to avoid it by using API directly for example. NetXMS uses own communication protocol, which is encrypted using AES-256 by default. Encryption scheme is pretty much standard - on client connect, server sends it's public RSA key to the client; client generates AES session key and sends it to server encrypted with server's public key. Same protocol used also for server-agent communications.
Best regards,
Victor
Transformation scripts are very flexible - main limitation is what data you can access. First of all, all scripts run in strict sandbox environment, and cannot access any data outside of NetXMS server process. It is also possible to restrict script's access to data of nodes other then current (see http://wiki.netxms.org/wiki/SG:Security_Issues for explanation).
You can collect any data with NetXMS, it just matter of efforts you'll need to get them. There are few possible ways to get data:
1. SNMP - it is here out of the box, you can collect anything provided by SNMP. You can freely add new MIBs, but this is not necessary for data collection - only for MIB tree visualization for seemlier configuration.
2. agent extensions - you can develop your own sub-agents to provide application or device specific data (currently you have to do this in C, but later this year we will introduce support for sub-agents written in Java); if you can get your data with command line tools, you can integrate them into agent as external parameters or external parameter providers.
3. Application agents - we have small and simple "application agent" library which can be embedded into your application and provide internal data to NetXMS agenet.
4. SQL database - with ODBCQUERY sub-agent you can read data directly from SQL database.
We are trying to keep NetXMS as secure as possible. You have very flexible access right control; all access checks done in server, not in GUI nor API, so it's not possible to avoid it by using API directly for example. NetXMS uses own communication protocol, which is encrypted using AES-256 by default. Encryption scheme is pretty much standard - on client connect, server sends it's public RSA key to the client; client generates AES session key and sends it to server encrypted with server's public key. Same protocol used also for server-agent communications.
Best regards,
Victor
