mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Monitoring via playwright tests #3371
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#3371
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @kaystrobach on GitHub (May 30, 2024).
📑 I have found these related issues/pull requests
🏷️ Feature Request Type
New monitor
🔖 Feature description
As a user i want to run playwright tests with kuma in order to check more complex szenarios.
this is also available in other monitoring solutions:
✔️ Solution
In browser playwright tests. It’s ok, to copy them in a textarea, the best solution would be to connect a git repo to get the tests.
❓ Alternatives
None, without switching products or having a middleware to run tests.
📝 Additional Context
No response
@CommanderStorm commented on GitHub (May 30, 2024):
I think what you are asking about (especially given the asked git integration) is likely better served by a CI-piepeline
@kaystrobach commented on GitHub (May 30, 2024):
Agree. Git is completely optional. Main use case is very simple tests, like login to idm, open service.
The ci pipeline runs anyway. But can not run every minute etc.
other uptime checkers start to integrate these simple test case implementations to have better insights.
@kaystrobach commented on GitHub (Jun 3, 2024):
related #3056
@kaystrobach commented on GitHub (Jun 3, 2024):
If it helps i can create a short video showing the use case. Please just tell me. Thanks
@kaystrobach commented on GitHub (Jun 3, 2024):
Other similar tools implementing playwright:
@techmattr commented on GitHub (Jun 11, 2024):
I too would love to see more complex checks available. I mentioned this on Reddit and was advised it was being tracked here. Currently Uptime Kuma has very limited use cases for me as all it can do is make sure my login pages are available. If Uptime Kuma had a way to log into these sites it could validate the site is actually working. The playwright integration changedetection.io is done amazingly well and a similar feature would add so much value to Uptime Kuma.
@kaystrobach commented on GitHub (Jun 11, 2024):
@louislam I have a developer set on that topic, if that is interesting for you, he can build the whole PoC and finalize it in the next weeks. Would be a thank you from the https://github.com/fucodo/ and https://github.com/4viewture/ team
@pilulu commented on GitHub (Jul 7, 2024):
Hi,
I'm really interested in a feature like this in order to monitor small things that need a javascript.
I agree that a complex process like logging or loading multiple pages is more adapted on a CI process.
I my use case i would only be sure that all few elements on a page that need javascript rendering are loaded properly.
If it's not a git repo, i expect at least a small textarea to evaluate short playwright scenarios from probe configuration page.
@kaystrobach commented on GitHub (Aug 6, 2024):
@louislam once I have the commitment, that this would get integrated, if implemented well, I would set a dev on that task in the next weeks, maybe for v2+?
@eitchugo commented on GitHub (Sep 23, 2025):
Hi folks! I'm also interested in this, using the uptime-kuma UI to handle a user journey test on a site is much better and user-friendly than using on CI and having to setup cronjobs, etc.
Is there any plans to continue this issue? Or maybe you need any more help?
@morla10111 commented on GitHub (Nov 19, 2025):
Me too would love to see this feature implemented.
@mabed-fr commented on GitHub (Nov 20, 2025):
I find this request interesting for creating robust tests.
In my case, it would be, for example, to add a product to the cart and open the cart. At first, we could limit the scenarios to 30 seconds.
What is the opinion of the managers and contributors on this feature, which is appearing in many monitoring software?
Considering that today it is very easy to record directly from the browser, we would not need an Iptime Kuma window.
@kaystrobach commented on GitHub (Nov 20, 2025):
totally agree, should be used for short stories only. otherwise we can use external hooks now. with the new hooks, we are using gitlab ci to keep the state up to date
@sule26 commented on GitHub (Dec 30, 2025):
+1
@olivernz commented on GitHub (Feb 4, 2026):
Did this end up going anywhere? Was just about to raise a feature request.