Simply select the addon from the List of Heroku addons. Select either a free or paid plan from the list. You will then be asked for the Heroku application name that you would like to add the addon to. Select the relevant application. Your Heroku app will be immediately configured with Logentries and all your application log events will be sent to your new Logentries account. Log in to your account to get automatic alerting set up (see below).
In a terminal, navigate to your apps directory and run the following command:
heroku addons:add logentries:XXX
Instead of XXX type in plan name from the list, such as
entry. Your Heroku app will be immediately configured with Logentries and all your application log events will be sent to your new Logentries account.
HTTPS drain gives you maximal flexibility in terms of managing multiple applications within and outside Heroku. To set up https drain, you have to add a new log in Logentries. Create a new Log and select Token TCP and Register the log, you will receive a unique Token UUID which will be printed under the form and then beside the log name in the list of logs. Then, let Heroku know where to send your log entries. Add a Heroku HTTPS drain
heroku drains:add https://heroku.logentries.com/v1/drain/*LOG-TOKEN*
Your log entries will now be available in the newly configured log in Logentries (you may need to hit the Logentries refresh button to see the new events).
On paid Heroku plans, log events and alerts occur within Logentries immediately. On free Heroku plans, events may be delayed by approximately 3- 15 seconds.
Select the Alerts tab in the Log view. From the list of alerts, remove an alert by selecting the Remove menu option (displayed on the right of each alert) twice.
However, do keep in mind for production applications that many error events lead to poor performance or dropped user requests.
L10 Errors indicate that the number of log messages being generated has temporarily exceeded the rate at which they can be delivered and Logplex, Heroku’s logging system has discarded some messages to catch up.
A common cause of L10’s is a sudden burst of log messages from a dyno. Logplex limits the total number of un-transmitted log messages it will keep in memory to 1024 messages. A burst of lines from a dyno with stacktraces for example, can overflow buffers in Logplex resulting in older messages being discarded in favor of newer ones.
By default, PHP users will only see heroku logs in their log drain. To see your PHP logs, you need to tail your app’s logs to STDOUT.
See lines 63 and 66 here on tailing an
app_log file which you can then append text to and it will be written to STDOUT and picked up by Heroku.