observatorium - GitLite

KO | EN

gitlite — search

#python #react #ai #go #android #machine-learning #rust #linux #docker #awesome #security #pytorch #mcp #open-source

observatorium

(★ 226)

This repository contains the deployment configurations for the Observatorium instances

파일 탐색기

최종 버전 다운로드 (.zip)

- .gitignore
- api.mod
- api.sum
- bingo.mod
- go.mod
- gojsontoyaml.mod
- gojsontoyaml.sum
- hugo.mod
- jb.mod
- jb.sum
- jsonnet-lint.mod
- jsonnet.mod
- jsonnet.sum
- jsonnetfmt.mod
- jsonnetfmt.sum
- kubeval.mod
- kubeval.sum
- mdox.mod
- mdox.sum
- obsctl.mod
- obsctl.sum
- README.md
- variables.env
- Variables.mk
- config.yml
- - docs.yaml
- - dex.libsonnet
  - gubernator.libsonnet
  - hydra.libsonnet
  - kube-prometheus.libsonnet
  - loki.libsonnet
  - memcached.libsonnet
  - minio.libsonnet
  - observatorium.libsonnet
  - thanos.libsonnet
  - token-refresher.libsonnet
  - tracing.libsonnet
- - k.libsonnet
- - e2e.sh
  - main.jsonnet
- jsonnetfile.json
- jsonnetfile.lock.json
- Makefile
- README.md
- main.go
- Makefile
- - recording-rules-api.svg
- - get_involved.md
  - governance.md
  - maintainers.md
  - README.md
- - architecture.md
  - metrics.md
  - multi-cluster.svg
  - Observatorium-High-Level.png
  - README.md
  - rules-api.md
  - single-cluster-read-path.svg
  - single-cluster-write-path.svg
- - 20220215-obsctl.md
  - 20230130-go-configuration.md
  - go-lib-upstream.png
  - README.md
- - getting-started.md
  - README.md
- api.html
- README.md
- Logo-Observatorium-Full.png
- ObservatoriumFinal_Blue_Horizontal.png
- ObservatoriumFinal_Blue_Horizontal.svg
- ObservatoriumFinal_Blue_IconOnly.png
- ObservatoriumFinal_Blue_IconOnly.svg
- ObservatoriumFinal_Blue_Vertical.png
- ObservatoriumFinal_Blue_Vertical.svg
- - default.md
  - docs.md
- - postcss.config.js
- - _index.md
- - observatorium.json
- - index.headers
  - index.html
- - android-chrome-192x192.png
  - android-chrome-512x512.png
  - apple-touch-icon.png
  - favicon-32x32.png
  - favicon.ico
  - logo.png
  - logo.svg
  - observatorium.png
  - site.webmanifest
- - doks
- .gitignore
- config.toml
- node_modules
- README.md
.gitignore
.gitmodules
.mdox.validate.yaml
.mdox.yaml
CODE_OF_CONDUCT.md
COPYRIGHT
go.mod
go.sum
LICENSE
Makefile
netlify.toml
README.md

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

![Observatorium](https://raw.githubusercontent.com/observatorium/observatorium/main/logo/Logo-Observatorium-Full.png)

[![Build Status](https://circleci.com/gh/observatorium/observatorium.svg?style=svg)](https://circleci.com/gh/observatorium/observatorium) [![Slack](https://img.shields.io/badge/join%20slack-%23observatorium-brightgreen.svg)](https://slack.cncf.io/)

### Configuration for Multi-Tenant, Flexible, Scalable, Observability Backend

Observatorium allows you to run and operate effectively a multi-tenant, easy to operate, scalable open source observability system on Kubernetes. This system will allow you to ingest, store and use common observability signals like metrics, logging and tracing. Observatorium is a "meta project" that allows you to manage, integrate and combine multiple well-established existing projects like [Thanos](https://thanos.io), Loki, Tempo/Jaeger, Open Policy Agent etc under a single consistent system with well-defined tenancy APIs and signal correlation capabilities.

As active maintainers and contributors to the underlying projects, we created a reference configuration, with extra software that connects those open source solutions into one unified and easy to use service. It adds missing gaps between those projects like consistency, multi-tenancy, security and resiliency pieces that are needed for a robust backend.

![](https://raw.githubusercontent.com/observatorium/observatorium/main/docs/design/Observatorium-High-Level.png)

Read more on [High Level Architecture](/docs/design/architecture.md) docs.

### Context

As the Red Hat Monitoring Team, we were focusing on the Observability software and concepts since the CoreOS acquisition. From the beginning, one of our main goals was to establish a stable in-cluster metric collection, querying, and alerting for OpenShift clusters. With the growth of managed OpenShift (OSD) clusters, the scope of the team goal has extended: we had to develop a scalable, global, metric stack that can be run in local as well as a central location for monitoring and telemetry purposes. We also worked together with Red Hat Logging and Tracing teams to implement something similar for logging and tracing. We’re also working on Continuous Profiling aspects.

From the very beginning our teams were leveraging Open Source to accomplish all those goals. We believe that working with the communities is the best way to have long term, successful systems, share knowledge and establish solid APIs. You might have not seen us, but members of our teams have been actively maintaining and contributing to major Open Source standards and projects like Prometheus, Thanos, Loki, Grafana, kube-state-metrics (KSM), prometheus-operator, kube-prometheus, Alertmanager, cluster-monitoring-operator (CMO), OpenMetrics, Jaeger, ConProf, Cortex, SIG CNCF Observability, SIG K8s Instrumentation and more.

## What's Included

* [Observatorium](https://github.com/observatorium/observatorium) is primarily defined in [Jsonnet](https://jsonnet.org/), which allows great flexibility and reusability. The main configuration resources are stored in [components](https://github.com/observatorium/observatorium/tree/main/configuration/components) directory, and they import further official resources like [kube-thanos](https://github.com/thanos-io/kube-thanos). Some Examples:
  * You can see examples of how it can be used in different variations/environments [here](https://github.com/observatorium/observatorium/tree/main/configuration/examples).
  * Our [Red Hat Observability Service](https://github.com/rhobs/configuration) is also built on Observatorium.

* We are aware that not everybody speaks Jsonnet, and not everybody have it's own GitOps pipeline, so we designed alternative deployments based on the main Jsonnet resources. [Operator](https://github.com/observatorium/operator) project delivers Kubernetes plain Operator that operates Observatorium.

> NOTE: Observatorium is set of cloud native, mostly stateless components that mostly do not have special operating logic. For those operations that required automation, specialized controllers were designed. Use Operator only if this is your primary installation logic or if you don't have CI pipeline.

> NOTE2: Operator is in heavy progress. There are already plans to streamline its usage and redesign current CustomResourceDefinition in next version. Yet, it's currently used in production by many bigger users, so any changes will be done with care.

* The [Thanos Receive Controller](https://github.com/observatorium/thanos-receive-controller) is a Kubernetes controller written in Go that distributes essential tenancy configuration to the desired pods.

* [The `API`](https://github.com/observatorium/api) is the facet of Observatorium service. It's a lightweight proxy written in Go that helps with multi-tenancy, tenancy (isolation, cross tenancy requests, rate-limiting, roles, tracing). This proxy should be used for all external traffic with Observatorium.

* [OPA-AMS](https://github.com/observatorium/opa-ams) is our Go library for integrating Open Policy Agent with Red Hat authorization service for smooth OpenShift experience.

* [up](https://github.com/observatorium/up) is a useful Go service that periodically queries Observatorium and outputs vital metrics on the Observatorium read path healthiness and performance over time.

* [token-refresher](https://github.com/observatorium/token-refresher) is a simple Go CLI allowing to perform OIDC refresh flow.

### Getting Started

* See [Getting Started](docs/usage/getting-started.md)
* See [Contributing](docs/community/README.md) on how to start contributing.

### Status: Work In Progress

While metric and logging part using Thanos and Loki is used in production at Red Hat,documentation, full design, user guides, different configurations support are in progress.

Stay Tuned!

### Missing something or not sure?

Let us know! Visit our Slack channel or put a GitHub issue!