I think you'll find doing this may be easier (and more fun!) than you expect. Even better, you don't need to create much of a new web address. Just a new view and some limitations based on what you want people to see when they log in. I use Active Directory Users & Groups, which ties in sweetly to NPM, to set who can log in. Then I give those users or groups the views I want through NPM's admin Settings area.
1. Use Network Atlas (go to the NPM server directly and run Network Atlas--don't use NPM's web GUI) and build a map showing the items you want. Select the background (or upload a graphic that's custom to your needs), drag the monitored items you want displayed in the new map from the left pane to the map. Connect them, label them, choose custom icons as you wish. Save the map with an intuitive name. Let me know if you need additional instructions or screen shots for this.
2. Now go to NPM's web GUI. In the upper right click Settings, then click Manage Views, then click Add.
3. In one column click Add and choose Map. Then add the other items you want displayed in any of the columns, move the items up or down to make sense to your needs. Add more columns if you like.
In this view I created "East Data Center Network Equipment". I added map in the top left, then added in things I wanted to monitor about those items in that map.
4. Remember to set View Limitations if appropriate.
5. Click Done (you can always edit this View anytime).
6. To make it easy to access this new View I'd add it to a menu bar by clicking Edit in one of your menu bars, then dragging it into the bar:
You can see this bar has the "East Data Center" view added to it. Anyone on my team can click on that and see my new view.
7. Save it and login as the account that has that Menu bar.
8. When the new view opens, in the Map section choose Edit.
9. Select the Map you built in step 1 and click Submit.
10. Open your new view and Enjoy!
11. Remember to create an account for your users who need to log into NPM to see this info! Then give it your new view as the default view, and go through the access & privileges carefully to ensure the AD users/groups that can access it get only what you want them to have. Write if you need instructions for this part, but I bet you've got it down.
Customize your new view by clicking Edit on any individual area, or Customize Settings for the entire page. You can manage this yourself for the customers, or give them edit rights. I tend towards limiting their administrative access and it's worked well for the vast majority of users over the years.
As long as you & your team, or the customer & their group, log in with credentials that have access to this view, or have it set as their home page view, your new view will come up.
Remember to take away access to your new page from teams that don't need it (if appropriate). I recommend a peer review system for creating & editing these pages, to ensure someone's checking your work, asking the right kinds of questions for access (Do the customers need the ability to Edit? Do they need every option you've given? Are there other options/views we could offer them that might help them even more?). Security Admins can really be your help here, and they're often happy to see what you're doing and make helpful suggestions. Plus, it's an opportunity to share across silos and build more relationships. Maybe you can built Security some views that will help them (QoE for Splunk or Source Fire, or SAM or LEM--the sky's the limit).
I build these kinds of views for multiple teams and clients; their access is limited by AD credentials and groups, and also by the View Limitations you create in NPM. I just confirm the view is good, log in as a test user account that has the same rights as the user, and verify everything's good to go. Then I copy the URL and mail it to the client.
Customers LOVE being able to see the status of their gear. Plus they can view up-time, errors, history, trends--whatever you build and allow them to access.
Swift Packets!
Rick S.