That's the plan! The incumbent SaaS providers are effectively charging a premium over the underlying storage. Their business is really reselling storage. Removing that premium via a self-hosted system then greatly reduces the need to structure your applications to fit the cost of monitoring it. This also means that any negotiated discounts and features they may use (e.g., S3 Standard-IA) are also applicable to data in Opstrace.
We will also have a blog post about bad UX in a couple weeks… stay tuned. What are some of your biggest gripes about UX?
Just to answer the question about what metrics are included, you can write and read any kind of custom metrics and log data from your applications, and have to build useful dashboards yourself. When first deployed, the user tenants (you can create any number of tenants to partition your data) are empty (you start with a clean slate) and ready for you to send any metrics/logs to it. You also have to add your own dashboards to interpret the data you've sent.
Opstrace does ship with a "system" tenant designed for monitoring the Opstrace system itself. This tenant has built-in dashboards that we've designed to show you the health of the Opstrace system.
Incidentally, having sharable "dashboards" across people/teams/organizations is something we are also working on, so people don't have to re-invent dashboards all the time.
Yeah, anytime I hear "on-prem" deployment I think of my previous experience with getting a product deployed across a lot of different K8s environments. At the surface there are ostensibly common APIs, but the underlying components (networking, storage) are not necessarily interchangeable. There may also be custom policies around e.g. labels, SecurityContexts, or NetworkPolicies. In my own K3s cluster I generally just manage the YAML specs for the deployments by hand, since I’ll often need to e.g. specify the arch constraint to run against, or ensure that it’s running a multi-arch image. It’s a really interesting problem though, and it’s something that we’re targeting.
Hi, this is Nick Parker from the Opstrace team. I personally have my own on-prem arm64/amd64 K3s cluster, including a basic 4-node Minio deployment, so I’m very interested in getting local deployment up and running myself. We’re a small team and we’ve been focusing on getting a couple well-defined use-cases in order before adding support for running Opstrace in custom and on-prem environments. It turns into a bit of a combinatorial explosion in terms of supporting all the possibilities. But we definitely want to support deploying to custom infrastructure eventually.
We will also have a blog post about bad UX in a couple weeks… stay tuned. What are some of your biggest gripes about UX?