Official package · Frameworks

Your Hibira usage on the Laravel Pulse dashboard

A Pulse card that shows connections, messages and data sent next to your plan’s limits, a chart that follows Pulse’s period picker, and the busiest channels right now.

Packagist versionLicense

hibira-io/pulsePackagist ↗GitHub ↗

Fastest way: one prompt with the Hibira plugin

Install the plugin in your AI coding agent and paste the prompt. The agent signs you in, creates a free app if you need one, writes the code and sends a test event. GitHub ↗

  1. Install the plugin

    claude plugin marketplace add hibira-io/agent-plugin
claude plugin install hibira@hibira

  2. Paste this prompt

    Add Hibira Laravel Pulse (hibira-io/pulse) to this project.
Follow https://hibira.io/guides/pulse, adapted to how this project is already set up.
If I have no Hibira app yet, create a Free one that allows http://localhost so I can test right away.
Keep the app key and secret in environment variables, add placeholders to .env.example, and never commit real values or send the secret to a browser.
When you are done, send a test event, show me it arriving, and list the files you changed.

Prefer to do it by hand? These are the steps below:

  1. Install
  2. Set it up
  3. Use it

Other AI tools and what the plugin includes →

  • Connections now and the period’s peak against your plan’s limit, and today’s messages against the daily limit, so you see a limit coming before your users do.
  • The busiest channels by subscriber count, read from the Channels HTTP API with your app key and secret.
  • Nothing is recorded into Pulse’s tables: each reading comes from Hibira and is cached for 60 seconds.
The Hibira card on a Laravel Pulse dashboard: 220 connections now of 500 on the plan, 350,000 messages today, 13 MB sent in the past hour, a chart, and the busiest channels.
The Hibira card on a Laravel Pulse dashboard: 220 connections now of 500 on the plan, 350,000 messages today, 13 MB sent in the past hour, a chart, and the busiest channels.

Sign in to see these snippets with your own cluster host. Sign in

  1. Install

    composer require hibira-io/pulse

  2. Set it up

    # A personal API token with read access, from https://hibira.io/portal/api-tokens
HIBIRA_API_TOKEN=hkb_pat_...
HIBIRA_APP_ID=YOUR_APP_ID
# Optional: the key and secret turn on the channel list
HIBIRA_APP_KEY=YOUR_APP_KEY
HIBIRA_APP_SECRET=YOUR_APP_SECRET

  3. Use it

    {{-- resources/views/vendor/pulse/dashboard.blade.php --}}
<x-pulse>
    <livewire:hibira.usage cols="6" rows="2" />
    ...
</x-pulse>

Before you start

  • Restrict the API token to this one app and give it read access only: the card never changes anything.
  • Run php artisan vendor:publish --tag=pulse-dashboard first if your app has no Pulse dashboard view yet.

Use the app key from your dashboard; the secret stays on your server. Channels, events and authorization endpoints work exactly as they do with Pusher. Create your free account →