Maximilian Kaske

@mxkaske.dev

808 Followers 96 Following

building @openstatus.dev

chat interface with the collapsed list_response_logs details table
A component form card listing the current status page components. An open dropdown suggests you can connect monitor and static components while third-party components are yet disabled.
screenshot of status page with a single website monitor followed by two grouped monitors for EU and US. The second US group is collapsed.
theme explorer with the builder sidebar
raspberry pi powering my airplay for the receiver below and now a private location for openstatus.
operational status page with two monitors, all green and an empty state for the notifications.
Screenshot of a status page with an active degraded report that is currently investigated. Also two status tracker bars with a history of the last 45 days can be seen.
empty state of the status page without any monitors and events
keyboard navigation within tabs content, chart and legend.
caps + zine + stickers on a table with packaging stuff
Active ‘Global Latency’ tab including an area chart with the p50, p75, p95 and p99 percentiles of the specific monitor. The legend shows p75 and p95 as active areas. Other tabs are 'Region Latency' sharing that 5 regions are active and ARN is the slowest. And 'Uptime' of 99.99% with a total of 5.1k checks.
Main page of the status page with single and grouped monitor trackers. A main banner with 'All Systems Operational' is displayed for quick visibility of the current status.
me, wearing a cap with « I’m a teapot » written - next to the display showing the openstatus website and a pile of the same caps on the keyboard.
github pr overview with commit numbers, file changed and more for the new dashboard
landing page of the new openstatus-template that is a great kickstart for everyone working with shadcn
screenshot of the top right corner of the upcoming openstatus dashboard providing a feedback popover with a message form
login page of the new openstatus dashbard
light mode screenshot of a chart showing the response time of an endpoint, including a dotted reference line for the degraded threshold
chart of the timing phases of an endpoint. the controls are integrated within a descriptive text.
Draft pull request for the v2 of the dashboard
screenshot of the top-left corner of the upcoming openstatus dashboard with the avatar square generated by a seed and dicebear.com
Screenshot of a React component using useTransition and next/router. It defines a handleClick function that wraps router.push("/new") inside startTransition. The button triggers this function and is disabled while the transition is pending (disabled={isPending}).
hovering the button and focusing the menu-action will negative translate-x the status dot to the left.
The monitors overview page with a list of all of them, including some quick actions to filter.
The create monitor form page. It shows a minimal form to create the monitor and an empty state card informing the user that fine-tuning more settings is possible after its creation.
The supported OpenStatus regions can be selected via checkbox. All regions are grouped by continent.
Response logs 'upgrade-gated preview state' with upgrade button.
cmd+b expands/collapses the right and left sidebar automatically.
Right sidebar displaying multiple sections (Overview, Configuration, Integrations, Notifiers, Last Logs), each having key label table values that share informations about the monitor.
A clean shadcn sidebar project including a 'filter' and 'create' button next to the menu label
Prototyping an alternative page with a table displaying features between OpenStatus and BetterStack.
todos before the showcase
Updated data-table with a 'OpenStatus Light Viewer'
A scribble of the infinite query usage with the direction prev for the live data and direction next for the the load more section which fetches older data. Both use a cursor to memorize which until timestamp data has been fetched.
A small area of the data-table, showing the new unique values faceting on the 'Result' property and the min/max faceting for the 'Latency' property within the command k dialog.
Object array on how to configure the details sheet whenever a user selects a table row.
Before the update: We have the visual green check to define a successful resource (200), while a red cross for any failed resource (400, 500,..). The rows are horizontally separated with a border.