Notification Tags

Every notification carries a type and a tag, so you can tell where it came from at a glance.

Source	Type	Tag
Uptime checker (down or recovery)	INTERNAL	internal
Pushed with a token named sso log	EXTERNAL	sso log
Pushed with a token named jenkins logs	EXTERNAL	jenkins logs
Pushed with any other token	EXTERNAL	the token's name

How external tags are chosen

The tag is the name of the token used to push the notification. You do not send the tag in the request body. Create one token per source and name it clearly:

sso log        → login events from your SSO service
jenkins logs   → build results from Jenkins
nightly backup → output of a cron job

Renaming is not supported. To change a tag for future notifications, create a new token with the new name and revoke the old one. Existing notifications keep their original tag.

Levels

Independent from the tag, each notification has a severity level:

Level	Use for
info	General information.
success	Something finished successfully, or a site recovered.
warning	Something needs attention soon.
error	Something failed, or a site is down.

Filtering

On the Notifications page, the filter tabs are All, internal, and one tab per tag you have used. You can also filter by level.

Message format

Telegram and email messages always begin with the tag:

🏷️ [jenkins logs] Build Failed
━━━━━━━━━━━━━━━━━━━━━━
• Event: Production deployment #412 failed during test execution.
• Level: 🔴 ERROR
• Timestamp: 2026-10-25 01:12:15 UTC
• Channel: External Push API