Closed Bug 1788681 Opened 3 years ago Closed 3 years ago

support UtilityActorsName annotation

Categories

(Socorro :: General, enhancement, P2)

enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: gerard-majax, Assigned: willkg)

References

Details

Attachments

(2 files)

In bug 1788596 we will want to use IPC actor names instead of sandboxing kind value to expose on crash reports. It will be a string, comma-separated actor names.

I dont know if we can / should get rid of the index put in place in bug 1767435 ?

Flags: needinfo?(willkg)

I looked through the linked bugs and the description, but I don't understand what you're asking.

Is the UtilityProcessSandboxKind annotation changing in some way? Is a new annotation being created?

Flags: needinfo?(willkg) → needinfo?(lissyx+mozillians)

Yes, a new one will be created

Flags: needinfo?(lissyx+mozillians)

In order to add support for a new annotation, I need to know what the annotation is and it needs to undergo data review.

https://socorro.readthedocs.io/en/latest/annotations.html#adding-new-crash-annotations-to-a-crash-report

(In reply to Will Kahn-Greene [:willkg] ET needinfo? me from comment #4)

In order to add support for a new annotation, I need to know what the annotation is and it needs to undergo data review.

https://socorro.readthedocs.io/en/latest/annotations.html#adding-new-crash-annotations-to-a-crash-report

Yes, that will be done in time, my question was what do we do with the existing one that we will remove from CrashAnnotations.yaml ? There will be some records with it for some time on server, but do we need to keep the index?

It depends on how people are using it. If they need to keep searching with it, then we should keep it around until the data has expired. If they don't need it anymore and don't care about past values, then I can remove it.

So the new way to report using the actor names is now landing, what do you need me to do / infos do you need to perform the indexing steps ? We are adding UtilityActorsName as a string in https://hg.mozilla.org/integration/autoland/diff/2ec48e5350225f026d247ee692f53a633fd76765/toolkit/crashreporter/CrashAnnotations.yaml

Flags: needinfo?(willkg)

I missed this somehow. Sorry about that.

First off, the type for the field in CrashAnnotations.yaml is wrong. It's marked as an integer, but it needs to be a string.

Can you fix that as soon as you can?

Typically, because the field is marked as being included in the crash ping, we can't change the type. However, in this case, no one has updated the crash ping schema and picked up this field, so we can still fix it without having to create a whole new field.

Flags: needinfo?(willkg) → needinfo?(lissyx+mozillians)
Flags: needinfo?(lissyx+mozillians)

Fixed with bug 1795888, really sorry about that, I clearly remember switching the type, I dont understand how it could have made it like that and not break any test ...

I verified that it's landed.

Data review was done here: https://bugzilla.mozilla.org/show_bug.cgi?id=1788596#c13

UtilityActorsName is a comma-separated list of names, so we should convert it in the processor.

I'll work on the following:

  • convert the value from "foo,bar,baz" to ["foo", "bar", "baz"]
  • make UtilityActorsName searchable and aggregatable in Super Search
  • update the crash ping schemas so the data is in telemetry.crash BigQuery table

Grabbing this and putting it in my queue.

Assignee: nobody → willkg
Status: NEW → ASSIGNED
Priority: -- → P2

Gentle ping, have you been able to do that?

Flags: needinfo?(willkg)

Not, yet. I'm hoping to in December.

Flags: needinfo?(willkg)

I'll do a prod deploy later this week.

willkg merged PR #752: "bug 1788681: add FontName and UtilityActorsName to crash ping" in bd40909.

This adds UtilityActorsName to the crash schema, so it'll show up in telemetry.crash.

Component: Database → General
Summary: Add Utility process actor names index → support UtilityActorsName annotation

I pushed this just now to production in bug #1803661.

Status: ASSIGNED → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: