Bring an app event into Vortex

3 minute read · Signals & Errors

Bring an application event into Vortex so you and your agent can inspect what happened. Start with a deliberate test event before depending on the feed for real errors.

• Create a small integration you can verify
• Send one fictional event
• Resolve an integration failure
• Add the integration to the failing path

Create a small integration you can verify#

Create a named Signal app for the application and environment you are testing. Choose the local/cloud target offered by the UI and obtain its actual ingestion endpoint and token. Copy the generated integration snippet for the app's language or framework. The dialog provides examples for Laravel 10, Laravel 11+, Symfony, Node/Express, Python, Ruby, Go, .NET and cURL; these are snippets, not automatically installed SDKs.

Keep the token in the app's intended private environment configuration. Never include the real ingestion token in a public issue, documentation example or logged URL. Local and cloud targets have different reachability/storage boundaries, so use the endpoint generated for the selected target.

Send one fictional event#

Trigger a harmless development event with a recognizable message, such as “Small Stories integration check”, and a development environment label. Verify that it appears in the intended Signal app. Open its details and check the occurrence/receipt time, severity and any context supplied.

For an exception, inspect the class, file/line and trace. URL/method/context fields can contain private data; redact sensitive request headers, tokens and personal values at the sending application. The presence of an ingestion token is not a reason to send every raw request body.

Resolve an integration failure#

If the event is rejected, check the selected target, token, payload validation and rate-limit response. If no request arrives, inspect the sending app's integration path and environment configuration. If it arrives under the wrong app, stop sending and correct the token mapping rather than clearing another app's history.

Rotate a token deliberately and update the sender's configuration. A rotation needs a fresh test event before declaring the integration restored. See event management for sharing, unread counts and notifications.

Add the integration to the failing path#

Use the integration dialog for your application's language/framework, copy its generated example and store the token in private app configuration. Send a recognizable development event, then cause one controlled exception in a disposable flow. Check that severity, message, environment and file/line details help you identify the right failure.

Do not send an entire incoming request by default. Allow only useful context, such as a fictional record identifier or the failed operation name, and remove authorization headers, cookies and secrets before ingestion. An event URL or stack trace can expose private paths even without a password field.

If a token is rotated, update the sending application and verify another event. Check rejected payload and rate-limit responses as well as connection errors. The local and cloud targets have their own endpoint and reachability; using a cloud token with a local URL is not a valid substitute.

Related guides: reading events, storage limits.