Frank Elsinga

@jhonny-v46 This has been fixed in the [`1.22.0`-release](https://github.com/louislam/uptime-kuma/releases/tag/1.22.0) by https://github.com/louislam/uptime-kuma/pull/3203 and https://github.com/louislam/uptime-kuma/pull/3152 I missed this issue when linking them to the second PR. => Could you close this issue as...

Closing as resolved in the [`1.22.0`-release](https://github.com/louislam/uptime-kuma/releases/tag/1.22.0) by https://github.com/louislam/uptime-kuma/pull/3203 and https://github.com/louislam/uptime-kuma/pull/3152

> Is the current import feature on Uptime Kuma functioning? We currently have no feature to import csv's from Uptime Robot. I don't know what you mean by `I can...

@ramymoh please open another ticket in the `help` category. This is not the corrrect issue to discuss this.

@honestlai Please refrain from posting `+1` / requests for updates things on issues, as this makes issue-management harder. Issues are for discussing what needs to be done how by whom....

Related to this issue is the ability to format messages send. - #1529 - #2661 - https://github.com/louislam/uptime-kuma/issues/2617 - https://github.com/louislam/uptime-kuma/issues/2387 - and more: see #646 for a deeper discussion

@sprior Why not add a tag like `datacenter:eu-central-1`, `location:frankfurt`, `az:primary`, ... (something that matches your deployment strategy). I think this is already handled by said subsystem.

Why could this not be coverend by a tag like `room:2410.EG.006`, `room:MW 0450B` or `rack:42`?

Currently, there is no CLI and adding one is blocked by #118 imo. See PR #3854 for further details on planned progress.

> I'll probably end up attempting to reverse engineer this, as I have an _Immediate_ need for it. Are there technical documentations that I can use to assist in this?...