What Neo can do with Orion
The node behind a ticket
Find the node by caption, IP address, DNS name, custom property or group, and read its status, polling method and polling engine.
Alerts
Read a node’s active alerts with their severity, trigger time and message, find the alert behind an alert ticket, and acknowledge it, add a note or clear it with the ticket number.
Statistics
Read CPU, memory, disk, interface traffic, response time, application and hardware health, now and over time, to see when a problem started.
Mute and unmanage
Mute a node’s alerts for a change window and unmute it after, or unmanage and remanage a node, interface, volume or application.
Add and remove devices
Add a device to monitoring by ping, SNMP or WMI, let Orion find its interfaces and volumes, set its custom properties and groups, poll it to confirm it answers, and remove a retired device.
Your clients in Orion
Orion has no client object of its own: you mark each node’s client in its caption (such asAcme - Sydney - FW01), in a custom property, or in a group. Neo finds a client’s nodes the same way, so it works with the naming you already use. There is no Organization Mapping tab for Orion.
Credentials stay out of the agent’s context
Neo removes passwords, SNMP communities, keys, tokens and device configuration text from every Orion answer before an agent sees it, and refuses a query that names one of them. A setting stored as a name and a value is read one at a time, and Neo removes the value when its name says it is a credential. Text you typed elsewhere, such as a node’s description or an alert’s message, reaches the agent as written.Next steps
Connect SolarWinds Orion
Publish SWIS to Neo, create an Orion account for Neo, and save it in Neo.
