heroku exception logging doesn't work

sjain's Avatar


15 May, 2013 06:59 PM

I created a exceptional.io account independent of heroku. Then I configured exceptional.yml to include the correct api-key. I test verified config using "exceptional test" command locally.

When I deploy to heroku, I observe following behavior:
1) "exceptional test" soccessfully records exception
2) exception within app don't get recorded.

Here is my exceptional.yml file -

api-key: eb85778c3ba8c406f548594b8509369df0870a1a # (account: [email blocked])
  enabled: true
  send_to: api

Here is my "heroku config" --

=== medoptimizer-staging Config Vars
CODESHIP_ID: <something>
DATABASE_URL: postgres://<something>.compute-1.amazonaws.com:5432/<something>
HEROKU_POSTGRESQL_CRIMSON_URL: postgres://<something>@ec2-54-243-241-23.compute-1.amazonaws.com:5432/<something>
HEROKU_POSTGRESQL_GRAY_URL: postgres://<something>@ec2-107-21-101-4.compute-1.amazonaws.com:5432/<something>
LOGGLY_URL: http://<something>.loggly.com/heroku/resources/<something>
PGBACKUPS_URL: https://<something>@ackups.herokuapp.com/client
RACK_ENV: staging
RAILS_ENV: staging
SENDGRID_USERNAME: <something>@heroku.com

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac