Log Files

Where Are The Logs

 

EMAILS SENT FROM THE WEBSITE:

Property Update Emails

To see if we attempted to send a property update email to one of our client's leads, check the AWS logs: rg2-email-updates-prod.

Click Search Log Group, then enter the leads email address with quotes in the search box.

Welcome Emails 

To check if a sign-up autoresponder email from the website was sent to the lead, you would check in rg2-production 

If they have a live site, check rg2-ssl-production

From there, you would put the lead's email address in quotes and search by the subject of the sign up autoresponder email.

 

EMAILS/TEXTS SENT FROM THE LEAD MANAGER:

Agent Notification Emails

Notification emails that we send to our clients and their agents can be found in lm-worker-prod

The above doesn't include the status of those emails. So you may need to check lm-web-api or lead-manager-web-prod

Agent Notification Texts

You have to search the lead manager web server logs in cloudwatch for:
"---Notification-Delivery---"

The webservers flip back and forth between web and api so you have to look in lm-web-api and lm-web-prod 

Lead Export Emails

To see if a lead export email was sent out: lead-manager-web-prod or lm-web-api.

Enter the user's email address with quotes and "Lead export complete" in the search box.

Emails sent directly to leads from within the Lead Manager UI:

In all cases, one of the best things you can do is try to look for the
message in the user's sent folder. If you find it there, any
deliverability problems are almost certainly downstream from RG systems.

If that doesn't work, you can look for clues in our logs. Information
here was gleaned from the Lead Manager source, specifically the files:
app/jobs/standalone_message.rb, app/mailers/standalone_message_mailer.rb, and lib/user_smtp.rb

  • Is the sender one of a couple dozen users at liebowitzrealty.com?
    If so, the email goes out via Amazon SES, so information about
    delivery status can be found in the same logs you'd search to find
    agent notification emails.
  • Does the sender have a Microsoft email account linked?
    If so, the email gets posted via HTTP to Microsoft's Outlook API.
  • Does the sender have a Gmail account linked?
    If so, the email gets delivered via an SMTP connection to Google's
    servers.
  • Does the sender have a different SMTP server linked?
    If so, the email goes out via that server.

If the email appears to have been delivered normally, nothing will be
logged.

If there is an SMTP authentication error or other exception, Lead
Manager will write messages to the lm-worker-prod logs and attempt to
send a bounce notification email. See the code in github
for exactly what gets written to the logs, but in general you can search
for the string smtp-auth-error and poke around from there.


If the user is using RG email sync, you might have another chance at
finding out what happened to the email. We retain basic metadata (sent
timestamp, from, to, and subject line, but not the body or other
headers) for all email messages processed by email sync for one week.
Check https://email-sync.realgeeks.com, locate the user, and try
searching their messages.

If you don't find a message there, it could just mean that the user
recently disabled and re-enabled RG email sync, which will cause
email-sync to purge all messages related to the account. Timestamps on
the account might offer you some clues here.

 

EMAILS REGARDING LEADROUTER/API:

Lead Routing Email

Email related to our API as well as integrated services like BombBomb, Mojo, DotLoop, Zapier, Realvolve and others can be found in AWS: leadrouter-distributor-prod

 

Cool, so how do I use those things?

Our logs are currently in 2 locations.

Most can be found at https://papertrailapp.com/ while some are found in AWS at https://console.aws.amazon.com/cloudwatch/home?region=us-east-1#logs

Here's an example of searching in papertrail for a specific email on the 862991-app8 system:

Once you find a log for that email, you will then take the hash to get all the logs for the specific event:

 To view the logs at cloudwatch, first click the Logs tab, then search for the log group such as 'rg2-email-updates-prod' or ''lm-web-api' then click the 'Search Log Group' button under the Logs tab.

 

Once here, put your search in quotes such as this example:

 

Context.io

context.io emails go to the lead_router, which are then sent to the lead manager as activities
email_sent and email_received
those are logged as activities and added to the "Emails" tab on the lead manager, for that agent