Jump to content

Search the Community

Showing results for tags 'feature request'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Pulseway
    • News & Announcements
    • Installation & Configuration
    • General
    • Automation
    • Applications
    • Current Features & Server Modules
    • API
    • Feature Requests
    • Bugs
  • Pulseway On-Premise Server
    • Installation & Configuration
  • Pulseway PSA
    • General

Calendars

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

  1. Hi Pulseway. It would be very nice to be able to manage Tags from the client. It could be in the Pulseway Manager, in the registry settings, or via commandline. Could that be possible? Br, Martin.
  2. Let me start off by saying this is not meant with any kind of hate or ill will. I very much love the Pulseway product overall, and I have been using it for a quite a number of years now. I very much want to see Pulseway continue to improve and catch up to a lot of the other RMMs out there by addressing some obvious "misses" with certain aspects of the software. This is going to be a bit of a novel but I hope the Pulseway staff and the community give it a read and feel free to comment, add suggestions, etc. The below items are too much to put into a bunch of separate feature requests. I apologize in advance if this is too much in one spot Interface/Web UI: Ability to completely remove or hide default scripts. Should also be able to delete individual ones within the default section. Ability to adjust script level permissions. There are some scripts I have written such as an MDM remote wipe type script that I want to be able to access within Pulseway if needed, or one of my higher tiered consultants but not my lower tier. I should be able to assign some sort of permissions to scripts to hide/show them based on security group, level, or team. A full inventory of the machine should be performed by the agent and visible in the web portal. This is a basic function of every other RMM I've used. I should be able to see all services on the machine, just like Pulseway looks at all applications installed. Services should then be selectable to be managed or not, or allow the ability to manage them right from that screen. Windows Updates - We should be able to easily see a list of installed updates on the machine without having to go back through Patch Policy History. The list could easily be populated on the Windows Updates section that Pulseway currently has. Dashboard - Needs more adjustable widgets. Patch status should be available as a dashboard widget with the ability to drill down to site/customer or filter for those things when creating the widget. PowerShell Console - Should be able to press up or some other key to be able to access, select previous inputs from that active session. Scopes - From the Scopes creation page, we should be able to then click on the Scope and see all the machines that the Scope includes. This would be a much easier and faster way then having to go to Systems and then select the Scope and drill down that way. Exclusions - We are unable to create exclusions for alerts. The answer is to move the machine to it's own group, and apply a new policy to that machine. This is certainly not ideal as 1, if you logically group your machines together, then splitting one out is a mess and even more importantly, then more policies created, the more you have to worry about going in and updating them when you want to change 1 thing. The less policies that have to be maintained, the better. Scripting: Input Variables - My single biggest issue with scripting currently is the lack of usability with the current custom input fields. It takes more time to click add/edit and input what is needed into the UI, then it does for me to just declare the same variables at the start of my script when writing them. Have script input variables work as environment variables, and they can be filled in at the time of script run. So if I have script to search for something by date range, I can create 2 input variables, Start & End, and leave them blank. When I got to run the script, it pops up a window with the available custom input variables allowing me to fill them in at that time. Here is an example of a popup window at the time of run for another RMM tool I've used. All these variables are declared in the script as $env:customvariablename, and then inside the RMM portal, at the script creation screen, they are entered in, much like you can with Pulseway, and you can select the type of variable. Variable value, Boolean, selection (dropdown). Whatever is selected/inputted at the time of ran is simply passed to the $env:customvariablename that corresponds to that input variable. I've shown the 3 areas of how this works to show the complete idea behind this in the attachments. Site Variables - Pretty much the same concept as above, except these are created at the site (customer) level instead of the script level. They are called in the same fashion as above. This would allow for much greater flexibly around scripting as many clients have license specific software that needs to be installed and being able to set a site(customer) level variable that gets pulled automatically when the script runs, would allow for 1 script to be made and ran across multiple clients at a time without having to edit the script or make copies with the unique license key for each. It would simply read from the site variable when running and insert whatever is in that site variable field. Output of scripts (the content) in the push notification or email alert. If I schedule a task to run on a recurring basis and I get a failure notification, being able to see why is incredible helpful. Or, even if it's a success, there are plenty of use cases why seeing the output is needed. If I'm running a script to collect xyz info across multiple systems, being able to easily see that in a central spot on the notification or email is imperative. I shouldn't have to log into Pulseway and check each machine or check the task and look through the report. Tasks - We should have the ability to schedule tasks to run much more frequently that once per day. I would like the ability to run a custom script that checks for something specific let's say, once an hour, which then writes to a custom event log that I then have Pulseway set up to trigger an alert from. This would be helpful in creating plenty of custom alerts based on Event Log errors but once a day is not frequent enough in some cases. The ability to select multiple machines and run a script against them on the fly without having to tag them or create a scope and run a task. When a task is completed and you are viewing the results, it would be awesome if you could click the machine and go right to it from there. It's a little cumbersome to be viewing the results of a task, specifically looking at ones that failed, and then having to click out of the report and go drill down to each failed machine. Workflows As I understand it, the entire workflow idea works around something that generates a notification. This creates a big issue with workflows in the sense that, we are limited to whatever Pulseway deems an acceptable "condition" or filter. What would make workflows amazing, would be essentially turning them into "custom monitors". What I mean by that is I create a script that let's say reads some random programs event log because my customer needs to know when this particular software generates a specific error, (and no, it doesn't write this error to any event log). There is no built in way to approach this with Pulseway. If I could simply create a workflow and choose to run a script as the initial item, and then based on the exit code of that script, do other things from run a script to fix, generate an alert to my team so someone can go in and look at what is causing the error and resolve it, etc. I could apply that workflow to any systems I wanted, and set it to run every 10 minutes, an hour, whatever, and when it detects the event, again, based on how the script was written, it triggers the workflow or the alert. As in the example above, if I set it to run every 30 minutes and look for "if error exists", if it does, it then creates an alert so that myself and my team get notified. But it would also allow the workflow to perform additional steps as remediation if desired. Another useful example of what I'm trying to explain, is perhaps I want to perform a certain set of steps based on a tag setup in Pulseway. I should be able to set up a workflow against a tag or against a scope and set it to run every so often. When a machine is then given that "tag" the workflow triggers and performs the steps assigned. This goes along with 4 under scripting. In the same vein, workflows should be triggerable off the result of a script. In other words, I shouldn't HAVE to make it an event log entry. It would be great if I could set up a script via a task, and then set a workflow to check results of that script and allow me to choose either to alert or trigger a workflow on either a success of failure, whichever I wanted at that time. Cloud Backup: I would LOVE to use Pulseway's built in cloud backup, but there are just too many flaws / missing items in it currently. Scheduling - The only current options are every day, every 2, or every 3 days. All backup solutions I've ever seen, give you the ability to select which day(s) you want the backup to run, be it every Monday, or any multiple combination of days. We should also have the ability to select the TIME the backup will take place. Right now, it uses the time the backup job was created, so if I want a job to happen at 2 AM, I have to stay up until 2 AM to schedule that job for the first time. This is a very shocking miss on the backup front. Ability to exclude certain file types (by extension) is needed. Notification on job success or job failure is a MUST, not how it current is where it notifies you once it reaches below a targeted % range. The ability to see the used space. Since your cloud backup works off either 500GB or 1TB licenses, we need to be able to see how much space is current in use per machine so we can plan to take the needed action should the backups start approaching the limit. A report on the files backed up. Since this is a file only backup type, it's imperative to be able to see a list of all files backed up during the job, and if they were successful, failed, or skipped. The ability to specify if the backup is considered a failure based on % of failed or skipped files is also needed. For example, if I'm targeting 1000 files, perhaps 5 failed isn't a concern to me, but if 300 fail, that's a failed backup job IMO. Therefore, having the ability to say if 10% (or whatever amount I want) of files fail to backup, the job is considered failed. In general, during my demo of this, I've had some concerns which your staff did witness directly: The next backup date seems to fluctuate between the current day and next day if you sit that the backup status screen of Pulseway. The initial dig into a backup job, showed folders that I had excluded, were still present and you could drill down. However, after mounting a recovery to explore, the interface then hid all the folders not backed up. Concerning if it's collecting any data from folders I specifically didn't include in the target paths. You can see from the image below, it backed up 2 days in a row, almost the exact same amount of files and used the same amount of space. This is a test VM which had no changes in the test target directories, and yet the 2nd day it did what appears to be a full backup again. Subsequent days seem to have improved and the file count went down to a more expected level. Here are some feature requests I submitted around some of the points above: https://pulseway.featureupvote.com/suggestions/189283/more-robust-input-and-site-variables https://pulseway.featureupvote.com/suggestions/189917/patch-status-dashboard-widget https://pulseway.featureupvote.com/suggestions/214566/more-flexible-task-scheduling https://pulseway.featureupvote.com/suggestions/217128/exclusions
  3. Hey guys! I think Pulseway would be even better if the alerts would clear themselves when resolved.. For example, a server with available windows updates will reboot during our custom maintenance window but the alert will stay until I manually clear it in either the webGUI or the Dashboard app. Those kind of alerts along with cpu spikes, short memory outtage etc are more like "white noise" in the monitoring for me and I'd like to focus on alerts where a proper action is needed in order to resolve. To build further on this idea an even better improvement would be to tie alerts to scripts, so if Alert X is triggered, script Y will run and Alert X will be cleared. Let me know what you think! // Martin
  4. It would be great (save me a lot of time) if, when downloading the custom Windows agent installer, there was an option to specify if the installer should create shortcuts or not. IOW, in addition to selecting the organization, site and agent group, there would also be an option (true/false) for "create program shortcuts" (or similar).
  5. Instead of performing necromancy on this older thread, I will raise this question again. Why can we not see asset info for offline systems? I know this is available through reports, but that's a ton of steps to go through when it's already readily available offline (since the Reports can search it) and it should just be visible. This has been a big gotcha (along with not seeing internal IPs without running a report or being able to copy/paste in remote sessions) as we moved from another tool to Pulseway. I've seen more than one thread about this, and each time the response is 'run a report'. Please stop brushing it off as 'RTFM' and provide the functionality we're asking for. Thank you.
  6. You tell us we can monitor everything on any device from anywhere.. But with the vmware addon you cannot even readout the hardware/health status of esx(i) which is very simple because the API is already there.. you just have to read it out.. that all.. Now we do not know if a disk has failed.. and when the second disks fails.. down goes the ESX(i) server...
  7. You can now trigger workflow executions from Event Logs notifications and evaluate Event Id, Level, Message, Name, Source and Filter Title in conditions to build even more customisable workflows for your IT processes.
  8. I would really like to see an outlook add-in that can be pushed through office 365 to all users that would allow them to submit tickets with drop down menus for ticket type, sub-type, priority and description.
  9. I just signed up for Pulseway to monitor a small client of my side business. I am in the process of setting up patch management for workstations. I would like the systems to prompt the end users to reboot upon installing updates but Pulseway seems to be very restrictive in how it lets you set that up. It looks like all I can do is have it reboot immediately or give the users a 5 minute warning with a generic message. I work with a competitor product at my day job and it allows us to specify whatever message we want, set whatever timer amount we want and allow the users to defer the updates as many times as we want or force a reboot after a certain number of deferments. It does not appear Pulseway provides any of this customizability. It would be very nice to have these options so I can have choices other than forcing end users to reboot during the day or having systems that potentially go days without a reboot after installation. Thanks!
  10. As most of your supported OSs can run Docker can we have basic docker management? It would be handy to be able to start, stop and see what ports are exposed by the containers. Cheers.
  11. Hi. It would be amazing if all reports had a "Generate individual reports for each organization" option. Then we could just schedule a single report for "all systems" and get individual reports for each customer. The alternative is to set up individual reports scoped for each customer. And as a bonus remember to set up new reports every time a new customer is onboarded. :-)
  12. Remote Control really needs the ability to both trigger a reboot and to automatically reconnect when the system you're connected to completes the restart. Having it immediately disconnect when a reboot is triggered (usually if it's running as a service, it should be able to hold the session open for things like the first phase of installing Windows updates) and having to manually try over and over again to see if the machine has completed its reboot is really frustrating when you're trying to solve an issue remotely that requires a lot of reboots or even when you're just trying to do a number of updates to a system.
  13. TL;DR: Align timezones across reporting and web interface. Request: When raised during our trial to engineering, the feedback is that browser displays local time, and reports are generated using UTC. The misalignment is visible in my example shown where a report shows a system was back online at 05:32:07, but it actually and factually came back online at 06:32:07. Suggest either including "UTC" in the report, or allowing time zones to be configured globally or per site. Also noticed, that the "Generated at 04 Sep 2020 01:20" footer on the report is 6 hours behind GMT (report generated 07:20am GMT), so this could also do with being aligned accordingly.
  14. Requesting a Two-Way sync between Autotask's PSA and Pulseway. (And possible more ticketing / PSA systems). I would like to see when a ticket gets resolved that the Pulseway resolves / deletes the notification. I tried to get something going with the API, only the Ticket ID is not being sent over to Autotask. This could be a quick workaround. P.S. Why is under every ticket the text: "Sent from Pulseway (www.pulseway.com)." being added? I already paid for the product .
  15. I have a support ticket where I asked this question and got a reply that it could be looked at in the future. Just placing it here to ensure it gets put on Feature request list and so others can comment. When sales tax is added to invoice in PSA then synced to Quickbooks via PSA QB SYNC, it defaults to sales tax code G. In Canada, G is GST @ 5% by default (and correctly so) out of the box. H is for HST is dependent on province. In my case, HST at 13% is setup in PSA, but when the invoice syncs over to Quickbooks, it imports/syncs as tax code G (at 5%). I have to edit EVERY SINGLE INVOICE.I just need to tell PSA to use a defined sales tax code when syncing to QB. I would consider this more of a bug than a feature. What's the point of automation if you have to go back and edit everything? Connected...I sync invoices over to QB so I can use my custom invoice template. Its been said elsewhere, but we REALLY need a way to edit/create our own HIGH QUALITY professional and modern looking invoices in PSA. No offense, but the few invoice templates that exist look horrible. As always, I appreciate all you guys are doing and know you are swamped with current RD and RMM centralized rollout. Keep up the good work!
  16. I like automation and workflows but it has one big drawback. It can only run PW scrips or linux bash scripts. we cannot fire off any pulseway RMM internal functions. for example. Lets say when a computer checks in i want to launch a 3rd party Patch Management policy. Right now i can only do this on a timer or manually or set the policy for if missed, i can not make this part of a workflow. another thing i can't seem to do is have a workflow repeat. For example. i have a workflow that says when a computer registers it checkes and installs updates. Oviously for windows this needs to be done more than 1 time. I cannot find a way to have it check and then recheck until all windows updates are installed (maybe this is possible and i just dont know how)
  17. Not that I am opposed to blue, but it would be nice feature to change the theme colors on the webapp. This may also help those that need a more high contrast display as well.
  18. Would it be possible to add the current logged in user for each pc to the header info that shows in the middle panel. We manage several hundred pcs and the computer name of ASSET-1234 does not tell us whos using it at that time. Most end users do not know their computer names. So trying to find the computer a user is on is sometimes difficult. Having this info at hand in the search list would help that a lot. i am only thinking this information for workstations, servers could potentially have multiple users logged in at the same time and this information would not be as useful (not to mention not enough space) I have included a mockup of one way this could be done. Also adding the ability to search for a current logged in user would be helpful.
  19. We use Puleway Webapp (RMM) and PSA. I have to setup to different logins (PSA is on SAML) for access. Is there any plans to allow us to link and integrate these two logins?
  20. The ability to just pull your phone out and run a Ansible playbook would be amazing. Maybe even get run status or just the output of whatever playbook was run. This would add a crazy amount of flexibility to Pulseway.
  21. Hi there, This might be a bit of a long shot - but I have an end client who's interested in deploying custom Teams issues with Pulseway (as there aren't many users in-office for obvious reasons). I've attempted to deploy this by pushing a batch script, to copy the backgrounds from a shared location. The backgrounds folder in question is located in the user's roaming appdata (%appdata%\Microsoft\Teams\Backgrounds\Uploads). For this reason I wasn't able to use %username% correctly in my batch script, as the script is being run by some Pulseway service, rather than as the local user account. Please let me know if you've any ideas and have a great day. Cheers, Joe
  22. In trying to diagnose systems, often we need to be able to connect to a system before the user prompt for login. This allows us to see statuses of updates, rollback errors, etc.
  23. Treating user groups more like AD user groups would allow more granularity of access and less duplication of security roles.
  24. It would be nice to be able to add negative keywords to scopes (i.e. Does not have tag). We currently use a script to automatically update the system name to include the username, but there are some systems that we want to keep a static name so they are easier to identify. Currently we have to separate these into their own groups in order to keep them statically named.
  25. After coming from another competitor, one of the major things we are missing is a site wide software list with the ability to list systems with software and remove it from multiple systems. Ideally, initially it would show all software, but would allow you to filter software by name. At that point you would be able to click in and see installed systems with installed version.
×
×
  • Create New...