| linkTitle | title | description | weight | menu | aliases | owner | user_questions | last_review_date | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Observability |
Observability Features |
Overview of the observability related platform features to help you operate and improve your platform and applications. |
70 |
|
|
|
2024-03-21 |
Observability is based on four main data sources: logs, metrics, traces and profiles. To cover these needs, Giant Swarm provides its customers with a fully managed observability platform supported by 24//7 monitoring and alerting. The tools included in the observabily platform are listed below.
We chose these applications based on our general principles of preferring open source over proprietary solutions, as well as simplicity, performance, and speed over complexity.
If you want to learn more about observability, we recommend that you read this
To summarize, for observability, we recommend and provide these tools:
To store, index, and make logs (containers, kubernetes events, audit logs) searchable. You can also install our Loki App on your clusters.
To get all your metrics, process, store and alert on them. Prometheus has become the de-facto standard monitoring tool in the kubernetes ecosystem.
To analyze, visualize, and correlate any kind of observability data.
We are currently offering Grafana Tempo a part of our observability platform on demand and without any availability garantees due to the low priority it has with our customers.
Profiling is quite a new kid on the block when it comes to observability. Same as with Grafana Tempo, we are currently offering Grafana Pyroscope a part of our observability platform on demand and without any availability garantees due to the low priority it has with our customers.
If you want to learn more about our monitoring platform, feel free to dive into our [Getting Started]({{< relref "/vintage/getting-started/observability" >}}) section.