Skip to main content
The Streaming Hub module in Lerian Console shows how the Hub delivers your events. Use it to follow delivery, read the event catalog, and manage subscriptions. Managing subscriptions covers the same subscription tasks through the API.

​
Accessing Streaming Hub

The module works only when Streaming Hub is on for your organization. An administrator turns it on in Settings > Products. See Products. Open the product launcher in Lerian Console and select Streaming Hub. The sidebar has three entries: Dashboard, Event Catalog, and Subscriptions. When Streaming Hub is off, the module pages show a notice that points to this setting.

​
Dashboard

The module opens on the Dashboard. It shows event delivery, as the Hub measured it. Select the period at the top: 1h, 6h, 24h, or 48h. The default is 24 hours. For a different window, choose Custom, then set a Start and a Duration. The start must be in the past. The dashboard shows:
  • Current state: the subscriptions at the moment of the snapshot, counted by switch, by verification state, by destination kind, and by channel.
  • Events received: the events the Hub received in the period, with a chart per hour or per UTC day. This is not a delivery count.
  • Push delivery: the delivery jobs created, and the delivery attempts by outcome, such as Delivered or Failed.
  • Push backlog: the delivery jobs waiting, and how long the oldest one has waited.
  • Pull eligibility: the events that pull consumers had the right to read, and the eligible subscription matches. The Hub does not report what a consumer read.
Under them, Needs attention lists the subscriptions that need an operator’s attention in the period. Each row shows the destination, the verification, the state, the last success and failure, and the attempt counts. The Reasons column says why the row is there, for example Automatically disabled or Destination not verified.

​
Event catalog

Event Catalog lists the events that producers advertise, and how current each one is. The page groups the events by topic. Each event shows its event key, its schema version, a description, its resource, and its source. The event key is the value that a subscription takes as an event type. Each topic shows a freshness badge for each producer, such as Refreshed or Out of date. Use Search the catalog to filter by event key, description, topic, or producer. Producers advertising no events lists the producers that the Hub sweeps but holds no events from.

​
Subscriptions

Subscriptions lists where the Hub delivers your events. The table shows Name, Destination, Type, State, Verification, and Created. Filter the list by Destination kind, Delivery, and Verification. The Console shows each destination without its path, its query, and any account identifier. The Streaming Hub holds the full address. To open a subscription, click its name.

​
Create a subscription

1

Open the form

On the Subscriptions page, click New subscription.
2

Name the subscription

Type a Name. The list shows this name.
3

Choose the destination kind

Choose Webhook if the Hub posts to your endpoint, or Pull if your service reads from the Hub.
4

Type the endpoint

For a webhook, type the Endpoint: an https address that the Streaming Hub can reach.
5

Choose the event types

Choose every event type, including the ones published later. Or choose only the event types that you select from the catalog.
6

Set the optional fields

Leave Producing application empty to receive from every producer. Leave Schema major version empty to follow the version that the Hub publishes.
7

Create

Click Create subscription.
For a webhook, the Subscription created dialog shows the signing secret. The Streaming Hub returns it exactly once. Copy it, then select I have copied the signing secret and stored it safely. Then click Verify now to send one signed request to your endpoint, or Verify later. The Streaming Hub delivers nothing to the destination until one signed request reaches it and succeeds. For a pull subscription, the Pull subscription created dialog shows the subscription ID. A pull subscription has no signing secret: your consumer authenticates with its own token. See Consuming events.

​
The subscription page

The subscription page has these cards:
  • Destination: the address, the destination kind, the delivery state, and the verification state.
  • Delivery: the switch, the event types, the producer, the schema version, the signature scheme, the plan, the creation date, and the date of the last change.
  • Credential: the credential kind, such as Cross-account role or Stored queue credential, and the last time that the signing secret changed. The Hub never returns secret material on a read, so the card cannot show it.
  • How to consume this subscription: for a pull subscription, how your service reads it.
  • Delivery health: the success rate per attempt, the last success and failure, the dead-lettered attempts, the quarantined events, the consumer lag, and the attempt outcomes.
  • Actions: the actions for this subscription.
A subscription that waits for verification shows Pending verification at the top.

​
Verify, rotate, or delete a subscription

  • Verify now sends one real signed request to your endpoint. The Console does not offer it when the subscription is active and its switch is on. It is the only action that lifts an automatic shutdown.
  • Rotate signing secret is for a webhook that holds a signing secret. The Rotate the signing secret dialog issues a new secret and shows it once. The Hub signs each delivery with both secrets until the deadline that the dialog shows. Click Rotate the secret to confirm.
  • Delete subscription stops delivery. Type the subscription name to confirm, then click Delete it. If you create a webhook subscription again, it receives a new signing secret. A pull subscription loses the position that your consumer has read up to.

​
Next steps

Managing subscriptions

Create and manage subscriptions through the API.

Consuming events

Verify signatures, deduplicate deliveries, and pull events.