... | @@ -269,6 +269,8 @@ EAR metrics are reported as trace events. |
... | @@ -269,6 +269,8 @@ EAR metrics are reported as trace events. |
|
Node information is stored as Paraver task information.
|
|
Node information is stored as Paraver task information.
|
|
Node GPU data is stored as Paraver thread information.
|
|
Node GPU data is stored as Paraver thread information.
|
|
|
|
|
|
|
|
You can find in the tool's repository two [examples](https://github.com/eas4dc/ear-job-visualization/tree/main/examples) of Paraver Config Files, one for basic CPU metrics and other adding GPU metrics.
|
|
|
|
|
|
## Data visualization with Grafana
|
|
## Data visualization with Grafana
|
|
|
|
|
|
EAR data can be visualized with Grafana dashboards in two different ways: Using grafana with SQL queries (depending on your Data Center configuration) and visualizing data collected with `eacct` and loading locally.
|
|
EAR data can be visualized with Grafana dashboards in two different ways: Using grafana with SQL queries (depending on your Data Center configuration) and visualizing data collected with `eacct` and loading locally.
|
... | | ... | |