Noemi

Proof of concept thread (Slack): https://appsignal.slack.com/archives/CNPP953E2/p1677065498603149

@1player Pretty timely comment on your end as well! We closed this because we were unsure if there was enough interest in it -- we can reconsider this decision. Part...

This issue, as it was originally opened, was already resolved with the original implementation of backtrace cleaning (https://github.com/appsignal/appsignal-elixir/pull/804) I'm closing this issue. Feel free to reopen or open a new...

@crbelaus @gmile We're considering supporting this feature by adding the last line of the backtrace (the one further from Ecto's internals) in the event. Here's a quick mockup with placeholder...

Hi @gmile! My apologies, it is placeholder text -- I quickly copy-pasted a line of an Elixir backtrace from your comment above. Ideally we'd pick the line in the backtrace...

Since this issue is seen as a workaround for #603, I have decided to first approach fixing #603 in isolation, then look into implementing this. While it is true that...

Hi @bdewater-thatch! I believe the issue with the missing data is what our docs describe under "[Namespace and action for the current transaction](https://docs.appsignal.com/ruby/integrations/rails.html#namespace-and-action-from-the-current-transaction)" and "[Tags for the current transaction](https://docs.appsignal.com/ruby/integrations/rails.html#tags-from-the-current-transaction)". Long...

This is not ideal, but the recommended way to work around this would be to call `send_error` instead of `set_error`, and manually add contextual information to the error. > Maybe...

Thank you! Yes, that would be an improvement. If you open a pull request for that, we can merge it in as a partial improvement. That said, I believe that...

No, don't worry, that'll be a bigger task on our end. (In the AppSignal agent, probably)