mimiquate/tower

Issues

• Support setting contextual data to be reported later if an exception happens

  #94 opened 2 months ago by grzuy
  0

• Properly report throw as a throw (instead of exit) when Bandit plug call

  #87 opened 2 months ago by grzuy
  0

• provide a way for reporters to know whether the `Tower.Event` was auto or manually captured

  #72 opened 2 months ago by grzuy
  0

• `Phoenix.ActionClauseError` is reported when using Bandit, despite returning `400` http status code

  #83 opened 2 months ago by grzuy
  1

• Improve smartness of `Tower.Event.similarity_id` when minor dynamic values part of Exception reason string

  #79 opened 3 months ago by grzuy
  0

• protection from overload

  #13 opened 3 months ago by grzuy
  0

• Telegram reporter

  #70 opened 3 months ago by ivanhercaz
  4

• provide simple mix task to test tower is well configured

  #63 opened 3 months ago by grzuy
  0

• able to ignore certain errors

  #46 opened 4 months ago by grzuy
  0

• make it easier to distinguish between normal and non-normal exits

  #49 opened 4 months ago by grzuy
  0

• better handle logger_handler failures

  #16 opened 5 months ago by grzuy
  0

• doc: Usage section

  #6 opened 5 months ago by grzuy
  0

• able to report oban worker exceptions

  #5 opened 5 months ago by grzuy
  0

• include the `Plug.Conn` in the `Tower.Event` if available

  #38 opened 5 months ago by grzuy
  0

• clarify what the contract of a Reporter module should be

  #4 opened 7 months ago by grzuy
  0

• better process isolation when calling reporters

  #14 opened 7 months ago by grzuy
  0