Open logut opened 1 year ago
What monitor are you using? For example the http monitor allows you to set this header:
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/2331 If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage? If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^
Thanks for your reply!
I'm using the monitor HTTP(s) - Browser Engine (Chrome/Chromium) (Beta)
the current user agent is Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/90.0.4430.212 Safari/537.36
I would suggest setting Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) HeadlessChrome/90.0.4430.212 Safari/537.36 Uptime-Kuma/1.23.1
by default or somethinkg similar.
Allow setting custom headers for this monitor type would also work.
⚠️ Please verify that this feature request has NOT been suggested before.
🏷️ Feature Request Type
Other
🔖 Feature description
To be able to better identifiy the monitors in webserver logs, could you add Uptime-Kuma/* at the end of Chrome User Agent?
✔️ Solution
Be able to identify in server's log requests from Uptime Kuma monitors.
❓ Alternatives
📝 Additional Context
No response