Official Grafana Dashboards

[cboudereau]

It would be nice to have official dashboards using internal metrics / log to bootstrap quickly a vector setup on production.

I published on grafana labs useful dashboards for vector.dev pipeline monitoring and vector.dev host_metrics for node exporter dashboard.

Dashboards are available here : https://github.com/cboudereau/vector-community/.

The repository is called community like in opentelemetry collector.

Let me know where can I push those dashboards on your hand and / or how do you manage community contribution for dashboard ?

Dashboard are usually located on a live demo folder with a very little use case, a docker-compose and dashboards. Here is an example of a live vector demo I made for instance including happy an error path (the demo is sure too big but I can limit the example to an app + vector + grafana + loki + mimir) : https://github.com/cboudereau/consul-demo/tree/main/service-discovery/agents

If you think that such demo in interesting, where shall I put the demo or at least be referenced ?

A note for the community

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request

Use Cases

quickly a vector setup on production

Attempted Solutions

dashboards: https://github.com/cboudereau/vector-community/ live demo : https://github.com/cboudereau/consul-demo/tree/main/service-discovery/agents

Grafana Labs dashboards: vector drop-in solution for node exporter: https://grafana.com/grafana/dashboards/19650-node-exporter-vector-host-metrics/ vector monitoring: https://grafana.com/grafana/dashboards/19649-vector-monitoring/

Proposal

Can we officially push such dashboards and/or demo here ? If yes where could we put dashboards and live demo ?

[neuronull]

👋 Hi @cboudereau,

This has been discussed a bit in the past. And @zamazan4ik also started down the path in https://github.com/vectordotdev/vector/pull/14369.

I think since the discussion previously was focused in a PR, this GH issue could serve as a central feature request.

It's something we're not opposed to we just haven't sorted out the best way to host community supported resources.

I think we can keep this issue open to continue the conversation and track the demand from it.