Bug 1739447 Comment 4 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
The plan is to deploy on Tuesday and push the proxy configuration out.

I sent an email to stability and crash-reporting-wg working groups with this in it:

> 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
> 
> * https://symbols.mozilla.org/symbolication/v4   ->   https://symbolication.services.mozilla.com/symbolication/v4
> * https://symbols.mozilla.org/symbolication/v5   ->   https://symbolication.services.mozilla.com/symbolication/v5
> 
> 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:
> 
> https://tecken.readthedocs.io/en/latest/symbolication.html
> 
> 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.
Revision 1 by
on 
The plan is to deploy on Tuesday and push the proxy configuration out.

I sent an email to stability and crash-reporting-wg working groups with this in it:

> 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
> 
> * `https://symbols.mozilla.org/symbolication/v4`   ->   `https://symbolication.services.mozilla.com/symbolication/v4`
> * `https://symbols.mozilla.org/symbolication/v5`   ->   `https://symbolication.services.mozilla.com/symbolication/v5`
> 
> 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:
> 
> https://tecken.readthedocs.io/en/latest/symbolication.html
> 
> 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.

Note that this _only_ affects the symbolication API. The uploads and downloads APIs will continue to be at `symbols.mozilla.org`.
Revision 2 by
on 
The plan is to deploy on Tuesday and push the proxy configuration out.

I sent an email to stability and crash-reporting-wg working groups with this in it:

> 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
> 
> * `https://symbols.mozilla.org/symbolicate/v4`   ->   `https://symbolication.services.mozilla.com/symbolicate/v4`
> * `https://symbols.mozilla.org/symbolicate/v5`   ->   `https://symbolication.services.mozilla.com/symbolicate/v5`
> 
> 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:
> 
> https://tecken.readthedocs.io/en/latest/symbolication.html
> 
> 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.

Note that this _only_ affects the symbolication API. The uploads and downloads APIs will continue to be at `symbols.mozilla.org`.

Back to Bug 1739447 Comment 4