Oban Releases

📊 Charts

Charts for realtime metrics are enabled out of the box without any external dependencies. Charts are helpful for monitoring health and troubleshooting from within Oban Web because not all apps can, or will, run an extra timeseries or metrics database. And, because they’re displayed alongside the original jobs, you can identify outliers in aggregate and then drill into individual jobs.

Highlights

• Select between execution counts, full counts, execution time, and wait time
• Aggregate time series by state, node, worker, or queue label
• Rollup metrics by time from 1s to 2m, spanning 90s to 3h of historic data
• Measure execution and wait times across percentiles, from 100th down to 50th at standard intervals

🔍 Filtering

Filtering is entirely overhauled with a new auto-complete interface, new qualifier syntax, and vastly more performant queries. Full text searching with unindexable operators such as ilike and tsvector was removed in favor of highly optimized exact-match queries. With the new query syntax all searching is faster, and searching nested args is over 100x faster thanks to index usage.

One additional performance improvement for large oban_jobs tables is threshold querying. In order to minimize load on the application’s database, only the most recent 100k jobs (approximately) are filtered. The 100k limit can be disabled or configured for each state, i.e. you could restrict filtering completed jobs but access the full history of cancelled jobs.

Highlights

• Filter by args, meta, node, priority, queue, tags, and worker
• Typeahead with keyboard shortcuts for focusing, selecting, and completing suggestions
• Highly optimized suggestion queries across a configurable number of recent jobs
• Locally cached for immediate feedback and minimal load on your application database
• Auto-completion of nested args and meta keys and values at any depth

⏱️ Metrics

The foundation of charts, filtering, optimized counts, and realtime monitoring is the new Oban.Met package. It introduces a distributed time-series data store and replaces both Oban.Plugins.Gossip and Oban.Web.Plugins.Stats with zero-config implementations that are much more efficient.

Highlights

• Telemetry powered execution tracking for time-series data that is replicated between nodes, filterable by label, arbitrarily mergeable over windows of time, and compacted for longer playback.
• Centralized counting across queues and states with exponential backoff to minimize load and data replication between nodes.
• Ephemeral data storage via data replication with handoff between nodes. All nodes have a shared view of the cluster’s data and new nodes are caught up when they come online.

In the future Oban.Met modules will be public, documented, and available for use from your own applications.

❤️‍🩹 Deprecations

• The Oban.Web.Plugins.Stats plugin is no longer necessary and you should remove it from your plugins:

  plugins: [
  - Oban.Web.Plugins.Stats,
  ...

• The Oban.Plugins.Gossip plugin is no longer necessary and you should remove it from your plugins:

  plugins: [
  - Oban.Plugins.Gossip,
  ...

Changes

• Require a minimum of Elixir v1.13 for compatibility with features required by oban_met

• Require a minimum of Phoenix v1.7 to support verified routes.

• Require a minimum of Phoenix LiveView v0.19 for various features and bug fixes.

Enhancements

Navigation

• [PubSub] Indicate when PubSub isn’t connected or receiving notifications with a warning and explanation

• [Refresh] Persist refresh selection between sessions and resume the most recent value after pausing on window blur

• [Themes] Support selecting light, dark, or system theme via a dropdown menu

• [Shortcuts] Introduce keyboard shortcuts modal that’s accessible by pressing ?

• [Shortcuts] Add shortcuts to toggle refreshing, cycle themes, focus search, and navigate between pages

Charts

• Display canvas based charts for exec count, full count, exec time, and queue time

• Restore chart options on page reload, including whether it’s collapsed

• Indicate which filters are applied when charts are filtered

• Limit plotting large series, e.g. queues or workers to the 7 highest activity series. Without limitation charts are slow and unreadable.

• Estimate counts and times to a fixed size with a unit suffix

Jobs Page

• Restrict filtering and searching to a configurable maximum number of jobs. The default is 100k, which can be disabled or customized with a resolver callback.

• Calculate all relative timestamps on the client to minimize updates over the wire

• Reimplement jobs list view with simpler components without per-column sorting for better performance.

• Use a dropdown menu for job sorting to more clearly indicate which field is used for sorting and the sort direction.

• Orphans, jobs stuck in an executing state, are now marked with an status indicator

Sidebar

• Elevate “States” to the top of the sidebar and visually clarify that they’re for navigation while “Nodes” and “Queues” are filters.

• Always display a standard toggle icon rather than showing one on hover

• Use counts reported by oban_met. Counts are only reported by a single node and larger queue/state combinations are counted with exponential backoff.

• Removed from the queues page to maximize table space

• Reduce param tracking and Use patch rather than navigate on links for filter changes without a full update

Resolver

• Add jobs_query_limit/1 callback to control the maximum number of jobs to query when filtering, searching, or generally listing jobs

• Add hint_query_limit/1 callback to control the number of recent jobs to search for auto-complete hints.

Bug Fixes

• [Queues] Correctly handle toggling global limits on and off

• [Queues] Track global limit changes on edit without requiring increment or decrement

• [Web] Prevent lingering tooltips by by destroying instances on unmount

Bug Fixes

• [Assets] Correctly resolve assets directory across all build environments.

  A change to loading assets dynamically at runtime broke path resolution in release builds.

Bug Fixes

• [Assets] Inline assets and track them as external resources rather than loading on them at runtime.

Enhancements

• [Resolver] Prevent dashboard access with :forbidden access

  The dashboard now offers authentication by checking access on mount via resolve_access/1. Returning {:forbidden, path} will halt mounting and redirect to the specified path.

  By combining resolver_user/1 and resolve_access/1 callbacks it’s possible to build an authenticaiton solution around the dashboard. For example, this resolver extracts the current_user from the conn’s assigns map and then scopes their access based on role. If it is a standard user or nil then they’re redirected to /login when the dashboard mounts.

  defmodule MyApp.Resolver do
    @behaviour Oban.Web.Resolver
  
    @impl true
    def resolve_user(conn) do
      conn.assigns.current_user
    end
  
    @impl true
    def resolve_access(user) do
      case user do
        %{admin?: true} -> :all
        %{staff?: true} -> :read_only
        _ -> {:forbidden, "/login"}
      end
    end
  end

• [Jobs] Change default sort direction for completed states

  Completed, cancelled, and discarded states used an unintuitive sort preference with oldest jobs first. Now it’s restored to the historic ( and more intuitive) order of newest jobs first.

• [Deps] Loosen constraints to allow Phoenix LiveView v0.20 and above

• [Deps] Require a minimum of Oban Met v0.1.2 and above

Bug Fixes

• [Chart] Correct count estimation for values between 1k and 10k

• [Job Details] Make detail times relative on demand.

  Job details always showed - because the old relative_ timestamp fields were removed. Now details show the correct relative timestamp, including a fix to correctly show the timing and duration for completed jobs.

• [Chart] Use sum for exec counts and max for full counts to display accurate information when rolling up values by periods greater than 1s. Previously, full counts were summed across time windows.

Enhancements

• [Jobs] Append and submit filter suggestions on click

  Previously, clicking a suggested value injected it into the input but didn’t submit it as a filter. That was unexpected, and led to an odd “deletion” of previous values when typing multiple filters at once. Clicking on a suggested value immediately submits it as a filter now.

• [Jobs] Improved json path suggestions

  Auto submission exposed an issue with json path completion, i.e. path suggestions lacked a final : or . to indicate if it was a full qualifier or part of a path. Now it’s clear whether an args or meta suggestion is part of a nested object path (.), or a final key (:).

• [Jobs] Add filtering by a list of ids, e.g. ids:1,2,3

  It turns out this is a commonly used feature, especially in a staging environment and by testing teams.

Bug Fixes

• [Resolver] Only use a conservative query limit for completed jobs

  Due to the loose application of threshold queries, the 100k limit caused confusion for other states with only a handful of jobs, e.g. retryable. Now the limit is only applied to completed jobs by default and :infinity for all other states.

• [Jobs] Parse entire term as an integer when filtering

  Values, such as UUIDs that start with a digit, were incorrectly considered an integer and couldn’t be used in filtering.

• [Job Details] Prevent cancelled/discarded jobs showing completed

  The timeline component incorrectly displayed jobs that weren’t completed or executing as completed.

Bug Fixes

• [Resolver] Mount resolvers without an optional resolve_access/1 callback defined.

• [Query] Prevent to_existing_atom/1 errors when querying jobs by ensuring job state atoms are loaded before any jobs run.

• [Query] Correct appending filter choices with both a qualifier and dot separator.

  Clicking or tab completing a qualified term and a dot would incorrectly construct a compound term. Now, completing a partial filter like workers:MyApp.Al correctly returns workers:MyApp.Alpha instead of the broken workers:MyApp:MyApp.Alpha.

• [Job Details] Prevent cancelled and discarded icons from rotating in completed state

Enhancements

• [Jobs] Use the queue producer’s uuid when checking for orphaned jobs

  The node alone isn’t accurate enough to indicate orphans because queues may start, stop, or crash unexpectedly. Now that all engines include the uuid as part of the attempted_by array, we can reliablity use it to detect orphaned jobs.

• Support using phoenix_html 4.0

  The latest release Phoenix.HTML removes the top-level use macro and some common functionality. This changes allows using the older v3.3 release or v4.0, with the necessary internal changes to handle either.

This release requires Oban v2.17.4 or greater to support the new Notifier.status/1 connectivity check.

Enhancements

• [Dashboard] Display a connectivity indicator for isolated or solitary nodes.

  The previous connectivity status didn’t work for the PG notifier because the local node is always connected. This uses Oban’s new Notifier.status/1 check to enhance the status to indicate more subtle disconnected statuses with more information:

  • Isolated (no messages from any node)
  • Solitary (only messages from the local node)

• [Queues] Add “Pause All” and “Resume All” buttons.

  Add pause all and resume all functionality to queues page, with updated components and styling for individual pause and resume buttons.

  The buttons emit new pause_all_queues and resume_all_queues telemetry events.

• [Queue Detail] Add global queue partitioning controls.

  It’s now possible to view and edit global_limit partitions identically to rate_limit partitions from the queue details page. This also contains a subtle fix to selecting the “Worker

  • Args” partitioning scheme to prevent crashes.

• [Jobs] Indicate when filtered results are limited and link directly to the filtering jobs for reference.

• [Jobs] Show different icons to indicate when a queue is paused on “all nodes” and “some nodes”.

• [Jobs] Require confirmation before bulk deleting jobs.

  Bulk deleting jobs now requires a confirmation step like individual deletion. In addition, bulk operation labels are more descriptive to make it clear they’re operating on “jobs” and not the selection.

• [Jobs] Jobs rescued by the DynamicLifeline plugin have an icon indicator similar to orphans.

  Now it’s possible to identify rescued jobs on the dashboard. The status is based on rescued metadata added in the recently released Oban Pro v1.3.5.

• [Resolver] Add format_recorded/2 resolver callback to customize recorded output wherever it is displayed.

  This callback is similar to format_job_args/1, but it accepts both the recorded binary and the job to help augment the output. Now it’s possible to format recorded output just like args or meta.

• [Resolver] Expose decode_recorded/2 helper to format recorded.

  The new helper makes it possible to decode recorded values without the :safe flag applied.

Bug Fixes

• [Jobs] Gracefully handle bulk operations without any jobs.

  After an update a previously selected row may be removed from the page before a bulk operation (cancel, retry, delete, etc.) could be applied. Now that is safely ignored rather than causing a pattern match error.

• [Queues] Fix sorting the queues table by available status.

  Sorting was based on old counts and broke when any queue lacked available jobs.

• [Tooltips] Update tooltip labels after the initial render.

Enhancements

• [Jobs] Allow sorting jobs by the number of attempts.

  Sorting by the attempt column can help highlight jobs that fail and accumulate retries.

• [Router] Accept additional on_mount hooks to oban_dashboard

  You can provide a list of hooks to attach to the dashboard’s mount lifecycle. Additional hooks are prepended before Oban Web’s own Authentication. For example, to run a user-fetching hook and an activation checking hook before mount:

  scope "/" do
    pipe_through :browser
  
    oban_dashboard "/oban", on_mount: [MyApp.UserHook, MyApp.ActivatedHook]
  end

Bug Fixes

• [Chart] Display the correct time labels on the chart’s x-axis.

  Now the labels correctly reflect the current slice increment (e.g. 2s, 5s, 10s), rather than always counting by 1s.

• [Dashboard] Set default params before every page render, even when defaults aren’t needed.

  Occasionally, missing default params cause a missing key error when navigating from a job’s detail view back to the main page. As a precaution, we now set defaults in the detail clause as well.

• [Jobs] Safely parse search qualifiers like args without a trailing colon.

  Now parsing an args path without a trailing period or search term is considered empty rather than falling through and raising a match error.

Relax the Oban dependency to allow v2.17.4+ or v2.18.0+