Early Access Apache Pulsar 5.0 on StreamNative Cloud. Be among the first to try the future of streaming.

Request Early Access >

StreamNative Introduces Lakestream Architecture and Launches Native Kafka Service

Read Announcement > Sign Up Now >
StreamNative Logo
BlogJun 16, 2026

Introducing StreamNative Cloud finer-grained Alerting

Introducing StreamNative Cloud finer-grained Alerting

Written by

Baodi ShiPlatform Engineer at StreamNative

Topics

StreamNative CloudAnnouncementsObservabilityFunctions

Earlier this year, we launched StreamNative Cloud Notifications with a simple on/off model for Functions alerting. Today, we're taking a major step forward: fine-grained alert rule management. You can now create, configure, and manage individual alert rules with precise control over scope, targets, and recipients---all from the StreamNative Cloud Console.

Overview

The original notifications feature lets you enable or disable a rule for your entire organization. That was a good start, but we heard from teams who needed more: alert different people for different clusters, watch a specific function without noisy org-wide rules, or configure separate rules for production versus staging environments.

With this release, notifications are no longer just a global switch. Each alert rule is now a first-class object you create, name, and configure independently.

When creating a rule, you choose how broadly it applies:

  • Organization --- monitors all matching resources across your entire org
  • Instance --- scoped to a specific Pulsar instance
  • Cluster --- scoped to a specific cluster within an instance
  • Tenant / Namespace / Function --- drill all the way down to an individual function

This means your on-call team gets only the alerts relevant to their service, not everything happening across the organization.

Each rule now has its own Receivers field. You can specify one or more email addresses (comma-separated) to receive notifications for that specific rule. Different rules can notify different people---no more routing everything to a single inbox.

Alert Templates

Alongside the expanded control model, we're also adding a new alert template: API Key Expiration. This rule fires when an API key is within 7 days of expiring, and can be filtered by service account so you only get notified for the keys you care about.

Available Alert Templates

TemplateServiceConditionSeverity
Function OOMKilledFunctions / ConnectorsA container has been OOMKilled 2 or more times in the last 15 minutes.error
Function CrashLoopBackOffFunctions / ConnectorsA pod has been in CrashLoopBackOff status for 5 minutes.error
API Key ExpirationAPI KeyAn API key is about to expire within 7 days. Filterable by service account.warning
BookKeeper Disk UsageBookKeeperCluster disk is projected to be full within 2 days.warning

Get Started

Sign up for a trial and get started for free. Leverage the resources to learn more about StreamNative Cloud. Visit your StreamNative Cloud Console and view and learn more about the notifications functionality.

Happy streaming!

About author

Baodi Shi

Baodi Shi Baodi is a platform engineer at StreamNative. He once worked in a fintech company for 5 years, mainly responsible for middleware development. His work focuses on event sourcing, domain-driven design, and real-time computing.

newsletter

Keep up with Our Stream

Insights, news, and updates from the heart of our community.

Sign up successful

Welcome to the Stream!

Thank you for your interest. We've sent a confirmation link to your email.