If we had a photograph of every network room or node and could display it easily in NPM's view for a node we would have better information when remotely troubleshooting an issue. A photograph associated to nodes or network rooms would simplify: Coaching a technician via telephone to: View the right hardware in a rack Plug/unplug the right network connection in a node Reboot the right node in a rack Prioritizing network rooms for patch management / clean up Understanding available space in a rack or a room Remembering power outlet limitations Analyzing UPS status Have any of you found an easy way to automatically associate a photograph with a Node and insert it into NPM's view of that Node? I'm guessing that answer is "no". How about have you found an easy way to add a photograph to node's view? If so, how? Swift packets to those who have helpful experiences and advice! As for the rest of you . . . aw, OK, swift packets for you & your customers, too. ;^) Rick Schroeder

I've done it in the past. Client was an MSP who took photos of each of the locations they supported to document where the physical assets were in the building. We created a directory inside inetpub/solarwinds/orion/images/ and loaded all their images into it. Renamed the image files themselves with a naming convention that was basically <siteid>01.jpg through 10.jpg, created a new tab on the node details that just held 10 "custom html" widgets with contents like <img src="/orion/images/${siteid}01.jpg"> and that worked to get each node ready to display any images we had for the site. In the case that rschroeder has where you would want a 1 to 1 relationship then you would probably want to use the ${nodeid} variable and yes, it will be a chore to rename each image file based on the nodeid, but I can't think of any solution where there wouldn't have to be some kind of manual data entry process to correlate each image. What information do you currently have that keeps track of all these images to begin with?

This discussion has been locked. The information referenced herein may be inaccurate due to age, software updates, or external references.

You can no longer post new replies to this discussion. If you have a similar question you can start a new discussion in this forum.

Adding one or more photographs to NPM node views?

rschroeder over 5 years ago

If we had a photograph of every network room or node and could display it easily in NPM's view for a node we would have better information when remotely troubleshooting an issue.

A photograph associated to nodes or network rooms would simplify:

Coaching a technician via telephone to:
- View the right hardware in a rack
- Plug/unplug the right network connection in a node
- Reboot the right node in a rack
Prioritizing network rooms for patch management / clean up
Understanding available space in a rack or a room
Remembering power outlet limitations
Analyzing UPS status

Have any of you found an easy way to automatically associate a photograph with a Node and insert it into NPM's view of that Node?

I'm guessing that answer is "no".

How about have you found an easy way to add a photograph to node's view?

If so, how?

Swift packets to those who have helpful experiences and advice!

As for the rest of you . . . aw, OK, swift packets for you & your customers, too. ;^)

Rick Schroeder

Top Replies

Parents

0 hpstech over 5 years ago

Embed an HTML widget with an <img> link of the device in the Node details view, coded to specially select the image based on Node details name using encoded URL query string parameters.
I can see it, but can't do it. Hey, like Steve Jobs. The smart people can do it for sure though.
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 hpstech over 5 years ago

Embed an HTML widget with an <img> link of the device in the Node details view, coded to specially select the image based on Node details name using encoded URL query string parameters.
I can see it, but can't do it. Hey, like Steve Jobs. The smart people can do it for sure though.
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 mesverrum over 5 years ago in reply to hpstech

I've done it in the past. Client was an MSP who took photos of each of the locations they supported to document where the physical assets were in the building. We created a directory inside inetpub/solarwinds/orion/images/ and loaded all their images into it. Renamed the image files themselves with a naming convention that was basically <siteid>01.jpg through 10.jpg, created a new tab on the node details that just held 10 "custom html" widgets with contents like <img src="/orion/images/${siteid}01.jpg"> and that worked to get each node ready to display any images we had for the site. In the case that rschroeder has where you would want a 1 to 1 relationship then you would probably want to use the ${nodeid} variable and yes, it will be a chore to rename each image file based on the nodeid, but I can't think of any solution where there wouldn't have to be some kind of manual data entry process to correlate each image. What information do you currently have that keeps track of all these images to begin with?
Cancel
Vote Up +3 Vote Down

Cancel
0 rschroeder over 5 years ago in reply to mesverrum

I like it!
Our current image naming has no convention. But it will going forward if we are to adopt this idea. Referencing images of several hundred network rooms and their nodes will be an initial challenge, but we have unique region, site, network room, and node names. They'll be our go-to for the new directory inside inetpub/solarwinds/orion/images/.
mesverrum for the win!
Cancel
Vote Up 0 Vote Down

Cancel