Download the PHP package oliverthiele/ot-alerts without Composer
On this page you can find all versions of the php package oliverthiele/ot-alerts. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download oliverthiele/ot-alerts
More information about oliverthiele/ot-alerts
Files in oliverthiele/ot-alerts
Package ot-alerts
Short Description OT Alerts - Alert management for TYPO3 extensions — Pushover notifications with rate limiting
License GPL-2.0-or-later
Homepage https://www.oliver-thiele.de/
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package ot-alerts
ot_alerts — Alert Management for TYPO3 Extensions
Centralised alert proxy for TYPO3 extensions — sends Pushover push notifications
with built-in
rate limiting and deduplication. Other extensions simply call
AlertManager::notify() and
AlertManager::resolve(); ot_alerts handles throttling, state tracking, and
channel dispatch.
Features
- Pushover push notifications via REST API with HTML formatting
- Event key and occurrence count visible in every notification
- Optional tappable link button in Pushover (via
context['url']) - Rate limiting: first occurrence triggers immediately, then once per configurable reminder interval
- State machine: NEW → NOTIFIED → RESOLVED — resolved errors trigger fresh notifications when they reappear
- DB-backed event log (
tx_otalerts_events) for audit trail and future backend module - Optional integration: inject
?AlertManagervia constructor — ot_alerts is not a hard dependency, the service is simplynullwhen not installed - Configurable reminder interval via TYPO3 Extension Configuration, with optional per-alert override
- Transactional notifications:
throttle: falsedelivers every single time, bypassing rate limiting completely
Requirements
| Requirement | Version |
|---|---|
| TYPO3 | ^13.4 || ^14.0 |
| PHP | ^8.4 |
| guzzlehttp/guzzle | ^7.0 |
Installation
After installation, run database schema update:
Configuration
Environment Variables
Add the following to your .env file:
Both values are available in your Pushover dashboard.
Extension Configuration
Configure in the TYPO3 backend under Admin Tools → Settings → Extension Configuration → ot_alerts:
| Key | Type | Default | Description |
|---|---|---|---|
reminderInterval |
int | 3600 |
Seconds between reminder notifications (1 hour) |
pushoverEmergencyRetry |
int | 60 |
Seconds between retries for CRITICAL alerts (min 30) |
pushoverEmergencyExpire |
int | 3600 |
Seconds until Pushover stops retrying (max 10800) |
Usage
Optional dependency via constructor injection
The recommended integration pattern uses TYPO3's Symfony DI container. Declare
?AlertManager
as a nullable constructor parameter — when ot_alerts is not installed, the
container injects
null and all calls are silently skipped via the null-safe operator:
No class_exists() guard or GeneralUtility::makeInstance() needed — the
container resolves
the optional service automatically.
Sending an alert
Sending an alert with a URL
Pass context['url'] to add a tappable link button to the Pushover
notification.
This is useful to open the affected page directly from the push:
Sending an alert with a per-alert reminder interval
Pass reminderInterval to override the global extension configuration for this
specific alert. Useful when certain events need a shorter or longer throttle than
the global default:
Sending a transactional notification
Not everything worth a push is an error. A submitted form, a completed import, an incoming order — these are events that carry their own occasion and have to be delivered every single time. Rate limiting would silently swallow the second one within the reminder interval.
Pass throttle: false for those. AlertManager then skips the rate limit and the
event status entirely, and the occurrence counter is left out of the message,
because it describes a condition that keeps repeating:
notify() reports these dispatches as reason: notification. The event row is
still written, so the log keeps last_message, last_occurrence and the total
count — you just do not get them pushed to your phone.
NOTICE is the matching severity: audible like WARNING, but the title reads
[NOTICE] my_extension and does not claim that something is wrong.
Resolving an alert
Call resolve() once the error condition is no longer present. This resets the
state so the
next occurrence will trigger a fresh notification immediately.
Notification format
Pushover messages use HTML formatting for readability:
Severity levels and Pushover priorities
| Severity | Pushover priority | Behaviour |
|---|---|---|
INFO |
Low (-1) | Quiet notification, no sound |
NOTICE |
Normal (0) | Default sound and vibration — nothing is wrong, just worth knowing |
WARNING |
Normal (0) | Default sound and vibration |
ERROR |
High (1) | Bypasses quiet hours |
CRITICAL |
Emergency (2) | Repeated every pushoverEmergencyRetry seconds until acknowledged |
Emergency notifications (CRITICAL) require acknowledgement in the Pushover app.
Notification behaviour
With throttle: false none of this applies — every notify() pushes.
CLI
Test notification
Verify that Pushover credentials are configured and a push is delivered:
Send with a specific severity:
Reset the rate limit after the test so the next real error triggers immediately:
Dispatch as a transactional notification, the way throttle: false does — no rate
limiting, and the rate limit of the real events stays untouched:
Show per-channel dispatch result including HTTP status:
Show the raw Pushover API response body (full debug output):
If the alert was previously sent and the reminder interval has not yet elapsed,
the command shows [WARNING] Rate limit active. Use --resolve to bypass:
the command pre-resolves the event before sending (so the rate limit is skipped)
and post-resolves after (so the next test also sends immediately).
The command shows which ENV variables are present, dispatches the alert, and prints the result.
License
GPL-2.0-or-later — © 2025 Oliver Thiele
