ocis VS loki

I found a way to do this : just copying the data over WebDAV using rclone (https://github.com/owncloud/ocis/blob/b2323752289d31c4844f36ef71a2ba531bd749c2/docs/ocis/guides/migrate-data-rclone.md)

According to the README[1] on their source repository, that is, flatly, untrue.

They say:

> We are very happy that oCIS does not require a Contributor License Agreement (CLA) as it is Apache 2.0 licensed. We hope this will make it easier to contribute code. If you want to get in touch, most of the developers hang out in our rocket chat channel or reach out to the ownCloud central forum.

They also say:

> Some builds of stable ownCloud Infinite Scale releases provided by ownCloud GmbH are subject to an End User License Agreement.

Which seems both reasonable and sensible...

[1](https://github.com/owncloud/ocis/tree/master)

ownCloud recently released version 3 of ownCloud Infinite Scale (OCIS), which is completely rewritten in Go (which means it's fast) and uses micro-services instead of a PHP monolith. It doesn't have any features like mail/calendar/contacts/chat/etc.. yet, just file sync (but that's all I'm looking for).

This feature request (https://github.com/owncloud/ocis/issues/6558) aims to implement mind-mapping functionality in a free Open Source Software similar to Google Drive called ownCloud Inifite Scale (oCIS).

It's like Prometheus, but for logs. Okay it's not really to do with the Norse or Greek gods, instead Loki is a horizontally-scalable, highly-available, multi-tenant log aggregation system inspired by the open source project Prometheus. Built by Grafana Labs, Loki is designed for ease of use. Instead of indexing the contents of the logs, Loki provides a set of labels for each log stream. The latest update includes query acceleration with Bloom filters, native OTel support, Helm charts, and more. Check out the changelog for all the major changes and deprecations.

I also needed to make a small patch to Promtail to make this work: https://github.com/grafana/loki/pull/10256

We don't pull logs, we forward logs to a centralized logging service.

Over the past few months, I've been spending a lot of time creating dashboards on Grafana using Loki for MyUnisoft (the company I work for).

For log systems you generally don't migrate data. Logs lose value over time. What you want to do is to go ahead and start ingesting data into the new system (OpenObserve in this case) and slowly, the data in the old system will become stale and then you can retire it. However if you need to export logs anyhow, there is no straightforward way in loki to do this. You could run a script to query loki and export it to a file. If found this thread with a sample script - https://github.com/grafana/loki/issues/409

That snap is woefully out of date. The upstream repo was recently updated to 2.8.2, but the snap stable channel has 2.4.1 from 18 months ago. https://github.com/grafana/loki/releases/tag/v2.8.2

Loki