General
30 results found
-
Execution Filtering by User?
With thousands of files actions all day by many users, I believe it would be useful to be able to limit script execution for certain users, or at least pattern matching like the files/folders. We currently get around it by checking the script that is firing, but it there are thousands of unnecessary executions when one of our developers moves files around.
5 votesFiltering by user and/or process is now possible by prefixing your include/exclude pattern with ‘?’. This follows the same rules as file/directory filtering but the ‘?’ prefix indicates it is to be used for usernames and process names.
Please refer to Example #5 for more information: https://deventerprise.uservoice.com/knowledgebase/articles/196135-exclude-and-include-patterns
-
Syslog Option
Send alerts to syslog server
1 voteThis was actually completed quite some time ago. Please download the latest version to get the Syslog plugin included.
-
Better Text Log Handling
It would be helpful if the text logs had a limit to what is displayed and handled so the application does not crash when the text log gets really large. In my case, the log file gets very large very quick (sometimes is as little as a day or two) and occasionally crashed the program. It would be nice to not have to manually clear the logs.
5 votesThese performance issues have been completely addressed in v2.7.0.7.
Automatic trim of the UI text log file to 1000 records on startup. The log can grow to approx 10,000 lines during operation and then trim in 20% chunks, optimized to display all lines in rich text format. I recommend keeping custom text log files or use the grid log for anything more significant than these numbers.
The grid log will hold up to 20,000 records which load and group in under a second during startup and operation.
Loading of records in the grid and text log are heavily optimized now and does not affect the startup speed of Directory Monitor, processing of large files should really be done outside of Directory Monitor so these limits are set for optimal performance for ‘above normal’ usage.
-
Monitor folders only
Great program, just bought a Pro license. Just wondering if there is any way to monitor folder/subfolder changes only (and not the files within those folders).
Basically, we'd like to get an email alert when any folders or subfolders are moved, renamed or deleted. Without adding every file type to the exception list, is there any way to monitor for changes to folders/subfolders and not get emailed on changes to the files inside those folders?
1 voteReading the initial requirement more carefully, you do not want to get notified on ANY files, just actual directory changes which means a star-dot-star exclusion will be perfect.
-
Pause feature
It would be helpful to have a "Pause" feature to temporarily stop monitoring a directory without having to remove it from the list. Maybe via "Right-Click" to a particular directory in the list?
1 voteDone in v2.4.1.0.
-
Database Plugin
A plugin to write the event data from Directory Monitor into a database (relational or not).
This could include multiple plugins per database type or a single plugin with the ability to access multiple types of databases.
The following databases could be supported:
1. SQL Server 20005/2008/2012.
2. MySQL
3. Oracle
4. Postrgre SQL
5. SQLite
6. Azure (or other cloud based databases like FireBase)
7. MongoDB (or other NoSQL variants)
8. Many, many more...Scripts to create the database will be included if the user information provided to Directory Monitor does not have security rights to create tables, views…
24 votesThe plugin is complete and available in v2.6.1.1 for both MS SQL Server and MySQL database providers.
Please report any bugs so they can immediately be corrected and please email or lodge additional feature requests, suggestions or ideas right here at https://deventerprise.uservoice.com/admin/forums/198724-general
UPDATE: Fixed a number of bugs in v2.6.1.2. Please update to this version if you are using Directory Monitor 2.6.1.1 or 2.6.1.0.
-
Emailer Plugin (extras)
A plugin that send emails when events occur.
Plans to enhance the plugin with rules similar to the execute plugin. Ideas include:
- delay before sending mail (0...5 min, files probably is still locked)
- delete files after sending
- archive files in one archive (a lot of small files)
3 votesLeaving scheduling out of the plugin for now unless there is demand for it. Having advanced scheduling for when to send emails at a specific time would be a powerful feature although complex for the small potential usage.
Windows scheduling should suffice for most scenarios and the current rules/options are sufficient to get notified when changes occur rather than a full scheduling setup.
-
Growl Plugin
A plugin that uses Growl (http://www.growlforwindows.com/) to notify the user of messages as an alternative to balloons in the tray.
Growl is an advanced notification application that applications can register for. Using Growl you can be notified by an application on the same machine or even over the network. Notification windows can be completely customized.
3 votesGrowl plugin will be available in version 2.10.0.0 due for release on 07/06/2015. For an early preview please download https://directorymonitor.com/DirectoryMonitor2_vNext_Setup.exe
Documentation will come next.
-
What is the format for exclusion patterns?
Need a help article describing how to use this feature
1 voteAs requested, here is a KB article on exclude and include patterns: https://deventerprise.uservoice.com/knowledgebase/articles/196135-exclude-and-include-patterns
I hope that this clears things up, it’s quite a lengthy topic but once you get the hang of wildcards it’s easy.
-
Limit number of emails that can be sent in a time period
To avoid getting spammed with email (or flooding your email server) when a directory gets busy, a limit should be set on how many emails can be sent in a given time period.
A option to set the maximum number of emails as well as per minute/hour/day. Another option would be to send each backlogged (individually or in a batch which limits the subject macros) as soon as the cooldown period has passed. The user could also opt to ignore all emails and only start sending fresh ones after the cool down.
The cooldown could also be reset from the…
0 votesBasic time based limiting can now be applied in version 2.9.9.9. If more advanced options are required please open up a new idea to expand on this feature.
- Don't see your idea?