Install by platform
Ruby and Rails
Install gem install blipit
Add the blipit gem (0.3.0 or newer) and call init once with your project's public key. It runs on Blipit's own core with no runtime dependencies. Unhandled exceptions are reported on their own, and Rails, Rack, Sinatra and Sidekiq are built in.
1Gemfile
gem "blipit"2Initialise at startup
Rails: config/initializers/blipit.rb; nothing else to install, because Blipit adds its Rack middleware, Active Job and Rails.error reporting on its own. Rack and Sinatra apps add use Blipit::Rack. Scripts: before your code runs. The key is on the project's Keys page. With an empty key, init prints a warning and returns false instead of raising.
Blipit.init(
key: "<public key>",
environment: Rails.env,
release: ENV["RELEASE"],
)3Get your keys
Sign in at app.blipit.io and open API keys in the sidebar, then your project. Every project has two keys. The public key starts with blipit_pk_: it goes in browser and app code, can only send events, and is safe for anyone to see. The secret key starts with blipit_sk_: it stays on your server or in Odoo, never in a browser, because it can also read and change issues. The secret key is shown only once, right after it is created, so copy it then; if you lose it, press Create a new secret key, and the old one stops working at once. Some SDKs also need the project id, shown on the same page.
4Keep the key in Rails credentials
This SDK sends with the public key. In Rails, keep it in the encrypted credentials and read it in the initializer; elsewhere, use an environment variable.
bin/rails credentials:editblipit:
key: blipit_pk_your_public_keyBlipit.init(
key: Rails.application.credentials.dig(:blipit, :key),
environment: Rails.env,
)5Keep keys out of git
Keep keys in environment variables or your host's secret settings, never in code you commit, and add your .env files to .gitignore. A public key in a web page is normal. If a secret key ever ends up in git, a public page, a screenshot or a chat, open API keys, press Create a new secret key, and paste the new key wherever the old one was used: the old key stops working straight away.
.env
.env.local
.env.*.local6Manual capture and login attempts
Login attempts need the secret key: on the server, init with the secret key instead of the public one, or ingest refuses them with 403 security_needs_secret_key. Scale plan.
Blipit.capture_exception(e)
Blipit.capture_message("cache miss rate above 50%", level: :warning)
Blipit.set_user(id: "42", email: "ana@example.com")
Blipit.capture_security("login_failed", email, outcome: "bad_password", ip: request.remote_ip, user_agent: request.user_agent)7Check it works
Open Issues in app.blipit.io. The first event appears within a few seconds, grouped into an issue, and the people in charge get an email.
Blipit.capture_message("Hello from Rails")Good to know
- Pass traces_sample_rate: 0.2 to init and requests, jobs, Net::HTTP calls and SQL queries show up on the Pulse page.
- Upgrading from 0.2: project: is no longer needed (it is still accepted), Blipit.dsn is gone, and before_send now receives the event as a Hash in Blipit's format.
- Keeping Blipit up to date: the Keeping Blipit up to date guide (docs.blipit.io/updates) explains the update banner, the emails for important releases, the notice in your development console and the update command for this platform.
- One project per app and platform: each project picks its platform when it is created (Android, iOS, React Native, Flutter, Web, Backend or Odoo), and Blipit refuses data from any other platform with a clear error, so an iOS app and an Android app need two projects with two keys. Releases, versions, crash rates and store builds differ per platform, so mixing them in one project makes all of them wrong. A Web project also takes the server side of the same web app (the Next.js server or Node), and a React Native or Flutter project also takes its own native Android and iOS crash reports.
Stuck? Email support@blipit.io. Keys and the project id for each project are under API keys in app.blipit.io.

