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

Target not updating when adding HTTP operation?

I have added quite a few HTTP operations. Even though I fill out the "target" when creating, once the operation is added, the target field is left blank. This makes it difficult when browsing the numerous HTTP operations. I have attached 2 jpg's showing what I am talking about.

Is there a column in the database that I could select for multiple operations and add the target for them all at once (for each operation)? I have found no way within IP SLAM to modify this once the operation has been created:

sla_no_target_ss.jpg

Find more posts tagged with

Accepted answers

macnugetz

warbird,

Just checking in to see if renaming the operations worked for you.

-Craig

All comments

warbird

Here is the second ss:

sla_no_target_ss1.jpg

macnugetz

warbird,

Although this is technically not a bug, it is confusing. The 'Target' field that is blank in your screenshot actually translates to Target Node. In the case of an HTTP operation, you're targeting a url vs. an actual node, which is why nothing is displayed for this field. You can actually edit the target by editing the operation. Just click on the 'Edit Operation' link that is displayed in your first screenshot.

HTH,

Craig

warbird

Thanks Craig. So what is the easy/nice way to view specific HTTP operations? I feel like I am missing something very simple here. Let's say I want to view all HTTP operations from all of my SLA nodes to http://www.apple.com. What is the best way to go about it?

macnugetz

Are you sure they're not being grouped this way in your second screen shot? I can't tell because the tree isn't fully expanded down to the actual operations (note the '+' signs at the 3rd level down the HTTP tree in your second screen shot). If you expand these out, the operations should be grouped by the target url. I just tested this on my machine and it's working.

-Craig