Create a Grafana Dasboard template representing AI usage
>>> [!note] Migrated issue <!-- Drupal.org comment --> <!-- Migrated from issue #3567915. --> Reported by: [murz](https://www.drupal.org/user/157092) >>> <p>[Tracker]<br> <strong>Update Summary: </strong>[One-line status update for stakeholders]<br> <strong>Short Description: </strong>[One-line issue summary for stakeholders]<br> <strong>Check-in Date: </strong>MM/DD/YYYY<br> <em>Metadata is used by the <a href="https://www.drupalstarforge.ai/" title="AI Tracker">AI Tracker.</a> Docs and additional fields <a href="https://www.drupalstarforge.ai/ai-dashboard/docs" title="AI Issue Tracker Documentation">here</a>.</em><br> [/Tracker]</p> <h3 id="summary-problem-motivation">Problem/Motivation</h3> <p>We have the "AI Usage Reports" module that displays the AI usage statistics, based on the AI Observability logs, stored in the local Drupal database. Storing the logs in the database is the easy and convenient way, which works out of the box, but it is not good for large sites in production. Production websites usually store logs in a separate logging aggregators like Grafana Loki.</p> <h3 id="summary-proposed-resolution">Proposed resolution</h3> <p>Would be great to create a ready-to-use template of the Grafana Dashboard that represents the AI Usage report with the most interesting reports and charts: token usage per day, per user, per provider, cached token percentage, etc.</p> <p>And publish it to the Grafana dashboards repository here: <a href="https://grafana.com/grafana/dashboards/">https://grafana.com/grafana/dashboards/</a></p> <p>It will be a production-ready alternative to the "AI Usage Reports" module that represents the AI usage statistics from the local Drupal database.</p> <p>Why Grafana? Because it is a free opensource tool to view logs, metrics and traces, and one of the most popular solution to monitor site statistics.</p> <h3 id="summary-remaining-tasks">Remaining tasks</h3> <h3>Optional: Other details as applicable (e.g., User interface changes, API changes, Data model changes)</h3> > Related issue: [Issue #3533109](https://www.drupal.org/node/3533109)
issue