Catch Memcached Filter exceptions

The memcached filter connects when it is initialized, not when it processes an event. It never attemps to reconnect, which is a known issue.

Your approach might work to avoid calling a memcached filter that failed to connect, but the logs are going to be noisy unless you catch the exception and add a tag to the event (i.e. set your own tag, do not rely on _rubyexception).