"Roadmap-Board, Discord-Bot für die Cloud und neue API-Endpunkte"

On roadmap.livck.cloud you can see what we are working on right now, what comes next and what is done. With your LIVCK account you can:

• vote on topics
• follow topics
• join the discussion
• submit ideas of your own

A submission is first seen only by you, your organisation and us. If it appears on the board, it does so in our wording and without your name.

Our Discord bot brings your status page into a Discord channel. Until now that worked only with Self-Hosted; since 22 September it also works with status pages from LIVCK Cloud. To set it up:

1. Invite the bot to your Discord server.
2. Run /livck subscribe in the channel you want and paste the address of your status page. Cloud or Self-Hosted, the bot works that out itself.

Incidents and maintenance then appear as threads of their own.

Three new endpoints return everything around a service:

• GET /v1/services/{id}/incidents: its incidents
• GET /v1/services/{id}/maintenances: its maintenance
• GET /v1/services/{id}/checks: its check results with location, status, HTTP code, error and timings

That way the API also tells you why a service was unreachable. /v1/incidents and /v1/maintenances can also be narrowed to several services with service_ids.

Write requests (POST) accept an optional Idempotency-Key header. If the response to a successful request never arrives, for example because of a timeout, just repeat it with the same key. You get the original response back, and nothing is created twice. The only exception is uploading logos and favicons.

• GET /v1/tags now filters by label and key.
• POST /v1/tags/ensure creates a tag or returns the existing one.

No more paging through a list to find a tag.

If part of creating a service through the API fails, such as setting its tags, no half-created service is left behind any more. A second attempt therefore creates no duplicate.