Next: Configuring notifications, Previous: Creating your project, Up: The Telebugs Manual [Contents]

7 Sending your first error report ¶

Now that your project is configured, it’s time to send your first error report. This chapter walks you through the steps needed to connect your app to Telebugs by integrating a Sentry SDK. Once completed, Telebugs will begin receiving and displaying error reports from your app automatically.

Introduction to error reports ¶

These reports are sometimes called exceptions, crashes, or stack traces. There are subtle differences between these terms, but most software developers use them interchangeably. In Telebugs, we refer to them as error reports because that’s the format you, the user, will consume in the UI.

Viewing installation instructions ¶

If a project has no errors reported yet, Telebugs shows SDK installation instructions instead.

These instructions include a link to the official Sentry documentation, tailored to the platform you selected during project creation.

For example, if you selected Ruby on Rails in the New Project form, Telebugs will link you to Ruby on Rails Sentry SDK instructions.

Installing the Sentry SDK ¶

Follow the Sentry instructions relevant to your platform to install the SDK. Here’s a quick example for Ruby on Rails:

# Gemfile
gem "sentry-rails"

# Then run:
$ bundle install

Next, configure Sentry with the DSN provided by Telebugs:

# config/initializers/sentry.rb
Sentry.init do |config|
  config.dsn = "https://[email protected]/123"

  # Get breadcrumbs from logs.
  config.breadcrumbs_logger = [:active_support_logger, :http_logger]

  # Add data like request headers and IP for users, if applicable;
  # see https://docs.sentry.io/platforms/ruby/data-management/data-collected/ for more info
  config.send_default_pii = true
end

Using your Telebugs DSN ¶

Telebugs generates a unique DSN for each project. Copy this DSN from your project page and use it in your SDK configuration. The DSN tells Sentry where to send error data. Telebugs will listen in and collect this data for you.

Feature compatibility notes ¶

Disable any features related to Tracing, Profiling, Session Replay, or Performance Monitoring. Telebugs doesn’t support these and will ignore related settings. Features specifically related to error tracking, such as breadcrumbs and context data, are recommended.

Common mistakes and troubleshooting ¶

The SDK is installed, but nothing shows up: Make sure your app is actually raising an error. You can trigger a test one manually:
```
raise "Test error to verify Sentry setup"
```
"Invalid DSN" errors: Double-check that you copied the full DSN from the Telebugs dashboard.
App changes not picked up: Don’t forget to restart your app after adding or changing the SDK configuration.

Next steps ¶

Once your first error is received, Telebugs will stop showing installation instructions and begin displaying real-time error data. The dashboard updates automatically — you don’t need to refresh the page or restart anything.

From here, you can:

View error details and stack traces
Share or resolve issues

Glossary ¶

Error report: A record of an unexpected failure in your app, usually including a stack trace and metadata.
DSN: Data Source Name. A unique URL-like identifier that tells the SDK where to send captured error events.
SDK: Software Development Kit. Code you install into your app that reports errors to a service like Sentry (and in turn, Telebugs).
Breadcrumb: Contextual log entries that help explain what led to an error.
Platform: The technology stack your project uses: e.g., Ruby on Rails, Node.js, React.