khalidx / uptime

An uptime monitoring web application that is easy to understand, use, and extend.

Hi 👋, I'm Khalid

Let's connect!

Languages and Tools

Status Update

I'm currently working on cloudfs, an easy way to discover and manage your cloud like a local filesystem!

I'm also working on tree, a new language for computing, and the simplest language on the planet! It's in private beta.

Can't figure out how to use ESM + TypeScript + ts-node + Node.JS? Feel like you've been running in circles with tutorials and blogs claiming to have the right config? Look no further. If you want a working config, check out my gist with 490+ stars ⭐️. You'll be up and running in no time!

Repositories

Pinned repositories below are authored by me. Check out my Github Stars for notable projects from around the internet!

uptime's Issues

Add custom request support

Add auto-healing status when the service returns to normal operation

The status should update back to Operational after X number of successes after a failure.

Look up the value that monitoring algorithms use to determine when the status should be changed. Also, should a message be added automatically when statuses change? Or only a message added to the detail page.

Support importing of ansible syntax

Add support for friendly service names in the URL

Default messages should be hidden when loading is in progress

When a component is loading, the default data should not be shown, and the loading indicator should be present.

Publish custom metrics to CloudWatch

https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/publishingMetrics.html

Webpage screenshot support

Endpoints can be marked for taking a screenshot on a schedule, useful for visual confirmation of the status of a site.

Basic features for MVP

• static page with static data
• status page with services
• detail page with charts
• create (and delete) services and service messages
• export JSON data
• deployable to s3
• serverless infrastructure
• serverless deployment
• ping thousands of endpoints and IPs
• call thousands of endpoints with a pre-defined request
• log to CloudWatch and use CloudWatch alarms
• manually toggle health status, with message
• scheduled checks
• manually trigger a check, outside of schedule
• see debug logs for a check
• auth for UI and API users
• display errors when actions fail
• persistent history
• post status and scheduled maintenance messages
• version/refresh/etag support to prevent stale updates

The settings update form fails to change the title

Load testing support

Add support for load testing endpoints using a visual interface.

The web app doesn't load the detail page when there is a space in the service name

It also doesn't show an error. Just shows a mostly-blank page (except for the top navigation bar).

Submissions should be sorted by most-recent first

The submissions on the service detail page should show the most recent submission as the first one.

Implement a more efficient data-loading flow

Across all components, we should choose the optimal times to load (and reload) data when loading the components that depend on that data, whether we are coming from a different component or loading the site straight to the specified component. Data should load (and be refreshed) properly in both cases, and when changes are made.

Add webhook support

Add support for other deployment options

• one-click AWS deployment
• terraform deployment
• deployable as: EC2/AMI/Docker/Fargate/Lambda/S3/NGINX/Process

Configurable notifications

Support configurable notifications for status changes across various channels, like:

• email
• sms
• slack
• webhooks

Display latency metrics numerically on the detail page

Currently, the detail page shows a nice latency chart, visually, but it should also show the latency metrics numerically (avg, min, max, p99).

Changing service health with a message does not update on the detail page

The detail page for a service will still show "Operational", even though its status has been changed and is displaying properly on the Status page.

Backend `pinger` does not update the service status when checks fail

System logs are not loading in the dashboard

An error should be shown when data cannot be loaded

Instead of showing an empty UI (which is better than not showing anything, but uses empty arrays to get around missing data) we should (also) show an error to the user.

Updating a service removes the `nextCheck` value

The value of nextCheck is set on service creation, but not when updating a service. Thus, the value is removed on update.

Fix responsive button sizes and text

Buttons currently only show the icon when the screen is resized to be smaller, like when viewing in a small browser window or from a mobile device.

This should be fixed to show the button text as well, instead of only showing the icon (where applicable, of course).

Add refresh and docs/help buttons when an error occurs

Two buttons/links should be shown to the user in the error box when an error occurs:

• one for refreshing the page (if applicable)
• one for loading relevant documentation or opening a support ticket (if applicable)

Add custom response support

`ArchiveMessage` does not undo the change if the call to the backend fails

Has something to do with the way we are setting message.active.

Add tagging support

Add tagging and search support

Services and messages should be taggable and searchable. Full-text search should be supported.