Skip to content

Open-source status page, incident response and uptime monitoring

📝 changelog assertion

Thibault Le Ouay4d5b23eaee46
diff --git a/apps/web/public/assets/changelog/request-assertions.png b/apps/web/public/assets/changelog/request-assertions.png
new file mode 100644
index 000000000..8277f7d93
Binary files /dev/null and b/apps/web/public/assets/changelog/request-assertions.png differ
diff --git a/apps/web/src/content/changelog/request-assertions.mdx b/apps/web/src/content/changelog/request-assertions.mdx
new file mode 100644
index 000000000..e5a45db07
--- /dev/null
+++ b/apps/web/src/content/changelog/request-assertions.mdx
@@ -0,0 +1,14 @@
+---
+title: Request assertions
+description:
+ Not all requests should return a 200 status code. You can now assert on the
+ status code, headers of your requests.
+publishedAt: 2024-04-01
+image: /assets/changelog/request-assertions.png
+---
+
+Not all requests should return a 200 status code to be successful. Sometimes you
+want to assert on the status code of a request. For example, you might want to
+check that a request returns a 404 status code when a resource is not found.
+
+You can now do this with OpenStatus when you configure your monitor.