Skip to content

Instantly share code, notes, and snippets.

@rkst

rkst/logplex-changes.md

Last active August 29, 2015 14:04
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save rkst/52f4d45545284eecf6bb to your computer and use it in GitHub Desktop.
Save rkst/52f4d45545284eecf6bb to your computer and use it in GitHub Desktop.
Download ZIP
Raw
logplex-changes.md

Goodbye logplex_token, Hello log_input_url

Rather than provide a log token, we’ll now send a full URL, log_input_url. In the future, EU app logs will be serviced by logging infrastructure in the European region, which will be great news for customers concerned about data transit and residency.

The full documentation for this integration is available here. We will be migrating completely to these changes by October 15th, 2014.

Log input is now opt-in

Any add-on that had stored the logplex_token could use it to send log lines to an application. This method is being phased out and replaced by one that requires providers who wish to input logs to opt-in by adding “log_input” to the requires property of their add-on manifest.

Migrating from logplex_token

If you’re already using logplex_token to send us logs, then there are a number of steps you need to take to continue sending logs.

First, update the add-on manifest as described above to opt-in to the new approach. You must migrate to using log_input_url as soon as possible for all new provision requests.

All existing apps should then be updated to use log_input_url; you can obtain the URL for existing apps via the App Info API.

The use of logplex_token will be retired on October 15th, 2014. After that date, the field will no longer be available from the App Info API or provision requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment