[Observability] Grafana dashboards for local & cloud environments
Nobody has claimed this yet.
Assessment
This issue has not been assessed yet.
Description
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
poktrollto 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)
- Ensure OS level metrics for each service (PATH, Envoy Proxy, etc...) are accessible in a separate dashboard
-
Documentation:
- Development:
- Document how a backend developer can update the dashboards
- Lookng into adding
Makefiletargets 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
- Development:
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from pokt-network/path
-
Difficulty 3/5 1-2 days Newbie friendliness 45/100
pokt-network/path#509 ·
-
bug gateway
Difficulty 4/5 3-5 days Newbie friendliness 45/100
pokt-network/path#477 ·
-
config documentation evm portal-db portal-ui qos
Difficulty 4/5 3-5 days Newbie friendliness 48/100
pokt-network/path#475 · 1 comment ·
-
[RADIX][TRON][SUPPLIER] Suppliers should not have to append additional API paths in their RM config Openqos
pokt-network/path#443 · 1 comment · 3 assignees ·
-
config documentation portal-ui qos
pokt-network/path#409 · 1 assignee ·
All issues in pokt-network/path
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
GoogleCloudPlatform/k8s-config-connector#13462 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
coder/coder#29955 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
microsoft/TypeScript#64453 ·
Maintainers usually reply within 1 day
-
OpenAI-compatible endpoint: response ids have only 999 possible values (chatcmpl-rand.Intn(999)) Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day