Changelog

With GET, POST and DELETE /v1/enrollment-keys you manage keys. The key itself only appears in the response when you create it, together with the ready-made install command. Every key lists the server agents that enrolled with it.

Every server agent has the agent block in the API with its state, host data, update settings and the key it enrolled with. GET /v1/services/{id}/agent-metrics returns the current values, /agent-metrics/history the history.

Enrollment tokens now carry real tags of your organization. Server may add its own tags decides whether tags from the install command are added. A token's tag may also fill a status page group.

Open enrollment tokens

When you share an invitation in Slack, Teams or WhatsApp, the preview shows the organization's name and who is inviting.

When measurement data is briefly unavailable, /checks and the server agent metrics answer with empty values instead of an error.

Every status page now has a preview image of its own. It shows your page's name, logo and primary colour. At the bottom is the address from the shared link, followed by the current status. If someone shares a link on your own domain, the image shows that domain too. While everything runs, the image glows in your primary colour, otherwise in the colour of the status.

Every incident and every maintenance gets an image of its own with title, time and affected components. There is nothing to set up.

On the Free plan the image carries a small LIVCK logo at the bottom right, just like the footer of your status page.

In the SEO tab of your status page's settings you decide what search engines and link previews show:

• title, description and the subtitle in the image, per language of your status page
• background of the image: automatic, light or dark
• whether previews show the current status
• whether incidents and maintenance get images of their own
• whether search engines may list the page

The tab shows the image as it appears when shared. Platforms often keep previews for hours, messengers keep them in old messages for good. If a shared link should never show an outdated status, turn off the status in previews.

Status pages now have a seo field in the API with the same settings as the tab. With PATCH /v1/statuspages/{id}, seo replaces all of them at once. Whatever you leave out goes back to its default, and "seo": {} resets everything. If you leave out seo entirely, everything stays as it is.

Your organisation's settings now have a time zone. The preview images of incidents and maintenance give start and end in it. The default is Europe/Berlin.

Status pages with a password or an email whitelist no longer appear in search engines. Their preview images show only name, logo and address, never a status. Search engines also no longer pick up the links subscribers use to confirm or manage their subscription.

The time zone picker now groups zones by continent, with Europe at the top and cities in alphabetical order. This applies wherever you pick a time zone: in the organisation, for heartbeats and for SLA objectives.

Saving a status page reset the logo size to Medium. It now stays as you set it. The form also uploaded a newly chosen logo again on every further save. That is fixed too.

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.

Services and status pages can be bundled into an area and granted to specific teams or roles. Every other member sees nothing of them — not in lists, not in incidents, not in notifications.

With no areas, nothing changes: everything stays visible to everyone, as before.

Open access areas

LIVI shows the overall state of every service. Colour and face change as soon as something goes down.

After the pilot it is open to every organisation: CPU, memory, disks and running services next to your other checks. Nobody has to request access any more.

Connect a server

The server overview now shows every partition, not just the fullest.

A ready-made set for the status page, instead of adding each series by hand.