Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Observability] Grafana dashboards for local & cloud environments

Open
#89 5 comments 0 reactions 1 assignee View on GitHub

Nobody has claimed this yet.

Assessment

This issue has not been assessed yet.

Description

observability

Objective

Set the foundation for PATH Grafana dashboards.

Goals

  • Build out the foundational infrastructural for Grafana dashboards in PATH
  • Use the same patterns as in poktroll to be consistent across all of Grove's stacks
  • Clearly document how metrics + logs can be accessed and updated across multiple environents

Deliverables

  • Foundation

    • LocalNet: Ensure Loki, Prometheus, Victoria Metrics and Grafana are part of the stack
    • Staging: Ensure Loki, Prometheus, Victoria Metrics and Grafana are part of the stack
    • Ensure all dashboards (local and staging) are maintain via IaC in the helm-charts repo
  • Metrics

    • Ensure OS level metrics for each service (PATH, Envoy Proxy, etc...) are accessible in a separate dashboard
      • LocalNet (Tilt + Kind)
      • PATH (Staging deployment)
      • Ask @okdas what he recommends for this. Afterwards, look into this reference as another potential starting point.
    • Ensure logs are accesible
      • LocalNet (Tilt + Kind)
      • PATH (Staging deployment)
  • Documentation:

    • Development:
      • Document how a backend developer can update the dashboards
      • Lookng into adding Makefile targets to streamline this process (if possible); e.g. export and saving json.
    • Access:
      • LocalNet: Document (with links) how anyone can access the LocalNet dashboard
      • Staging: Document (with links) how anyone can access the Staging dashboard

Creator: @HebertCL
Co-Owners: @HebertCL @okdas @Olshansk

Dominant language
Go
Stars
12
Forks
8
PR merge metrics
No merged PRs in 30d

Getting set up

We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from pokt-network/path

All issues in pokt-network/path

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.