Here are the ideas we've heard from customers on what they'd like to see wrt/ Orion and Cirrus integration once Cirrus has its own website: * Allow users the ability to easily move between Orion Node Details and Cirrus Node Details views * Add a Cirrus "tab" to Orion website to allow easy navigation to Cirrus website * Provide Orion users the ability to leverage a Cirrus Node Details resource on the Orion Node Details view If you have other requests or would prioritize these differently, please let us know! We're especially interested in what you'd like to see for #3.

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Cirrus-Orion Integration Ideas

Here are the ideas we've heard from customers on what they'd like to see wrt/ Orion and Cirrus integration once Cirrus has its own website:

Allow users the ability to easily move between Orion Node Details and Cirrus Node Details views
Add a Cirrus "tab" to Orion website to allow easy navigation to Cirrus website
Provide Orion users the ability to leverage a Cirrus Node Details resource on the Orion Node Details view

If you have other requests or would prioritize these differently, please let us know! We're especially interested in what you'd like to see for #3.

Find more posts tagged with

Accepted answers

All comments

savell

Hi Chris - thanks for the opportunity to contribute idea's.

Adding a Cirrus tab would be great - preferably with an option to authorize via the existing Orion security attributes (as per the the existing modules). Given the need to accommodate stand-alone users however - this may be tricky.

As per #3, I would like to get access to the device configuration history from the Orion Node Details View. Being able to invoke a compare (i.e current running with last version) without having to enter Cirrus would be an added bonus.

Dave.

SamuelB

With a Cirrus-Orion Integration, I would like the option of the following resources when I view the Orion Node Details for a node.

* A resource that shows the scheduled jobs for that node

* A resource that shows the output of one or more "show" commands for the node (Ability to run a show command and save it in the database needs to be implemented first before this can work)

* A resource for Switch nodes that shows the MAC/IP address that is connected to each port

* A resource that allows for config comparison for the node.

I know that some of these requests will require some further work on Cirrus before the integration can even begin, but that is what I would like to see. I also realize that you need to support users that have a stand alone Cirrus installation, however, my integration dream is that most information about a node could be found on the Node Details page in Orion by adding resources to the page, while the items that don't pertain to a node would be on the Cirrus tab (but that page would also allow resources to be added to look more like a stand alone installation if someone desired).

jonchill

Very much along the same lines as Samuel.

The extra tab would be great but having Node specific details such as latest config and running show commands and interface specific details of MAC\IP\Device name would be perfect.

Thanks

amm_orion

* A resource that shows the output of one or more "show" commands for the node (Ability to run a show command and save it in the database needs to be implemented first before this can work)
* A resource for Switch nodes that shows the MAC/IP address that is connected to each port
* A resource that allows for config comparison for the node.

I agree with these, and especially would like to see the MAC & IP address connected to each port! I just want to easily see Cirrus details from Orion.. Thanks!

I would like to see a function that would configure cirrus and orion to share the same node database. This may be difficult to juggle around, but the fact remains that I have multiple places to edit nodes and there shouldn't be that requirement.

At the very minimum, the sysname, ip, and node ID should match between cirrus and orion.

-JP

SamuelB

* A resource that shows the output of one or more "show" commands for the node (Ability to run a show command and save it in the database needs to be implemented first before this can work)

To think this resource out ever further, it would be nice for the resource to be just a list of (configurable) show commands like this:

show ip interface brief

show version

show processes cpu

Then once the mouse is moved over the command, an AJAX style window pops up and shows the output of that command. This would potentially provide a lot of information on the Node Details page without taking up too much real estate on the screen.

This AJAX style popup window idea could be used for other resources I listed above too, but the show command resource is a good example.

jlgugler

I want to share the custom properties of nodes between Cirrus and Orion ! Have the same tools for merge repport !