Fix Excon instrumentation and other improvements

Changed

• Fix Excon requests being reported as taking almost no time. An Excon request is now recorded as a single request.excon event covering the whole request, so the event lasts as long as the request did. The response.excon, retry.excon and error.excon events no longer exist. AppSignal also no longer registers itself as Excon's instrumentor.

• Report which template was rendered for collection and layout render events.

• Name ROM query events after ROM, rather than after the database they ran against. A query made through ROM was reported as query.postgres, or query.sqlite, or whatever else the application's database was. Those queries are now all reported as query.rom.

  Events that dry-monitor reports and AppSignal has no formatter for are now named after their event id followed by .dry, so an event reported as foo becomes foo.dry. They had no group at all before.

  If you have a dashboard, trigger or saved filter that names one of these events, point it at the new name.

Fixed

• Fix a rare hang when stopping AppSignal in an application that sends check-ins. Stopping AppSignal waits for any check-in events that have not been transmitted yet, and it could wait forever instead of finishing.

• Fix event formatters that register or unregister themselves. Calling unregister on the formatter itself, as in MyFormatter.unregister("my.event"), did nothing at all. The formatter stayed registered, and no error was raised and nothing was logged to say so. Calling register on the formatter itself stored it where AppSignal never looked for it, so it was never used to format an event.

  Registering and unregistering through Appsignal::EventFormatter itself, as in Appsignal::EventFormatter.unregister("my.event", MyFormatter), was not affected and keeps working the same way.

View the Ruby gem v4.10.0 changelog for more information.