Application incidents
Let your applications report failures through the Web API. Keep the system, module, platform, and description together.
- Company client credentials
- Direct API or gateway delivery
- One place for reported incidents
MONITOR. NOTIFY. RESOLVE.
Real-Time Issues Tracking and AI-generated solutions.
A system to monitor and manage issues generated by all company applications, providing real-time notifications and AI-generated solutions.
Named IP monitoringGateway retriesMobile push alerts
ISSUES CLOUD DASHBOARDExample
Your incidents, at a glance.
A clear view from detection to resolution.
Resolution progress42%
Open incidents7
Closed incidents5
Total incidents12
Incident activity Open Closed
6 weeks agoThis week
Recent incidentsAll incidents
Open
Application serverNetwork / Ping Monitor
Closed
Email deliveryNotifications / Gateway
Open
Payment processingOrders / Checkout
ONE CONNECTED WORKFLOWPing MonitorNotification GatewayIssues Cloud APIWeb & mobile
MONITORING WITH CONTEXT
Keep an eye on the systems
your team depends on.
Connect reachability checks and application reports to the same incident workflow. Give every alert a system, a module, and a clear description.
Alerts for the right people
Use active System and Module subscriptions to route push notifications to users with a registered device.
- Mobile push notifications
- Open and Closed incident filters
- Close incidents from the app
Named IP monitors
Check routers, servers, and network devices with the Ping Monitor worker. Recognize a device by its name, not just its address.
- IPv4 and IPv6 targets
- Configurable interval and timeout
- Consecutive failure thresholds
YOUR NETWORK. YOUR CHECKS.
A monitor that fits
your environment.
Run the worker on a host that can reach your devices. Tune how often it checks, how long it waits, and when a failure deserves an alert.
Wait for a pattern
Set a consecutive failure threshold to avoid alerting on every isolated missed ping.
Control reminders
Choose a reminder interval during an outage, or send one alert per outage. A successful check resets the failure count.
ICMP reachability checks show whether a device responds to ping; they do not measure application health.
Ping Monitor configurationExample settings
Office router192.168.1.1
- Check interval
- 60 seconds
- Ping timeout
- 3 seconds
- Failure threshold
- 3 consecutive checks
- Outage reminder
- Every 60 minutes
- Delivery destination
- Notification Gateway
Configured in the worker’s settings file. Each pass completes before the next interval begins.
THE NOTIFICATION GATEWAY
A temporary outage
shouldn’t lose an alert.
Place the gateway between your applications and the Issues Cloud API. It saves accepted requests to a local queue and retries when upstream delivery fails.
- Durable local storage before forwarding
- Automatic retries for pending requests
- Company credentials for authenticated delivery
ApplicationsPing Monitor
Notification GatewaySave → Forward → Confirm
Issues Cloud API
Upstream unavailable? Keep it queued. Retry later.
Direct API — Send straight to Issues Cloud when your application manages delivery.
Gateway — Add a durable local queue and automatic retries. Delivery is at least once; retries can produce duplicates.
FROM SIGNAL TO RESOLUTION
Four steps. One clear path.
Connect your environment, define who needs to know, and keep incidents moving.
Connect
Configure named IP targets in the worker, or send incidents from your applications.
Deliver
Use company credentials to send through the API or a gateway with a persistent queue.
Notify
Match users to System and Module subscriptions and register their mobile devices.
Resolve
Review incident details, filter Open and Closed items, and close an incident from the app.
Context travels with the alert.
STAY CONNECTED ON MOBILE
From a notification
to the next step.
Keep incident details close, even when you’re away from your desk. The mobile app connects push alerts with your team’s incident list.
See the bigger picture
Review your issue summary and move between Home, Issues, and Profile.
Close the loop
Confirm a resolution in the app and move the incident from Open to Closed.
Check your notification setup
Open the web console View registered device details and queue a sample notification from the web User page.
A FEW THINGS TO KNOW
Questions,
answered.
Start with a setup that matches your network and delivery needs.
What can I monitor with Issues Cloud?
The Ping Monitor worker checks named IPv4 and IPv6 addresses using ICMP. Applications can also report incidents through the Web API or gateway. Ping checks indicate reachability, not whether a website or application is functioning correctly.
Where does the monitor run?
Run the C# worker on a machine with network access to the IPs you want to check and permission to send ICMP traffic. Set targets, intervals, timeouts, thresholds, and credentials in its configuration, then restart it after changes.
Do I need the notification gateway?
No. The worker supports direct API delivery as well as gateway delivery. Use the gateway when you want accepted requests stored in a durable local queue and retried if the upstream API is unavailable.
What happens if delivery fails?
The worker keeps pending alerts in memory and retries on the next pass; a worker restart clears that state. Once the gateway accepts a request, its local SQLite queue preserves it across restarts when its data directory is retained. The Web API also retries eligible Firebase delivery failures.
Who receives a push notification?
Active users with a registered device token and an active subscription matching the incident’s System and Module. The app needs notification permission. The current user registration stores one device token per user.
Does a recovered monitor close the incident?
A successful ping resets the monitor’s failure count and logs recovery. It does not automatically close an existing incident. Review the issue and mark it Closed from the mobile app when it has been resolved.
LET’S TALK ABOUT YOUR TEAM
Interested in Issues Cloud?
Tell us what you’d like to monitor and how we can help. Leave your email and a message to start the conversation.
MAKE THE NEXT ALERT COUNT
Bring your signals together.
Monitors, gateways, and incidents. A clearer view of what needs your attention.