DarienAL
-
Posts
18 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Posts posted by DarienAL
-
-
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.
-
6 minutes ago, rzubulake said:
I am picking up someone elses mess here. Looks like they are in different groups. So how would I set that up on the group level?
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.
-
-
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.
-
I've been experimenting with a scheduled task to restart some machines based on scope and I've had mixed success. Some machines in the scope restart as scheduled some don't. My powershell skills are limited so right now the pulseway script that I created to do restarts just has the powershell command Restart-Computer. Should there be more?
-
We setup some SQL query based notifications on one our servers yesterday and when it fired I noticed that at the bottom of the alert it said: Note: Another notification for this filter will be sent only after this notification is deleted.
I know there are other types of alerts that won't refire on their own unless they are reset (I believe disk, mem and cpu are the same). It would be nice if all these types of alerts that need to be manually reset carried this additional note at the bottom as a reminder as I don't think they currently do. -
This has always been my pain but for cpu and memory. Because those alerts don't reset once the resource is back below the threshold if they aren't manually cleared they won't refire. This does not make them verify useful. Hoping to get more details on how this auto clear functionality works. The examples show how to use work flow to create notifications, they don't show how to clear a notification once the threshold is below the required figure.
-
Thank you!
-
Where did group policy management go in 6.0? I don't see it in the webapp or on the agents...
-
as far as notification can you clarify something do you need to be an admin to get notifications or can you just have read-only user rights and get notifications on the status of a system?
-
I have to say I'm very disappointed in this upgrade.
Functionality actually missing that was in the previous version? (System level user rights, separate notifications rights)
No ETA for the return of those features?
Disappointing.
Older Server SSL Error
in Windows
Posted
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.