cos-lite docs - solution matrix

Solution matrix

K8s charm Machine charm Legacy charms - LMA deps Non-juju workload
Logs LokiPushApiConsumer (for workloads that can communicate directly with Loki, LogProxyConsumer (installs promtail in the workload; not suitable for air-gapped), LogForwarder (pebble-native, Juju>=3.4.1) cos_agent (subordinate, pulls logs from /var/log or from other snaps with a matching slot) cos-proxy grafana-agent snap (manually configured)
Metrics prometheus_scrape (in-model), prometheus_remote_write (CMR) - with grafana-agent cos_agent cos-proxy scrape-target, grafana-agent snap
Traces tracing (instrumented workloads), charm_tracing (for the charm itself) tracing (CMR), cos_agent N/A grafana-agent charm
Dashboards grafana_dashboard, cos-configuration cos_agent, cos-configuration cos-proxy, cos-configuration cos-configuration
Alert rules via metrics and logs relations, cos-configuration cos_agent, cos-configuration cos-proxy, cos-configuration cos-configuration
  • The COS Lite bundle does not include tracing by default; however, there’s a bundle overlay for that.

External links

1 Like

@sed-i should we be adding grafana-agent to ‘tracing/non-juju workloads’ now that we have merged support for it? Also we could be link to How to integrate `cos-lite` with uncharmed applications for more context?

Yes to both questions :slight_smile:

I also think the table is not very readable with discourse’s width limit. Would you like to try splitting this page into sections? From first glance it seems that “Logs”, “Metrics”, … could be the new section titles, but perhaps you discover something different.

will give it a shot next week if I have time. For now adding gagent and the link