NetCrunchをヘルプデスクやその他の生産性ツールなどのさまざまなサードパーティサービスと統合します。 このモジュールを利用することで、NetCrunchを他のNMSなどと連帯させることも可能となります。
このモジュールは次の製品でご利用可能です。:
このモジュールは他の全てのNetCrunchプラットフォーム製品に追加いただけます。
IT is complex and consist of many different elements. As the system evolves over time, it is hard to rely on a single vendor. We understand that the best way is to connect services in such a way that makes it work smoothly even when each part comes from a different vendor.
This trend becomes more important in cloud times where we perceive the computing as multiple dislocated services.
Each integration requires defining its profile, where usually you need to add an API key/token for the external system.
This simple notification can send a proper notification to the external system.
Supported systems:
Because these systems send data to NetCrunch, you have to create an API key for the integration to use it to send a message back to NetCrunch. The URL to send data into NetCrunch will look as follows
http://<nc-server-address>/api/rest/1/integration/<api-key>
NetCrunch can accept messages from:
The export feature takes all the hassle of writing a code to access data API.
The exporter can get trend data from NetCrunch Server and push it to designated SQL database. It can help you create a custom report or custom data analysis.
You can schedule trends export to be performed periodically. In order to set it, go to Tools > Options > General and enableAdvanced Options. Then you will be able to enable trend export and configure the schedule.
You can also export data on demand for a quick analysis
In both cases, you have to use right click menu and select Trend Export
NetCrunch allows you to forward all received traps and syslog messages to another monitoring program. It significantly reduces trap configuration hassle as you need to configure sending traps only to NetCrunch.
The program also allows you to forward SNMPv3 notifications, but it requires a profile to be set first.
You can enable this option in the program Tools > Options.
NetCrunch offers ODBC driver to access SQL event database. Since NetCrunch works as the system process, you need to create the system DSN to access the database.
NetCrunch sends SNMP trap as the response for an alert. In such case, you might need MIB modules to let other NMS understand all alert parameters.
This function is available from the top menu Atlas > Export NetCrunch SNMP MIB.
You have to export the MIB after adding any new alert definitions to NetCrunch.
It is possible to upstream live NetCrunch data to big data (Cassandra, Splunk) or cloud databases. The project is currently in the research and development phase.
Let us know if you are interested in beta testing.