-
## To do
- [x] Load `config/appsignal.rb` if present on `Appsignal.start`.
- I don't think we should add this logic to the Config class itself, but `lib/appsignal.rb` instead on `start`.
- It…
-
As currently implemented, `appsignal-wrap` sends data to AppSignal on the background, while concurrently passing through the process' standard output and error. However, when the process it wraps exit…
-
Given this instrumentation
```ts
import { Appsignal } from "@appsignal/nodejs";
import * as skiffaAppsignal from "@skiffa/appsignal";
const appsignalPushApiKey = process.env.APPSIGNAL_PUSH_API_K…
-
When the wrapped process exits with a non-zero exit code, this should be reported to AppSignal as an error. To ensure grouping is consistent, the error name and action should be low-cardinality, but a…
-
Next.js 14.2.x applications don't report spans to the agent.
When configured following the docs, the agent starts, and host metrics work. However, Next.js spans aren't reported, and the AppSignal O…
-
-
Here is the email from app signal:
Backtrace & parameters from app signal
- [ ] Other frameworks
- [ ] Absinthe - https://github.com/appsignal/appsignal-elixir/issues/751
- [ ] Background job libraries (verk, exq, Toniq (…
-
It would be good to include an error monitoring tool, like [Sentry](https://sentry.io/welcome/) or [AppSignal](https://www.appsignal.com/), even if it is just for development environments.
-
In #1130 we use the `stripInternal` config option and `/** @internal */` JSDoc comments to control which symbols are exported by the TypeScript compiler into `.d.ts` files, which in turn controls what…