qubership-logging-operator

First-hop classification and localization of incoming Qubership logging-stack support tickets. Use when triaging what a ticket author is asking for (a problem on an installation, a consultation, a feature request, or a security/vulnerability remediation) and where it sits (which component, on VM or Kubernetes, at runtime or during deploy, and the specific symptom or topic). Decides from ticket content; uses the author's Ticket Type only as a tie-breaker and ignores Resolution/Root Cause. Research-phase skill; classifies only, takes no system action and answers nothing.

First-hop disposition of a classified Qubership logging-stack support ticket. Use after logging-l1-classification has labeled a ticket, to decide the next action — ask the author for missing data (Additional Info Required), flag a suspected known issue with a draft reply (Suspected Known Issue), or hand a structured packet to L2 (Handoff to L2). Reads ticket content and attachments (logs, screenshots); never touches live systems, mutates the ticket, or closes it.