solution: example of a grafana dashboard
This commit is contained in:
committed by
GitHub
parent
9dffe2f6e9
commit
73f971d299
1395
dashboard/dshackle.json
Normal file
1395
dashboard/dshackle.json
Normal file
File diff suppressed because it is too large
Load Diff
@@ -1,3 +1,5 @@
|
||||
:imagesdir: assets
|
||||
|
||||
= Logging & Monitoring
|
||||
|
||||
== Access / Request Log
|
||||
@@ -93,4 +95,28 @@ monitoring:
|
||||
----
|
||||
|
||||
Where `jvm` options enabled monitoring of the JVM internals, such as memory, GC, threads, etc.
|
||||
And `extended` enables additional metrics for query selectors, etc.
|
||||
And `extended` enables additional metrics for query selectors, etc.
|
||||
|
||||
== Grafana Dashboard
|
||||
|
||||
Simple Grafana dashboard available link:../dashboard/dshackle.json[here]
|
||||
|
||||
image::dshackle-dashboard.png[alt="",width=80%,align="center"]
|
||||
|
||||
This dashboard contains:
|
||||
|
||||
- Upstreams Availability
|
||||
|
||||
- Upstreams Lag
|
||||
|
||||
- JSON RPC total request / failed requests
|
||||
|
||||
- GRPC total request / failed requests
|
||||
|
||||
- JSON RPC Response time
|
||||
|
||||
- Upstreams Errors
|
||||
|
||||
- JSON RPC upstream conn seconds 50,75,90,99 percentiles
|
||||
|
||||
|
||||
|
||||
BIN
docs/assets/dshackle-dashboard.png
Normal file
BIN
docs/assets/dshackle-dashboard.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 105 KiB |
Reference in New Issue
Block a user