Rollbar

Rollbar

This connector works with Rollbar error monitoring through the REST API (https://api.rollbar.com/api/1): items (grouped errors and messages) with their history and occurrences, dashboard reports and the Metrics API, deploys, environments and code versions, RQL queries, and the account's projects, users and teams. It can resolve, mute, reassign, snooze and retitle items, comment on them, report deploys and run RQL queries.

Setup (3 minutes) Rollbar has two kinds of access token, and which one you paste decides what the connector can reach:

• A project access token (project, Settings, Project Access Tokens) reaches one project. Give it the read scope for the reads, write to change items, and post_server_item to report deploys. It cannot list projects, users or teams.
• An account access token reaches the whole account: a service token (account Settings, API Access Tokens, Service tab) for every project, or a personal access token (User Settings, Personal access tokens) that can do only what its user can do. Scopes are read and write. On project tools pass project_id (from rollbar_list_projects); rollbar_list_items searches all projects unless you pass project_ids. Only a personal access token can comment on items. Paste the token into ROLLBAR_ACCESS_TOKEN and run rollbar_list_items to check it.

Workflow

• What is broken: rollbar_get_top_active_items (last 24 hours), rollbar_list_items with status: ["active"] and level: ["error", "critical"], then rollbar_get_item. A number from a Rollbar URL (#123) is a counter: resolve it with rollbar_get_item_by_counter.
• Investigate: rollbar_list_item_occurrences, then rollbar_get_occurrence for the full stack trace; rollbar_list_occurrences for the latest events of the whole project; rollbar_list_item_events for who changed what.
• Triage: rollbar_update_item (resolve with resolved_in_version, mute, change level or title, assign with ids from rollbar_list_users or rollbar_list_teams, snooze), rollbar_add_item_comment.
• Trends: rollbar_get_occurrence_counts, rollbar_get_activated_item_counts, rollbar_get_item_metrics, and on the Advanced plan rollbar_query_occurrence_metrics (filters, group_by, aggregates) and rollbar_get_resolution_time_metrics.
• Releases: rollbar_list_deploys, rollbar_get_deploy, rollbar_report_deploy and rollbar_update_deploy; rollbar_list_environments; what a release broke: rollbar_get_version and rollbar_list_version_items with event: new.
• Ad hoc analysis with RQL: rollbar_create_rql_job, poll rollbar_get_rql_job until status is success, then rollbar_get_rql_job_result. rollbar_list_rql_jobs and rollbar_cancel_rql_job manage them.
• Account: rollbar_list_projects, rollbar_get_project, rollbar_list_users, rollbar_get_user, rollbar_list_teams.
• Privacy requests: rollbar_request_person_deletion (switched off by default; erases a tracked person everywhere) and rollbar_get_person_deletion_status.

Reading the answers: every answer is {"err": 0, "result": ...}; err: 1 comes with a message. rollbar_report_deploy answers {"data": {"deploy_id": ...}}. All timestamps are Unix seconds in GMT. An item has a system-wide id (used by these tools) and a per-project counter (shown in URLs). Item status is active, resolved, muted or archived; level is debug, info, warning, error or critical. Occurrence lists leave out request headers, cookies and notifier details; rollbar_get_occurrence returns the full payload, which may contain personal data of your end users.

Paging: items come 100 per page; occurrences, deploys, environments and events 20 per page by default (limit up to 5000 where offered); pass page from 1. Occurrence lists also page with last_id. total_count is null on projects with more than 100,000 items.

Errors: 401 means a missing or malformed token; 403 a token that is disabled, lacks the scope, is a project token on an account endpoint, or (Requires project access) an account token without a usable project_id; 404 an unknown id or another account's; 422 invalid parameters; 429 the token's rate limit (see X-Rate-Limit-Remaining).