Search Results for "page"

Kuberhealthy is a Kubernetes operator for synthetic monitoring and continuous process verification. Write your own tests in any language and Kuberhealthy will run them for you. Automatically creates metrics for Prometheus. Includes simple JSON status page. Kuberhealthy lets you continuously verify that your applications and Kubernetes clusters are working as expected. By creating a custom resource (a KuberhealthyCheck) in your cluster, you can easily enable various synthetic tests and get Prometheus metrics for them. Kuberhealthy comes with lots of useful checks already available to ensure the core functionality of Kubernetes, but checks can be used to test anything you like. ...

Making SLOs with Prometheus manageable, accessible, and easy to use for everyone. When running Pyrra outside of Kubernetes, the SLO object can be provided through a YAML file read from the file system. For this, one container or binary needs to be started with the API argument and the reconciler with the filesystem argument. Here, Pyrra will save the generated recording rules to disk where they can be picked up by a Prometheus instance. While running Pyrra on its own works, there won't be...

Meet the easiest way to generate SLOs for Prometheus. Sloth generates understandable, uniform, and reliable Prometheus SLOs for any kind of service. Using a simple SLO spec that results in multiple metrics and multi-window multi-burn alerts. Easy and simple Prometheus SLO (service level objectives) generator.

Maintainable configuration files. Navigate to each package's directory for their respective READMEs. You can download pre-built binaries for Windows, OS X and Linux on the release page. You can then click the "Help" button in the bottom right corner, which will show you a nix-env command that you can run to install the prebuilt executable. You will probably want to use the shared caches hosted at cache.dhall-lang.org and dhall.cachix.org when doing Nix development. This is not required, but this will save you a lot of time so that you don't have to build as many dependencies from scratch the first time. ...

Kubernetes tail. Streams logs from all containers of all matched pods. Match pods by service, replicaset, deployment, and others. Adjusts to a changing cluster - pods are added and removed from logging as they fall in or out of the selection. With no arguments, kail matches all pods in the cluster. You can control the matching pods with arguments that select pods based on various criteria.