Now that you've installed and configured Pharos in your sandbox instance, let's setup a live error feed from your production instance. In order to accomplish this Pharos will require an api connection to your production org. This connection will be used to read metadata via the tooling api. Pharos will never modify any of your production data or metadata via the api. Utilizing the tooling api allows Pharos to render rich visuals for Logs and Issues that it generates. This will provide you with the best production-like experience without actually installing the application in prod. Don't worry, this process isn't complex at all and requires only 2 steps. Let's get started!

1. Create a Connected Org

Simply Navigate to Pharos Admin -> Connected Orgs and follow the instructions in the video below.

2. Send Apex Exception Emails from Production

Now that we're connected to production, let's feed those exception emails to Pharos to make sense of. First, let's first grab the Pharos-generated email address that will capture those exception emails.

Note: this email address resides on the org where Pharos is installed. It is generated specifically for that org during Pharos configuration. Sending an email to this alias will capture this email within your org only. At no point during this process does any data travel to anywhere else but your org. Neither Pharos nor any other 3rd party processes or stores these emails.

To grab a hold of this email alias, follow the steps below:

Now that we have our address copied, the next step is to send your production errors to it. There are two ways to accomplish this. We recommend option (1) for its simplicity and low risk. 

1. Adding a Recipient to the Apex Exception Email Distribution List

This is by far the easiest method if you have access to this area of setup in your production instance. The process here involves adding a new recipient to the distribution list and will not impact anyone that's currently on that distribution list in production. Now, let's proceed with the steps below in your production instance:

If you get to the last step and find that the External Email Addresses field is not empty, simply scroll to the end of the text there, add a comma (,) or a semicolon (;) and paste the value after it. 

1.1 Send Production Flow Errors to Pharos 

This is optional but highly recommended especially if you are an admin. Devs would also do well to be aware of flow failures since these may overlap with apex triggers or other code. Pharos has some great functionality for visualizing and debugging flow errors. This section describes how to send flow errors to Pharos allowing you to experience the troubleshooting view on the Log and Issue details.

Additionally, by simply performing the steps below you will improve visibility into flow failures across your entire team. The default flow error reporting settings are just very, very wrong. So, let's change that!

If you find that your Process Automation Settings are already configured as shown in the video below, congratulations! You can safely skip this step and move on. Otherwise, login to your production instance and let's start.

Once you've added everyone to the recipient list, we are done! 

2. Forward Exception Emails From Your Inbox

This process will only work if you are currently receiving exception emails in production. If you are not on that recipient list, please add yourself first by following the steps below in prod:

Now that that's out of the way, we'll need to create a forwarding rule on your email client. The goal is to forward all salesforce production exception emails to a Pharos-generated email alias. Please refer to this knowledge article for forwarding instructions.