openstatus.dev
Openstatus
www.openstatus.dev
🔗 fix link (#1382)
authored by
Thibault Le Ouay
and committed by
GitHub
56104b5c
a8e79d78
+27
-24
+2
-2
apps/dashboard/src/app/(dashboard)/cli/page.tsx
+2
-2
apps/dashboard/src/app/(dashboard)/cli/page.tsx
···
129
129
Get started with the CLI to export and manage your monitors in your
130
130
code.{" "}
131
131
<Link
132
-
href="https://docs.openstatus.dev/cli/getting-started/"
132
+
href="https://docs.openstatus.dev/reference/cli-reference/"
133
133
target="_blank"
134
134
rel="noopener noreferrer"
135
135
>
···
191
191
<SectionDescription>
192
192
We have a few more commands to run. Check the{" "}
193
193
<Link
194
-
href="https://docs.openstatus.dev/cli/getting-started/"
194
+
href="https://docs.openstatus.dev/reference/cli-reference/"
195
195
target="_blank"
196
196
rel="noopener noreferrer"
197
197
>
+1
-1
apps/dashboard/src/app/(dashboard)/notifications/client.tsx
+1
-1
apps/dashboard/src/app/(dashboard)/notifications/client.tsx
+1
-1
apps/dashboard/src/app/(dashboard)/status-pages/[id]/subscribers/page.tsx
+1
-1
apps/dashboard/src/app/(dashboard)/status-pages/[id]/subscribers/page.tsx
+3
apps/docs/src/content/docs/reference/http-monitor.mdx
+3
apps/docs/src/content/docs/reference/http-monitor.mdx
+1
-1
apps/web/src/components/marketing/cli/card.tsx
+1
-1
apps/web/src/components/marketing/cli/card.tsx
+3
-3
apps/web/src/components/marketing/feature/index.tsx
+3
-3
apps/web/src/components/marketing/feature/index.tsx
···
378
378
action={
379
379
<Button variant="outline" className="w-max rounded-full" asChild>
380
380
<a
381
-
href="https://docs.openstatus.dev/cli/getting-started"
381
+
href="https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/"
382
382
rel="noreferrer"
383
383
target="_blank"
384
384
>
···
530
530
action={
531
531
<Button variant="outline" className="w-max rounded-full" asChild>
532
532
<a
533
-
href="https://docs.openstatus.dev/cli/getting-started"
533
+
href="https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/"
534
534
rel="noreferrer"
535
535
target="_blank"
536
536
>
···
570
570
action={
571
571
<Button variant="outline" className="w-max rounded-full" asChild>
572
572
<a
573
-
href="https://docs.openstatus.dev/monitoring/opentelemetry"
573
+
href="https://docs.openstatus.dev/guides/how-to-export-metrics-to-otlp-endpoint/"
574
574
rel="noreferrer"
575
575
target="_blank"
576
576
>
+1
-1
apps/web/src/content/changelog/cli-improvement.mdx
+1
-1
apps/web/src/content/changelog/cli-improvement.mdx
···
13
13
- Export monitors: Export all your workspace monitors to a YAML file.
14
14
15
15
16
-
Check out our [CLI documentation](https://docs.openstatus.dev/cli/getting-started/) for more information.
16
+
Check out our [CLI documentation](https://docs.openstatus.dev/reference/cli-reference/) for more information.
+1
-1
apps/web/src/content/changelog/opentelemetry.mdx
+1
-1
apps/web/src/content/changelog/opentelemetry.mdx
···
7
7
8
8
We have added support for exporting your OpenStatus synthetic checks as OpenTelemetry metrics.
9
9
10
-
Check our [documentation](https://docs.openstatus.dev/monitoring/opentelemetry/) for more information on how to set it up.
10
+
Check our [documentation](https://docs.openstatus.dev/guides/how-to-export-metrics-to-otlp-endpoint/) for more information on how to set it up.
11
11
12
12
Here's an example of us exporting our synthetic checks to Grafana.
13
13
+1
-1
apps/web/src/content/changelog/status-page-badge-v2.mdx
+1
-1
apps/web/src/content/changelog/status-page-badge-v2.mdx
+1
-1
apps/web/src/content/changelog/webhook-integration.mdx
+1
-1
apps/web/src/content/changelog/webhook-integration.mdx
+1
-1
apps/web/src/content/posts/hono-vercel-fluid-compute.mdx
+1
-1
apps/web/src/content/posts/hono-vercel-fluid-compute.mdx
···
90
90
url: https://hono-cold.vercel.app/
91
91
retry: 3
92
92
```
93
-
We have deployed it using the [openstatus cli](https://docs.openstatus.dev/cli/getting-started/).
93
+
We have deployed it using the [openstatus cli](https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/).
94
94
95
95
```bash
96
96
openstatus monitors apply
+1
-1
apps/web/src/content/posts/introducing-openstatus-cli.mdx
+1
-1
apps/web/src/content/posts/introducing-openstatus-cli.mdx
···
88
88
89
89
We're incredibly excited about the openstatus CLI and believe it will fundamentally change how you interact with your monitoring. It's a significant step towards a more integrated, efficient, and developer-friendly monitoring experience.
90
90
91
-
Ready to take your monitoring to the next level? Head over to our [documentation](https://docs.openstatus.dev/cli/getting-started/) to learn how to install and start using the openstatus CLI today.
91
+
Ready to take your monitoring to the next level? Head over to our [documentation](https://docs.openstatus.dev/tutorial/get-started-with-openstatus-cli/) to learn how to install and start using the openstatus CLI today.
92
92
93
93
We can't wait to hear what you think of it.
+9
-9
apps/web/src/content/posts/product-strategy-a-reality-check.mdx
+9
-9
apps/web/src/content/posts/product-strategy-a-reality-check.mdx
···
10
10
tag: company
11
11
---
12
12
13
-
We worked closely with [Emily Omier](https://emilyomier.com/) to understand our place in the open-source ecosystem and to challenge ourselves. Over the course of a month, every week, Emily hit us with tough questions and then questioned our answers again. All async - so everyone could work on it when they had the capacity.
13
+
We worked closely with [Emily Omier](https://emilyomier.com/) to understand our place in the open-source ecosystem and to challenge ourselves. Over the course of a month, every week, Emily hit us with tough questions and then questioned our answers again. All async - so everyone could work on it when they had the capacity.
14
14
15
15
Spoiler alert: it’s been hard - really hard.
16
16
···
32
32
33
33
## Unique value in the ecosystem
34
34
35
-
We didn’t feel particularly unique. And that’s one of the hardest things we’re struggling with. If you know what makes you special, you can lean into it.
35
+
We didn’t feel particularly unique. And that’s one of the hardest things we’re struggling with. If you know what makes you special, you can lean into it.
36
36
Without naming any competitors - most of them offer status pages and monitoring. So why would anyone choose an open-source, bootstrapped company?
37
37
38
38
Here’s why:
39
39
40
40
We build in the open, share what we learn, and our work inspires others. At the start of our journey, we were lucky to make it onto the oss-friends list. We speak the same language as developers (and never like corporate brands). That’s just not who we are. We focus on crafting beautiful DX, UX, and UI - and that gets people talking.
41
41
42
-
Technically, we offer parallel scheduling and multi-region monitoring by default.
42
+
Technically, we offer parallel scheduling and multi-region monitoring by default.
43
43
But most of our users primarily care about one thing: uptime. Parallel pings are resource-heavy, and if we want to offer more monitors at a lower cost, we should consider round-robin scheduling to reduce resource consumption and pass those savings to users.
44
44
45
45
Lots of competitors use a pay-as-you-go approach. We try to keep reasonable limits within a fixed pricing. Know in advance what you'll pay!
46
46
47
-
With the new dashboard and CLI (soon more), we’re moving toward an opinionated but clean DX/UX (inspired by the [Linear method](https://linear.app/method)) and focusing entirely on monitoring + status pages. We’re also updating our pricing very soon (if we haven't already) to better reflect what our users need.
47
+
With the new dashboard and CLI (soon more), we’re moving toward an opinionated but clean DX/UX (inspired by the [Linear method](https://linear.app/method)) and focusing entirely on monitoring + status pages. We’re also updating our pricing very soon (if we haven't already) to better reflect what our users need.
48
48
49
49
{/* ~~REMINDER: add post once published~~ */}
50
50
51
51
With tools like `shadcn` emerging and the increasing influence of AI-powered tools, we want to embrace this wave and provide even more value to the ecosystem.
52
52
53
-
We're a small, bootstrapped, and transparent team, we can move fast in terms of changes but it also implies moving slower due to pivots. So we have to be aware of our values and stay true to ourselves.
53
+
We're a small, bootstrapped, and transparent team, we can move fast in terms of changes but it also implies moving slower due to pivots. So we have to be aware of our values and stay true to ourselves.
54
54
55
-
And if you have an issue, you’ll hear from the Thibault or me directly.
55
+
And if you have an issue, you’ll hear from the Thibault or me directly.
56
56
57
57
> Get in touch: via [cal.com](https://openstatus.dev/cal), [Discord](https://openstatus.dev/discord), or simply by [email](ping@openstatus.dev) - choose your channel.
58
58
···
64
64
65
65
Over time, we’ve tried to reduce friction - like migrating from Clerk to NextAuth - but we’re not fully there yet. Thankfully, [Tinybird published a Docker version](https://www.tinybird.co/blog-posts/tinybird-local-docker-container), which removed one of our biggest blockers. And our usage of Google Queue can easily be replaced.
66
66
67
-
Our resources are limited. Until there's a clear and urgent need to invest in self-hosting, we have to stay focused. That’s also why we’re not building an on-call system or branching out into features that would broaden our audience too much. Doing so would mess up our purpose: monitoring and status pages. Instead, we provide solid integrations with tools like [OpsGenie](https://docs.openstatus.dev/alerting/providers/opsgenie/) and [PagerDuty](https://docs.openstatus.dev/alerting/providers/pagerduty/).
67
+
Our resources are limited. Until there's a clear and urgent need to invest in self-hosting, we have to stay focused. That’s also why we’re not building an on-call system or branching out into features that would broaden our audience too much. Doing so would mess up our purpose: monitoring and status pages. Instead, we provide solid integrations with tools like [OpsGenie](https://docs.openstatus.dev/reference/notification/#opsgenie) and [PagerDuty](https://docs.openstatus.dev/reference/notification/#pagerduty).
68
68
69
69
Also: running OpenStatus yourself, with all features enabled, is often **more expensive** than paying for a hosted plan.
70
70
···
78
78
79
79
But we now provide a simple way for uptime monitoring as code: you don't need language stuff - just a simple yaml file. Run it in your CI/CD pipes and add additional health checks after deployments via our [GitHub integration](https://docs.openstatus.dev/guides/how-to-run-synthetic-test-github-action/).
80
80
81
-
> We know that our marketing page doesn’t clearly explain the problems we solve.
81
+
> We know that our marketing page doesn’t clearly explain the problems we solve.
82
82
> It lists features (not even very well), but it should focus on the _problems_ we address - and how OpenStatus helps solve them. It will take time to rework our pages and fill it with words.
83
83
84
84
## Our opinions in the ecosystem
···
96
96
We were lucky to work closely with Emily - and lucky that she challenged us. If you are in the OSS space, we can only recommend reaching out.
97
97
Even now, I can already picture her questioning our decisions as we move forward. She gave us timeless input, tough questions, and a method we’ll come back to whenever we find ourselves stuck.
98
98
99
-
Everything takes time and we have reduced the number of new features shipped over the last months - on purpose. Changes are coming - and we’re excited to start this next chapter with you.
99
+
Everything takes time and we have reduced the number of new features shipped over the last months - on purpose. Changes are coming - and we’re excited to start this next chapter with you.
100
100
101
101
As always, we’re incredibly grateful for every feedback and support we are getting.
102
102