deprecating symbols.mozilla.org/symbolication/ API endpoints -- please update

9 views
Skip to first unread message

William Kahn-Greene

unread,
Nov 8, 2021, 12:02:52 PM11/8/21
to crash-reporting-wg, stability
Hi!

Over the last year, I've been working on a new standalone symbolication API service. This service is codenamed Eliot. You can see it here:


Eliot went live in production a couple of weeks ago. I made some fixes last week, but it's looking good.

I'm hereby deprecating the old symbols.mozilla.org symbolication API endpoints in favor of their symbolication.services.mozilla.com counterparts.

Old service -> New service


Starting Tuesday, we're going to tweak nginx for symbols.mozilla.org to proxy all incoming symbolication API requests [1] to symbolication.services.mozilla.com.

While you're updating code and services to use the new service endpoint, I'd appreciate if you also did the following:

1. Upgrade from the v4 to v5 versions of the API. The v4 version has been deprecated for a while and I'd like to remove it.
2. Add a User-Agent HTTP header to your symbolication API requests. One of the problems I'm having with deprecating things is it's impossible to know what's using it.

The symbolication API documentation has been updated:


One thing to notice is that the v5 API returns line numbers and filenames for symbols.

If you have any questions, comments, or concerns, please reach out to me or ask on the #crashreporting channel on Matrix.

/will

[1] This is _only_ for symbolication API requests. This doesn't affect upload API or download API requests.

William Kahn-Greene

unread,
Nov 8, 2021, 8:15:34 PM11/8/21
to crash-reporting-wg, stability
Bah--I messed up the urls! They should be this:

Old service -> New service

Reply all
Reply to author
Forward
0 new messages