Wanted to check out some additional swag purchases, but I'm getting a Jive error.
Like this:
Sorry, the page you requested can't be found. You can go back and try again, or start again at home.
rharland2012 how are you getting to the page? Direct link? Banner on the homepage? Search? I'm able to get to the store page so just looking to gather some more info.
I am getting the same error
I click on the Store link from my account settings area on the drop down
Hi there - right-hand side of the homepage was my vector for attempted access.
rharland2012, kthomason,
Can you try using this URL and forcing your IP to hit this particular node?
https://thwack.solarwinds.com/___sbsstatic___/node1.html
We are having some issues with Node 2, so if the load balancer is routing you to that node, certain URL's are throwing 404 errors. If that doesn't work, let me know. I am working with our vendor to resolve the issue, but until they have it fixed, this might be the best option for us as a temporary work around. Sorry for the inconvenience!
Thanks,
Rach
BING!!! That did it. I appreciate the help!
Sounds like you need Orion watching the 2 servers on the other side of the load balancer...just so you know when one isn't responding as it should.
I have been begging our vendor to use Orion because we don't own those servers. The most I can do is use NPM to ping the individual nodes but it can't tell me when certain themes break, which is what happened here. If they would let me teach them how to use NPM and SAM they would be much more proactive rather than reactive. One day, they just might listen
Make that part of the contract.... (ya right!)
The swag order can wait.... NBD...
Load balancer url worked like a champ.... thanks.
just watch the urls to the individual servers...like what you gave rharland2012
So we do use NPM to hit those individual URL's, just like you mentioned, but it only hits the home page to let me know if it's up or down. Node 2 is actually up; it's only throwing the 404 error when you hit certain pages that are linked to customizations we've done. The typical community platform does not allow us to use gamification for physical store items, so we built the store as a customization that integrates into our theme. Another thing that isn't working is the idea's. You can click on the main pages of an idea but actually clicking on the idea returns a 404 error because again, we've customized how those work so people can see most recent ideas, their ideas and FAQ's. Again, this is integrated into our theme. I wonder if I could use SAM and have aLTeReGo build me some custom templates to monitor our customizations specifically. Hmmmm....you've got my wheels turning Jfrazier.
you should be able to do the "monitoring" of the ideas and and use WPM to login as a "user" so you can get to them as a user would.
That way you can see how long it takes for portions of the page to load and can give you a feel for user experience. It helps if your WPM machine watching the load balancer is on the outside (internet side) looking in.
The other one looking at the two servers can be inside the firewall but if available as in this case from the outside works too.
The key is to test this at each server and through the load balancer so that you see where it could be broken at because just watching it via the load balancer may not tell you that you have a problem.
Depending on the load balancer, it may tell you if it tossed one of the servers out of the pool because it was not responding properly.
You can use a combination of SAM and WPM for your best value...
If I understand the suggestion properly, it sounds like some of this might not be an option for me as we don't own the servers, load balancer or firewall. All of that is being managed by our vendor. We only started using NPM to hit the individual URL's because we were seeing load times increasing but our vendor wasn't actually monitoring that aspect of things. They only have it set to ping them if the node goes down. I get the alerts if the home page doesn't render within a certain time frame so I can then provide screenshots so they can troubleshoot it for us. :-(
I think it's still worth a conversation internally to see what more we could be doing to give us better visibility into the performance of our website.
Yah, it's so helpful to be in total control. Where I monitor our F5's and servers and internal resources, life is happy, everyone gets alerts when something isn't quite right.
Monitoring an ASP's internal functionality can be problematic if you only get access to the VIP of their F5's. But if you can get deeper in, you should be golden.
Even if you can't get into specific nodes behind their F5's directly, I'd expect you could hit the F5 VIP's frequently enough to have them round robin you to a server that's problematic. A single failure would be enough to generate an e-mail to your team--and also to the vendor's Support staff.
How ironic they're not wise enough to take advantage of your company's expertise and tools!
