digitalmars.D.announce - status.dlang.rocks =?UTF-8?B?4oCU?= A new Status Page
- Mindy (0xEAB) (20/20) May 03 I proudly announce the go-live of the new D infrastructure status
- Mindy (0xEAB) (3/5) May 03 The old status page can be found under this short URL:
- Meta (2/22) May 03 It's missing blog.dlang.org
- Mindy (0xEAB) (2/3) May 03 ✔️ Added.
- libxmoc (3/23) May 04 I prefer the old version, it's easier to read vertically and had
- Mindy (0xEAB) (30/32) May 11 Thanks for honest the feedback!
I proudly announce the go-live of the new D infrastructure status page. It can be found under <https://status.dlang.rocks>. Features include: • Dashboard (overviews) — services currently up/down • List of all monitored services • Detailed check information • Historical incident data The already in existence link <https://dlang.at/status> will continue to work (and is the preferred short URL). Available dashboards as of now: • D (+DLF): <https://status.dlang.rocks/dashboards/dlang.org> • Open D: <https://status.dlang.rocks/dashboards/opendlang.org> • dlang.at: <https://status.dlang.rocks/dashboards/dlang.at> The monitoring is powered by updown.io (SaaS). All data is retrieved from their API. The status page application is FOSS; its source code can be found on GitHub. <https://github.com/dlang-at/status-page> Looking forward to hearing your feedback! :)
May 03
Mindy (0xEAB) <desisma heidel.beer> On Sunday, 3 May 2026 at 17:36:16 UTC, Mindy (0xEAB) wrote:The already in existence link <https://dlang.at/status> will continue to work (and is the preferred short URL).The old status page can be found under this short URL: <https://dlang.at/updown.io>
May 03
On Sunday, 3 May 2026 at 17:36:16 UTC, Mindy (0xEAB) wrote:I proudly announce the go-live of the new D infrastructure status page. It can be found under <https://status.dlang.rocks>. Features include: • Dashboard (overviews) — services currently up/down • List of all monitored services • Detailed check information • Historical incident data The already in existence link <https://dlang.at/status> will continue to work (and is the preferred short URL). Available dashboards as of now: • D (+DLF): <https://status.dlang.rocks/dashboards/dlang.org> • Open D: <https://status.dlang.rocks/dashboards/opendlang.org> • dlang.at: <https://status.dlang.rocks/dashboards/dlang.at> The monitoring is powered by updown.io (SaaS). All data is retrieved from their API. The status page application is FOSS; its source code can be found on GitHub. <https://github.com/dlang-at/status-page> Looking forward to hearing your feedback! :)It's missing blog.dlang.org
May 03
On Sunday, 3 May 2026 at 19:19:05 UTC, Meta wrote:It's missing blog.dlang.org✔️ Added.
May 03
On Sunday, 3 May 2026 at 17:36:16 UTC, Mindy (0xEAB) wrote:I proudly announce the go-live of the new D infrastructure status page. It can be found under <https://status.dlang.rocks>. Features include: • Dashboard (overviews) — services currently up/down • List of all monitored services • Detailed check information • Historical incident data The already in existence link <https://dlang.at/status> will continue to work (and is the preferred short URL). Available dashboards as of now: • D (+DLF): <https://status.dlang.rocks/dashboards/dlang.org> • Open D: <https://status.dlang.rocks/dashboards/opendlang.org> • dlang.at: <https://status.dlang.rocks/dashboards/dlang.at> The monitoring is powered by updown.io (SaaS). All data is retrieved from their API. The status page application is FOSS; its source code can be found on GitHub. <https://github.com/dlang-at/status-page> Looking forward to hearing your feedback! :)I prefer the old version, it's easier to read vertically and had more details.
May 04
On Monday, 4 May 2026 at 13:29:22 UTC, libxmoc wrote:I prefer the old version, it's easier to read vertically and had more details.Thanks for honest the feedback! Much appreciated :) Old status page --------------- First and foremost, the old status page isn’t going anywhere. It’s set up using a feature provided by updown.io as part of their SaaS offering for free of (additional) charge complementary to their monitoring service. Regarding the visible details ----------------------------- • There is a table view showing all monitored endpoints with a few details: <https://status.dlang.rocks/checks> • I’m limited to what data I can gather using their API. Unfortunately, that outright lacks certain details (i.a. HTTP/2 availability, IPv4/IPv6 availability). Others are only readable using a write-enabled API key. (I’ve opened a feature request regarding this, but they are wary adding another API key type; while I’m wary adding full access API key to an app that is only supposed to have read-only access.) • From my perspective, a status page is primarily supposed to provide a quick overview about which services are down (and which are up). That’s why the dashboard (which serves as a front page) is designed the way it is. • The “grid” view of the dashboard actually consists of two grids: One for services that are down, one for services that are up. (Thought I’d add this fact, as it’s only observable in situations where something is down.) • I will experiment with a “list” view for the dashboard. Thank you for this idea.
May 11