Alert configuration

Control which alerts appear in the Dashboard and which trigger outbound notifications

Workspace alert configuration lets you reduce noise without losing data. Each workspace has its own settings for visibility, severity filters, and per-integration (OEM) overrides.

For how alerts are stored and classified, see Alerts.

Where to configure#

Open the Texture Dashboard.
Go to Settings → Alerts (/settings/alerts).
Adjust the controls below.
Click Save to apply changes to the workspace.

Only workspace admins and owners can edit alert settings. Other members can view the current configuration in read-only mode.

Before you save for the first time#

Alert configuration is opt-in per workspace:

State	Dashboard	Notifications	Database
No saved config	All alerts visible	All alerts fan out to Destinations	Everything captured
After first Save	Filtered per your settings	Filtered per your settings	Everything captured

Until you save at least once, the platform does not apply any visibility filters—even if the form shows recommended defaults (Critical and Warning on, Info off). Those defaults are what you see in the UI before the first save; they become enforced only after you click Save.

This keeps existing workspaces backward-compatible: behavior changes only when an admin explicitly configures the workspace.

Capture vs visibility#

Configuration affects what you see and what gets notified, not what Texture stores.

Layer	Affected by config?
Ingestion and database storage	No — every alert is captured
Dashboard lists (`alerts` query, Site/Device alerts)	Yes — after first save
Destination fanout (`ALERT_CREATED`, etc.)	Yes — after first save

Hidden alerts remain available for audit, compliance, and internal operations. They are excluded from operator-facing views and external notification pipelines only.

If the platform cannot read your saved configuration (for example, a transient database error), it fails open: alerts stay visible and notifications continue until the config can be read again.

Controls#

Alert visibility (master switch)#

The Alert visibility toggle is the workspace-level on/off switch.

Setting	Dashboard	Notifications	Capture
Enabled (default)	Alerts shown subject to severity and OEM rules	Fanout subject to severity and OEM rules	Always on
Disabled	No alerts shown	No alert fanout to destinations	Always on

When disabled, a warning explains that alerts are hidden and notifications are paused, but capture continues in the background.

Severity and OEM sections are visually dimmed when the master switch is off; they remain editable so you can prepare settings before re-enabling.

Severity filters#

Choose which severity levels are included in the Dashboard and notification pipeline. Each level is an independent toggle:

Level	Typical use
Critical	Safety, outages, and conditions requiring immediate action
Warning	Degraded performance or elevated risk
Info	Informational events and lower-urgency notices

Only alerts whose severity matches an enabled level are shown and notified. For example, with Critical and Warning enabled and Info disabled, INFO alerts are captured but hidden from the UI and destinations.

Recommended starting point (pre-filled before first save):

Critical — on
Warning — on
Info — off

If you disable all three levels while visibility is enabled, no alerts appear in the Dashboard and none trigger notifications. Alerts are still captured.

UI labels vs behavior

The Dashboard may describe severity cards with phrases like "Critical + Warning." Backend filtering treats each level independently — you enable the specific severities you want, not a cumulative minimum threshold.

OEM overrides#

OEM overrides control visibility per connected integration (manufacturer). The section lists only OEMs with active system connections in the workspace.

Switch	Behavior
On (default)	Alerts from that integration are included (subject to master switch and severity)
Off	Alerts from that integration are hidden from the Dashboard and excluded from notification fanout

Overrides are keyed by manufacturer slug (for example, solaredge-web, enphase, sma) — the same identifier used when alerts are ingested. You do not need to turn integrations on explicitly; only off overrides are stored.

If no OEM connections exist, the OEM overrides section is not shown.

For provider slugs, ingestion paths, and volume quirks, see OEM alert reference. When the connection slug and stored Alert.provider differ (for example SolarEdge), confirm which key your alerts use before relying on OEM overrides.

What changes after you save#

Once configuration is saved, the same rules apply everywhere visibility is enforced:

Dashboard — Alert lists, site/device alert panels, and counts respect the saved config.
REST API — GET /v1/alerts returns only visible alerts after configuration is saved. See Alerts API.
Destinations — Webhooks, email, SMS, and Kafka forwarders do not receive ALERT_CREATED / ALERT_UPDATED for filtered alerts. Events are still archived internally. See Management API: Destinations.

Workspace alert configuration (visibility, severity, OEM overrides) is configured in the Dashboard only — there is no REST endpoint for it today.

Common scenarios#

Reduce INFO noise from OEM integrations#

Open Settings → Alerts.
Leave Alert visibility enabled.
Under severity, enable Critical and Warning; disable Info.
Save.

INFO alerts continue to be stored but no longer appear in the Dashboard or trigger destinations.

Pause all alert notifications temporarily#

Disable Alert visibility.
Save.

All alerts are hidden and destination fanout stops. Re-enable when ready—severity and OEM settings are preserved.

Hide alerts from one noisy integration#

Leave Alert visibility enabled.
Under OEM overrides, turn Off for the integration you want to suppress.
Save.

Other integrations and severities are unaffected.

Return to showing everything#

Delete filtering by saving a permissive config (all severities on, no OEM overrides off, visibility enabled), or contact Texture support if you need the stored configuration row reset for the workspace.

Permissions and workspaces#

Settings apply to the current workspace only. Switch workspaces in the Dashboard to configure each one separately.
Non-admin members see the same page in read-only mode without Save/Discard actions.

Alerts — Overview, data model, and capture principle
Alerts API — List and lifecycle endpoints (GET, POST, PATCH)
OEM alert reference — Provider slugs and ingestion quirks
Destinations — Delivering alert events to external systems