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

Calling all feature requests

v9 is barely out the door and in addition to an upcoming service release, we're already gathering requirements for our next feature release of ipMonitor! I've listed several of the core focus areas for us below (based on our prioritization) to help frame your requests.

1. Monitor Support
2. User Interface
3. Reporting
4. Community Integration

Now is the time to submit your top 5 requests in each area! Feel free suggest other focus areas.

Thanks,

-Chris

Find more posts tagged with

Accepted answers

All comments

bleearg13

One thing I've always felt ipMonitor should have is a single-monitor license or perhaps a client app that can be run on a remote machine which will test the availability of your ipMonitor server. This is a nice failsafe option in the event your ipMonitor server dies unexpectedly or loses connectivity. The client app and the full install could basically monitor each other.

Another user mentioned RDP monitoring, which is a great idea, too.

Not sure how you could do any sort of community integration. What are SW's ideas regarding this?

chris.lapoint

One thing I've always felt ipMonitor should have is a single-monitor license or perhaps a client app that can be run on a remote machine which will test the availability of your ipMonitor server. This is a nice failsafe option in the event your ipMonitor server dies unexpectedly or loses connectivity. The client app and the full install could basically monitor each other.

This is a really interesting idea. I'll add this to the list for the next version.

Another user mentioned RDP monitoring, which is a great idea, too.

Can you elaborate further on what you'd expect to see around RDP monitoring?

Not sure how you could do any sort of community integration. What are SW's ideas regarding this?

Here are some of our ideas....would love to get your thoughts on these and if there are others that you'd suggest.

Provide ability to import to and export device templates from Thwack
Provide ability to import to and export SmartGroups from Thwack
Create custom HTML resource in support of Thwack
Create tab for Thwack in product

bleearg13

Another user mentioned RDP monitoring, which is a great idea, too.

Can you elaborate further on what you'd expect to see around RDP monitoring?

That's a pretty good question. Maybe there is some type of login that it can to which will ensure that RDP is responding. Currently, we only monitor the availability of the TCP port, which is not always accurate - similar to how HTTP can be up, but not serving any pages. Maybe the user who posted the original request has some other ideas.

chris.lapoint

Thanks for the additional comments. I'll reply to the original post to see if I can get some more details.

dclick

I actually got a request today to have Orion display, if possible, WHO (what login) is currently using an RDP session. we have seen that sometimes, people may forget they have a RDP session up to a server (or 2 or 3) and when we need to start a session, there are none availble.