LiveNX integrates with IT systems, applications and tools to facilitate the creation of automated workflows, comprehensive monitoring, alarm or event correlation for governance across audit, reports and analysis. Integration is provided in several ways including REST APIs, parsed data (e.g. email), SNMP data aggregation, protocol interactions (e.g. PfR), syntax checking, or discovery of assets. The LiveAction API Quick Start Guide provides the initial steps and practices to leverage the open interfaces available in LiveNX.
The total amount of a resource that is defined for use, although may be less than the true maximum capability of resource. Example, the max capacity of an interface to 1Gbps, but only purchased 10% which is 100Mbps, so 100Mbps is the capacity reference for calculation purposes.
Alerts and alarms are somewhat synonymous. The standard term is probably more Alarm. Alert is generated from events and other data that match a particular criteria with certain severity. The alert hits an on condition when triggered and actions such as email, visual notification or even control could be initiated. The alert may at some point turn off if the conditions based on criteria go away.
Alerts should indicate to the user the urgency/severity to act, not just an error but type of error and conditions. Red – Critical Amber/Yellow – Warning Green: Good.
To use the LiveNX REST APIs, an API key is assigned for authentication. This can be accessed through the LiveAction Server Management Console by clicking on the Properties tab.
Discover detailed hardware information, supporting audits of user accounts to find old, unused or unauthorized accounts and remove.
Either sync or async events generated directly from devices or generated from analyzing data from devices
Specific geographic regions at various hierarchical levels
- Continent: North America, South America, Europe, Asia, Australia, Africa
- Region: East Coast U.S.A, West Coast U.S.A
- City: New York, Boston, San Jose
- Site: San Jose Campus
- Building: Bldg 22
REST (REpresentational State Transfer) is an architectural approach to systems integration. Application Programmable Interface is a set of commands that use HTTP requests to GET, PUT, POST and DELETE data. Together REST APIs provide open (documented) communications between different system’s data.
LiveNX displays sites as organization significant locations that may house multiple offices and buildings like a San Francisco campus.
Pub / Sub
The publish-subscribe pattern (pub/sub) is a Ruby on Rails messaging pattern where senders of messages (publishers), do not program the messages to be sent directly to specific receivers (subscribers). LiveNX presents a pub/sub API for integration for identity management, for example.
Swagger is a framework of API developer tools for the OpenAPI Specification(OAS), enabling development across the entire API lifecycle. Swagger is embedded within the LiveNX home page in the top line menu. Swagger within LiveNX contains all LiveNX API references.