provide orgId to grafana RuleGroup (#8113)

Author: jonathanawesome

deployment/services/grafana-alerts.ts

@@ -23,11 +23,11 @@ export function deployGrafanaAlerts(envName: string) {
 
   // Single rule group for the metric-alerts feature; evaluation interval
   // matches the cron that produces the underlying metrics (every minute).
-  // @ts-expect-error @lbrlabs/pulumi-grafana@0.1.0 marks orgId required on
-  // RuleGroupArgs but optional on Folder/Dashboard; per the library docstring,
-  // omitting it falls back to the provider's configured org (same as how the
-  // Folder above and Dashboards in services/grafana.ts are set up).
+  // `orgId: 1` is the default "Main Org" — Folder and Dashboard fall back to
+  // the provider's configured org when omitted, but RuleGroup validates the
+  // property at construct time and throws if missing.
   const ruleGroup = new RuleGroup('metric-alerts-evaluator', {
+    orgId: '1',
     folderUid: folder.uid,
     name: 'metric-alerts-evaluator',
     intervalSeconds: 60,

deployment/services/grafana.ts

@@ -23,6 +23,7 @@ export function deployGrafana(envName: string, tableSuffix: string) {
   );
   params['TABLE_SUFFIX'] = tableSuffix;
   params['PROM_DATASOURCE_UID'] = params['PROM_DATASOURCE_UID'] ?? 'grafanacloud-prom';
+  params['TEMPO_DATASOURCE_UID'] = params['TEMPO_DATASOURCE_UID'] ?? 'grafanacloud-traces';
 
   const dashboards = availableFiles.map(filePath => {
     const fullPath = join(dashboardDirectory, filePath);