FTPI 1660: Setup Monitoring Service and Tests up to PHP 8.4

[Abraham-Flutterwave]

feat(monitoring): add monitoring service.

📋 Summary

Signoz Service Telemetry

🧪 Testing

• Event sent when /health/ready returns status: ok (probe carries x-api-key)
• Health result cached — two events produce one probe and two POSTs
• Event dropped and failure recorded when status is degraded
• Exactly 3 POST attempts on persistent 503, counted as one breaker failure
• No retry on non-503 errors (verified with 422)
• Circuit opens after 3 consecutive failures; subsequent sends make zero HTTP calls
• Successful send resets failure count and open-until timestamp
• Open circuit shared via PSR cache blocks all HTTP across workers
• app.created sequence updated: merchant lookup → health probe → event POST
• All static state reset in setUp/tearDown to prevent cross-test leakage

✅ Checklist

• Code follows the project coding style
• All exceptions swallowed in the telemetry path (never breaks payments)
• No secrets committed — API key remains the %%SIGNOZ_API_KEY%% build placeholder
• Unit tests added/updated and passing locally
• Backwards compatible — no public API or constructor signature changes
• Verified against staging SigNoz instance
• Changelog entry added

📦 Breaking changes

None. Constructor signature, public methods, and event payloads are unchanged.

---

Signed-off-by: Abraham Olaobaju abraham@flutterwavego.com

[wiz-f83cb90411]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	15  1  1
SAST Findings	-
Software Management Findings	-
Total	15  1  1

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try using Wiz Code VS Code Extension.

[gitguardian]

⚠️ GitGuardian has uncovered 3 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
4465424	Triggered	Generic High Entropy Secret	e8dfd50	assets/js/v3.js	View secret
33875719	Triggered	Generic High Entropy Secret	4d1e1ce	src/Monitoring/SignozServiceLogger.php	View secret
33875719	Triggered	Generic High Entropy Secret	d7b1839	src/Monitoring/SignozServiceLogger.php	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}