lcsw2013 ✭✭✭✭✭

Couldn't have said it better. The other way around works too, but only if your environment is perfect haha. In case of our's it's not perfect, and thus we have issues when using anything but ICMP for response time. I'm hoping this gains traction.

Bumping Again! Running into some big frustrations with reporting and limitations on the conversion engine. Trying to find some support in having a better reporting that uses the new excel extension and allows more character and doesn't limit me. Having to split report into weeks at a time creates several spreadsheet that I…

I tried it. And I'm getting an error "The specified string is not in the form required for an e-mail address." What I did was I created a nodes custom property called Owner_Test_CP. I then set the alert up according to the KB and your explanation. The alert worked normally as a reboot alert. I rebooted a test server I have…

Thank you so much!! ding​ , I wanted to get your opinion on this feature request. Any chance it can be implemented? Or is it part of the roadmap for IPAM?

I hate to use the word force. So I'll say that I agree, but deprecating report writer and removing it from the software it will "nudge" users to see the value in the web report writer. You have my up vote. Rewrite them and transfer them to web report writer. Lets move the software forward. Not backwards. 

bump

Bumping! I know I'm not the only environment monitoring UCS (Or trying too). And I'm not a fan how most opt for customization rather than requesting it to solarwinds as a native feature. There has got to be other administrators out there properly monitoring and alerting on UCS hardware. Would love to have help and…

bumping it up.

It's in RC so I'd assume they will launch soon I guess. As far as fixes go I think some fixes are included but not all of them. Some things are still being worked out. 

Just an Update for anyone following this. SolarWinds has confirmed a known bug with unmanaged interfaces and volumes causing polling to get stuck and stop. It polls perfectly manually but the polling is broken in the the next poll time will keep going into the past. This is confirmed a known issue discovered in our…

What I've seen from others on this thread is that there is no mention of a fix for the polling issue in this new version. In our own ticket with solarwinds they have told me that they are not sure of the root cause yet to the problem. They confirm that it is an issue but they don't appear to have a fix available yet. If…

No Update. We actually just had a meeting with a Support director who admitted that they understand the issue but do not know the root cause. And they will be assigning our ticket to their highest engineer with the most experience in the software to work with development and others to try and sniff out the root cause and…

Normally we wait RC versions. But in this case we are awaiting direct confirmation from the Rep's we are working with before we consider making any changes to our environment. No one here wants to make a change unless solarwinds can guarantee it works. 

Interesting.

We are awaiting word directly from the Rep's working with us. We normally do not consider RC Versions. We normally wait till General availability to make sure all kinks are worked out. But in this case we aren't upgrading till we have direct confirmation the upgrade will fix the issue. 

In our environment we usually hold off Till General Availability. We allow solarwinds to work out kinks in RC versions before we consider an upgrade. And our Rep's at solarwinds haven't confirmed this would fix our specific problem. But hopefully it does. Looks like solarwinds is moving relatively quick to try and fix…

In our environment we don't even have them go unknown. We just have the yellow warning box saying that the information is obsolete and the second clue is graphs that stop updating. And the last clue is the next poll time gets stuck in the past. Then we have issues with server monitoring that it too will not go unknown but…

Yes. I've had a ticket escalated now for over a few weeks. Not much in a way of progress have done in order to stabilize polling at least while we troubleshoot. I got tired of asking for this and support kept going around this and diverting back to troubleshooting. Essentially forcing me to take some measures into my own…

When I saw this I attempted it in our environment and it didn't help at all. I think the above fix could be specific to certain issues. And since polling instability seems to be related to different issues and not one single issue there could be different fixes depending on the issue. Seems like at a high level the issue…

Unfortunately under our escalated tickets they have not mentioned anything. I think that the date mentioned might be speculation I would assume. But as for us we have not been told of any buddydrops or hotfixes. The only thing we have going on is testing where their development asks for something we do it and the back and…

As mentioned in my other response if I was in your shoes I'd be cautious and wait. But if you must upgrade at least save the backups and hang on to them because if the problems do happen you'd want to revert back. 

We have a moderate sized environment and this issue has been on-going since we upgraded to 2023.2. I can't speak for anyone else but I'm pretty sure they can chime in if they are experiencing this too. It is know to solarwinds. So it is a know issue that they are actively trying to solve. If I were you I'd wait just to be…

You have failover which is an awesome feature. Unfortunately for us we don't have that implemented. Or that would of solved a huge headache we have currently in our situation. For us we've only been restarting solarwinds services and restarting agents that get stuck. I've attempted to make and modify a few scripts to try…

No worries! I was just happy to see that it wasn't just us having issues. Hopefully solarwinds finds a fix for all of us. 

Those steps to me seem like it would cause you to lose historical data. We do have agent polling issues we are seeing but in our case it doesn't appear to be agents that are acting up but rather the poller itself. From what I understand from support. What I've been doing is I restart the job engine and many times it's…

Mention this thread to support. I started to try and consolidate similar instances of everyone having polling issues so they could investigate on their end. They have identified there is a polling issue as it appears like everyone is reporting the same thing once service is restarted it works for a bit then it stops. But…

Tony, I've been at this with support for a long while now. They have Application Engineers and Developers both trying to figure this out because the root cause appears to be different between different environments out there according to what I've heard from the folks working on my ticket. For example they explained that…

According to the folks I been talking to at support there isn't a fix yet. What I do is as soon as I notice poll next times start to fall behind for a poller I manually restart the job engine on that poller. I'm trying to figure out how to properly automate this. I've attempt to script it a few times but it doesn't work…

There isn't a fix yet. I've been working with support nearly every day for several weeks now. They are narrowing down a solution but not there yet as they said that at a high level polling affected but on their research they see that different environments are failing differently this is why they haven't officially yet…

The update I've gotten from support is that this has become a front and center issues for them and they are attempting to investigate and find a way to troubleshoot this and find a resolution. As for us, we have been manually polling devices and restarting services just to keep the system going. Otherwise it stops polling…