DarienAL

I had a conversation with Pulseway support a bit more than a year ago(because I couldn't get my hyper v cluster machines to appear through the same setup you are trying) and after a back and forth they told me how to re-enable the functionality at the local manager app level but I can't find that email... I'll keep poking around to see if I can find it, in the meantime you should open a ticket with support and ask them directly how to re-enable that functionality. EDIT:Found this discussion.

I noticed recently that none of my scheduled reports that were then emailed to me have run since around 7/2... has anyone else noticed this as an issue?

Don't see upload/download options in the storage section of any of my endpoints in the pulseway web interface.

Does Pulseway have a status page?

Same. Have a few legacy machines that I can't quite kill just yet and noted them going offline. Assumed it was probably a secure connection error just haven't gotten around to opening a ticket with pulseway to confirm that they had just dropped 2003 because of its inability to support current secure connection options.

The issue is still occuring me as well after revisiting our alert history.

I noticed similar behaviour in a number of our servers with the pulseway agent about 2 or so months ago. Most noticeably because when the memory monitor that we configured was being triggered for high memory usage the agent was one of the highest memory usages on the machines. I havent seen this much recently so I'm not sure if, at least for us still an issue. I'd always suspected that it was some bug that would be addressed in a future patch.

I've noticed when reviewing some recent high memory alerts on a few machines that the Pulseway service seems to be using significantly more memory than it use to. Wondering if this is to be expected.

This the case even if you remove a machine from that group and reassign it? Have not seen that one, might have to chat with support about it.

If your machines are organized into groups via the section in the web portal, Server Admin>Configuration then for each Agent Group you can specify the patch management policy at the group level. Then any machine assigned to that group will inherit that policy.

It doesn't like you've still implemented the highest requested upvoted item "The ability for Pulseway to clear the notification when the condition is no longer true."

Wouldn't it be easier to have your machines in different agent groups in pulseway and assign the patch policy at the group level?

I continue to receive multiple offline/online notifications from pulseway on many of our machines across multiple environments (onprem and cloud) is this related to the issues you are having?

What were the symptoms for us as users? I received a some offline notifications for machines that weren't offline, was that related to this?

Bumping this topic as I'd also have interest in this feature.