Open Bug 2012438 Opened 7 months ago Updated 1 day ago

Send telemetry event in case of policy errors

Categories

(Enterprise Products :: Firefox, enhancement, P3)

Desktop
All
enhancement

Tracking

(Not tracked)

People

(Reporter: RT, Assigned: janika, NeedInfo)

References

(Blocks 1 open bug)

Details

(Whiteboard: [size=1])

User Story

There's two ways we can get into an inconsistent state on the client:

- Policy unknown to the client
- Policy threw on application

We should report these to the console

Acceptance criteria:

- If the policy on the client produces errors (unknown or throws), then a telemetry event is sent to the console:
"type": "policy-error",
"glean_timestamp": glean-timestamp,
"message": the error that occurred on the client
"local-policy": the value the client tried to apply, if possible
No description provided.
User Story: (updated)
No longer depends on: 2012433
Priority: -- → P1

We've been back on this a bunch of times but this would basically be a "failure to apply policy" event?

Whiteboard: [size=1]

(In reply to Gian-Carlo Pascutto [:gcp] from comment #1)

We've been back on this a bunch of times but this would basically be a "failure to apply policy" event?

Yes that's the intention

Blocks: 2015808
Severity: -- → S2
Target Milestone: --- → Pilot
Assignee: nobody → jneuberger

If the local policy status on the client does not align with the console policy status received through the policy poll after attempting to apply the policy

To clarify, this is not about local policies (json or registry), it's about the client failing to apply to remote policy so the local settings won't reflect what the console is sending out.

Target Milestone: Pilot → MVP
Flags: needinfo?(jneuberger)
Priority: P1 → P3
No longer blocks: 2012076

Should we refine this to be a "telemetry event sent when any error is reported at about:policies#errors"?

User Story: (updated)
Summary: Send security event in case of local policy inconsistency → Send telemetry event in case of policy errors
You need to log in before you can comment on or make changes to this bug.