openstatus.dev
Openstatus
www.openstatus.dev
1---
2title: "Level Up Your Monitoring: Introducing the Openstatus CLI"
3description:
4 Say hello to our new CLI and manage your openstatus monitors as code.
5author:
6 name: Thibault Le Ouay Ducasse
7 url: https://bsky.app/profile/thibaultleouay.dev
8 avatar: /assets/authors/thibault.jpeg
9publishedAt: 2025-08-02
10image: /assets/posts/introducing-openstatus-cli/CLI.png
11tag: engineering
12---
13
14As developers, we live in the terminal, sometimes we are even stuck trying to quit NeoVim. At openstatus, we understand that deeply. That's why we're thrilled to announce the release of the openstatus CLI, a powerful new tool designed to bring your monitoring workflow directly into the environment you love.
15
16## From ClickOps to GitOps: A New Approach to Monitoring
17
18Remember the early days of openstatus? It was all about ClickOps – navigating dashboards, clicking buttons, and managing your monitors through the web application. While effective, we knew there was a better way for those who spend their days in their terminal. We wanted a more integrated experience, one that felt as natural and efficient as everything else you do in your terminal.
19
20That vision led us to develop a command-line interface (CLI) that allows you to interact with openstatus directly from your terminal. We wanted to empower you to quickly grab essential information about your monitors and trigger tests.
21
22## Under the Hood: Why Go?
23
24When it came to building our CLI, the choice of Golang was clear, we are already using it for our probe. Its robust standard library, excellent concurrency primitives, and strong type system make it an ideal language for building fast, reliable, and portable command-line tools. Go's ability to compile into a single binary simplifies deployment and ensures a smooth experience across different operating systems. This focus on performance and ease of use perfectly aligns with our goal of providing a seamless terminal experience.
25
26## The Power of the Terminal: Meeting Developer Needs
27
28As we were building openstatus, we listened closely to our users. A recurring theme emerged: while dashboards are great for an overview, more and more developers want to move beyond pure ClickOps. They want to integrate their monitoring directly into their development workflows, automate tasks, and manage their infrastructure as code.
29
30We already have a [Terraform](https://registry.terraform.io/providers/openstatusHQ/openstatus/latest) provider but we wanted to use the same cli to trigger and modify monitors. Also we think YAML is more readable than HCL.
31
32The openstatus CLI directly addresses these needs. Imagine being able to:
33
34
35### Export and manage monitors as code
36
37We've made it possible to import your existing monitors from your openstatus dashboard.
38Just run `openstatus monitors import`
39
40This means you can now manage your monitoring configurations as version-controlled files. Define your monitors in a YAML. To apply your change run `openstatus monitors apply`
41
42This isn't just about convenience; it's about empowerment. The openstatus CLI allows you to treat your monitoring setup like any other part of your codebase, bringing the benefits of version control, automation, and a developer-centric workflow to your uptime and performance checks.
43
44
45
46### Trigger checks directly from your GitHub Actions
47
48Integrate monitoring into your CI/CD pipeline, ensuring that every deployment is thoroughly tested before it goes live.
49
50Here's our custom GitHub action : [https://github.com/marketplace/actions/openstatus-synthetics-ci](https://github.com/marketplace/actions/openstatus-synthetics-ci)
51
52And if you want to install here's our GitHub Action worklow
53
54```yaml
55name: Run OpenStatus Synthetics CI
56
57on:
58 workflow_run:
59 workflows: ['Fly Deploy']
60 types: [completed]
61 branches:
62 - main
63 repository_dispatch:
64 types:
65 - 'vercel.deployment.success'
66 branches:
67 - main
68
69jobs:
70 synthetic_ci:
71 runs-on: ubuntu-latest
72 name: Run OpenStatus Synthetics CI
73 steps:
74 - name: Checkout
75 uses: actions/checkout@v4
76 - name: Run OpenStatus Synthetics CI
77 uses: openstatushq/openstatus-github-action@v1
78 with:
79 api_key: ${{ secrets.OPENSTATUS_API_KEY }}
80```
81
82If you want to see the action in action we are using it in our main repository and running test after every deployment:
83
84https://github.com/openstatusHQ/openstatus/actions/workflows/synthetic.yml
85
86
87## Get Started Today!
88
89We'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
91Ready 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
93We can't wait to hear what you think of it.