Error Monitoring

Configure Rollbar error tracking for Jitera Self-Hosted services

Jitera Self-Hosted integrates with Rollbar for real-time error tracking, alerting, and diagnostics across all application services. Rollbar captures unhandled exceptions, errors, and log messages from both server-side and client-side code.

Rollbar is optional. If no tokens are configured, error monitoring is simply disabled — it does not affect the operation of Jitera.

---

How It Works

Jitera injects Rollbar tokens and environment identifiers into each service at deploy time. When an error occurs, the service reports it to Rollbar with context including the service name, environment, stack trace, and request metadata.

Service	Token Source
Automation (Rails)	credentials.rollbar.post_server_item_access_token
Frontend	credentials.rollbar.post_client_item_access_token
Frontend Core	credentials.rollbar.post_client_item_access_token
Ultron	credentials.rollbar.post_server_item_access_token
Boost	credentials.boost.JITERA_BOOST_ROLLBAR_ACCESS_TOKEN

Server token (post_server_item_access_token) is used by backend services (Automation, Ultron). It has write access to report errors from server-side code.

Client token (post_client_item_access_token) is used by frontend services (Frontend, Frontend Core). It has limited permissions suitable for client-side JavaScript running in the browser.

Boost token (JITERA_BOOST_ROLLBAR_ACCESS_TOKEN) is a separate token for the Boost service, configured independently from the shared Rollbar credentials.

---

Prerequisites

1. Create a Rollbar account and a project for your Jitera deployment
2. Generate the following three access tokens from your Rollbar project settings. Each must be a distinct token — they serve different roles with different permission levels:
   • A post_server_item token — used by backend services (Automation, Ultron)
   • A post_client_item token — used by frontend services (Frontend, Frontend Core), with limited permissions suitable for browser-side code
   • A separate token for Boost — the Boost service uses its own token, configured independently

For detailed instructions on creating tokens, see the Rollbar access tokens documentation.

---

Configuration

Rollbar Tokens

credentials:
  rollbar:
    post_server_item_access_token: "<ROLLBAR_SERVER_TOKEN>"   # Backend services (Automation, Ultron)
    post_client_item_access_token: "<ROLLBAR_CLIENT_TOKEN>"   # Frontend services

  boost:
    JITERA_BOOST_ROLLBAR_ACCESS_TOKEN: "<ROLLBAR_BOOST_TOKEN>"  # Boost service

Environment Names

Each service reports its environment name to Rollbar, which allows you to filter errors by deployment stage (e.g., production, staging). The defaults are set to production:

frontend:
  env:
    ROLLBAR_ENV: production

frontend_core:
  env:
    VITE_ROLLBAR_ENVIRONMENT: production

ultron:
  env:
    ROLLBAR_ENVIRONMENT: production

boost:
  env:
    JITERA_BOOST_ROLLBAR_ENVIRONMENT: production

The Automation service reads ROLLBAR_ENV from the same credentials config as the Frontend. If you need a different environment name for Automation, it can be overridden via automation.env.ROLLBAR_ENV.

For the complete list of Rollbar-related Helm parameters, see the credentials.rollbar section in the Helm Values Reference.

---

Verification

After deploying with Rollbar tokens configured:

# Verify tokens are injected into Automation
kubectl exec -it deploy/jitera-automation-rails -n jitera -- \
  cat /app/config/secrets.yml | grep rollbar

# Verify Boost token
kubectl exec -it deploy/jitera-boost -n jitera -- \
  env | grep ROLLBAR

# Verify Ultron environment
kubectl exec -it deploy/jitera-ultron -n jitera -- \
  env | grep ROLLBAR

Then trigger a test error in the application and confirm it appears in your Rollbar dashboard.

---

Network Requirements

Rollbar requires outbound HTTPS access to api.rollbar.com:443 from your cluster. See the “3rd Party Integrations” table in Network and Firewall for the complete list of required outbound rules.