Closed
Bug 2005778
Opened 8 months ago
Closed 4 months ago
[KR5] Phase 3 - MVP: Add Glean telemetry metrics for AI Window Security Layer
Categories
(Core :: Machine Learning: General, task)
Core
Machine Learning: General
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: rconcepcion, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [genai])
Add Glean telemetry to track security layer performance in production. This data will help monitor performance impact and identify regressions as the security layer evolves.
Coordinate with Taimur to align with existing inference runtime telemetry patterns and naming conventions.
Metrics to Track
- Evaluation duration (time spent in SecurityOrchestrator.evaluate())
- Evaluation count (number of evaluations per session)
Notes
- Security layer is a bottleneck for LLM calls; production telemetry will help monitor real-world impact
- Start with basic metrics; expand as needed based on findings
Acceptance Criteria:
- Glean metrics implemented for security layer evaluation
- Metrics aligned with existing inference runtime telemetry naming
- Data visible in Glean dashboards
Updated•8 months ago
|
| Reporter | ||
Updated•8 months ago
|
Summary: Add Glean telemetry metrics for AI Window Security Layer → [KR5] Phase 3 - MVP: Add Glean telemetry metrics for AI Window Security Layer
Comment 1•4 months ago
|
||
This is getting removed in Bug 2029729.
Status: NEW → RESOLVED
Closed: 4 months ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•