Logentries Docs

Engine Yard


Engine Yard Log Management. Get up and running in minutes.

Install the Add-on

Install the Logentries Add-on from the Engineyard dashboard.


Prepare the Logentries Chef Recipe

Clone the Logentries recipe to your local development environment using the following git command:

git clone git://github.com/logentries/eycloud-logentries.git

Next, modify the recipe with your Logentries API key. This API key is found by clicking Show Vars underneath the Logentries button in your Engineyard dashboard.

Navigate to the following chef file

eycloud-logentries/cookbooks/le/attributes/recipe.rb

and modify the following line with your copied Logentries API key:

le_api_key('YOUR_API_KEY_GOES_HERE')

To configure the logs you would like to send from your EngineYard instance to Logentries, modify the following file

eycloud-logentries/cookbooks/le/recipes/configure.rb

Simply include the log files you would like to monitor.
By default the following files are configured to be sent to Logentries:

"/var/log/syslog",
"/var/log/auth.log",
"/var/log/daemon.log",
"/var/log/nginx/#{app_name}.access.log"

Some other logs you may be interested in adding to your Logentries account are listed here.
For information on what logs may be important for you check the introduction to Linux /var/log files and important Engine Yard logs.

/var/log/engineyard/apps/#{app_name}/production.log    # Production log

/var/log/nginx/#{app_name}.error.log                   # Nginx error log

/var/log/mysql/mysql.log                               # Mysql logs
/var/log/mysql/mysql.err

/var/log/chef.mail.log                                 # Chef log

/var/log/daemon.log                                    # Information logged by background daemons
/var/log/dmesg                                         # Kernal info
/var/log/messages                                      # Global system messages including mail, cron, daemon, kern, auth, etc.
/var/log/boot.log                                      # Boot info
/var/log/mail.log                                      # Mail server info
/var/log/user.log                                      # User level log info

Upload the Logentries Chef Recipe

Next upload the recipe to your EngineYard environment:

ey recipes upload -e ENVIRONMENT_NAME

Then run the chef script either by clicking the “Apply” in the Engineyard UI, or by running the following command:L

ey recipes apply -e ENVIRONMENT_NAME

Log into your Logentries account (or refresh your account page) and you will see your EngineYard instance configured with the specified logs. Note it usually take a few minutes for the chef script to complete. When you see your EngineYard instance in your account you can easily test that logs are being sent from your instance. SSH into your instance and run the following command:

logger 'this will log a test event to syslog'

Troubleshooting

Check if the agent is running correctly on your instance with the following command:

sudo /etc/init.d/logentries status

If you want to follow more files after applying the recipe, use the following command, where filename is the name of a logfile with the full path if in a different directory:

le follow filename

Note, that after you follow a new file you need to restart the logentries service with the following command:

sudo /etc/init.d/logentries restart
Back to Top