zachgoldstein

Part of https://github.com/airbrake/airbrake-python/pull/73 was a change that would check for `sys.exc_info()` when a bare exception is used.

The only thing holding me back here is looking at the other approaches from rollbar and sentry. Looks like they both use `**kwargs`, https://github.com/rollbar/pyrollbar/blob/master/rollbar/__init__.py#L263 and https://github.com/getsentry/raven-python/blob/master/raven/base.py. I'm starting to think...

> If I pass in a context key/value pair that airbrake doesn't support, should I get an error when instantiating the notifier class? Ya, I think errors at init time...

There's a couple different types of filters to build here: - White/black list keys, and replace their contents with `[Filtered]`. - https://github.com/airbrake/airbrake-ruby#airbrakeadd_filter where we add a user-supplied callback that does...

Filters: https://github.com/airbrake/airbrake-python/issues/48

@kyrylo My understanding is that filters act to remove sensitive data, where this could possibly add sensitive data to the context? I'm not sure how we would be sending data...

@kyrylo https://github.com/airbrake/airbrake-python/issues/52 contains tests that make sure that blacklisted keys do not get sent in the environment payload.

Yup, replies as well. Ideally like control over the exchange via the connect for all sockets really. It's not clear to me what socket.connect does off the bat. It either...

Basically if we've got a variety of different services, each one doing rpc, we can do something like namespacing via the exchanges and not have to worry about something going...

Also, setting a different exchange than the default allows us to set durability and auto-delete and all that. Those choices can be a bit application-specific and having access to that...