Bdtyktl

I find my Mac's syslogd "Cosole" logs become unusable when some badly written app (PathFinder.app in this case) incessantly spews into syslogd all day long.. I read somewhere that you could disable logging PER app by..

1. 
   

   Creating an alias to the executable bundle inside the App "package", and then ONLY launching that alias FROM the terminal. The process was... Browse to /Applications/ObnoxiousLogger.app, right click, "Show Package Contents", and then Browse to...

   
   
   

   /Applications/ObnoxiousLogger.app/Contents/MacOS/ObnoxiousLogger

   
   
   

   Then you make the alias through the GUI and remember to always launch the app from that alias, again ONLY via the terminal.

   
   
   

   This is annoying, as you HAVE to create the alias via the Finder (symlinking doesn't work, and there is no way to create an alias via the terminal). And if it gets launched ANY other way, youre back to square one, logorrhea.. This method DID work, but for a very short amount of time.

   
   



2. It would seem you could set this via a launchctl command, or a plist variable, but this isn't an app that is opened by launchd, and launchd's documentation is so all-over the place, but I guess this is a possibility, I suppose.




3. I saw something about sending the log to /dev/null, but it wasn't clear if this was some kind of syslogd pipe, or command, or an /etc/syslogd.conf setting, or what...

Please let me know if you have a surefire way to selectively silence logging per application, or even better, increase or decrease the logging verbosity, per process / command, etc in Mac OS X.

You may want to look at asl.conf(5) which allows you to ignore/process log messages on quite a fine-grained level.

Something like:

? [= Sender ObnoxiousLogger] ignore

should do the trick. If you still want to see the more serious messages from the obnoxious sender, something along the lines of:

? [= Sender ObnoxiousLogger] [> Level error] ignore

might be more appropriate.

Note: after editing /etc/asl.conf, don't forget to kill -HUP your syslogd.

Just create a File » New Database Search…, looking for Facility contains "console" and Sender does not contain "ObnoxiousLogger", and ignore the default Console Messages database search?

You can use the following command to set individual log filtering levels for specific processes:

syslog -c processname -d

This will set the log level of currently running instances of processname to all messages of debug level or higher. the possible levels are each character of pacewnid: (Panic), Alert, Critical, Error, Warning, Notice, Info, and Debug.

So, to only enable logging of warning messages and higher for Finder, use:

syslog -c Finder -w

You will need to repeat this whenever you restart the process in question.

The proposed solution by Torsten doesn't seem to work. It seems adding those configuration to the global asl.conf doesn't have the expected effect the way the rules are handled.

A solution to this problem, I found, after I almost went berserk fighting with the main asl.conf, is to use separate asl/* configuration files for each filter. Those files must be stored in /etc/asl/

e.g. to ignore "com.example.Sender" and filter its log spam from system.log we could create a file /etc/asl/com.example.Sender with the following content:

? [= Sender com.example.Sender] claim only

* ignore

The claim only for the match (a "Sender" in the example) causes the rules in the master asl.conf to be ignored which means things won't end up in system.log.

Don't forget to restart syslogd, of course.

I posted a more detailed answer at AskDifferent.

Put in /etc/asl.conf a rule like the following

? [= Sender foobar] [<= Level error] notify com.apple.foobar

  op   key   value   op  key   value

  -----query 1----- -----query 2---- ---------action--------

In order to ignore messages in both system.log and in Console.app, you should add rules to ignore messages before the following comment in asl.conf.

# Flat file configurations formerly in syslog.conf

Example with modifier S, which ignores messages matching that substring from SIMBL Agent.

? [= Sender SIMBL Agent] [S= Message warning: failed to get scripting definition from] ignore

  op -key-- ---value---  mod --key-- --------------------value-----------------------

  --------query 1------- -----------------------query 2------------------------------- action

After adding a rule restart the daemon with sudo killall HUP syslogd.

Tested successfully in OS X 10.8.5.

I am on MacOS Mojave (10.14.3) and this post was helpful to me so I want to clarify what worked for me as I have not seen it all together in a single place. In my case I wanted to filter out Microsoft OneNote messages which were constantly spamming my system.log file at a rate of 5 a second. Sample message:

Feb  3 22:52:49 MyMacMini-2 Microsoft OneNote[393]: [ACT]:[TASKSCHEDULER]:[Info]:opQueue=0x6000012d7760 after call to waitUntilAllOperationsAreFinished

So I edited /etc/asl.conf with the following rule:

# Disable Microsoft OneNote logging as is filling up system.log!

? [= Sender Microsoft OneNote] ignore

You need to add this before the line that says:

# Rules for /var/log/system.log

As otherwise it will not work. Then just restart syslogd with this command and the messages should be gone from system.log:

sudo killall -HUP syslogd