We at Pharos are constantly looking for ways to improve. Just like Pharos is making your org better by providing visibility into problem areas, our team is also embracing a proactive approach when it comes to customer experience. As much as we strive for perfection, we know that issues will happen. When problems do occur Pharos generates an internal log. These logs don’t contain any information from your org but rather elaborate on failures in our own code. We’d love to see that data and tackle your Pharos issues before you even have a chance to run across them.
There are 2 ways that your Pharos error data could get to us.
- Automated Error Reporting
- Manual Error Reporting
Both methods are passing the same data the only difference is that automated error reporting passes multiple logs instead of a single log to us. Another key difference between the two is that manual error reporting is user initiated, from a Pharos log record.
Automated Error Reporting Data Collection Process
Automated error reporting is performed weekly during the weekend. This process involves sending one or more emails to our error collector alias (errors@pharos.ai). These emails contain a list of log records that were generated by Pharos. More specifically, we're interested in logs with either:
- Category = Pharos Error
- Functional Area = Pharos
Data We Collect
The table below outlines all data points collected as well as details around each data point. All of the data we collect is Pharos-generated for the purposes of troubleshooting only. We never share this data with 3rd party. This data is used to improve our application and provide you with a better experience.
We collect the following attributes from a Pharos Log record:
| Pharos Log Attribute | Details |
| Organization Id | We already know your Organization Id through the native Salesforce license manager. We need this value to be included with the log record on the error report so that we can associate it with your account. |
| First Occurred On | Date and time of the first occurrence of this error. This is required for troubleshooting and accurate tracking. |
| Occurred On | The actual date of occurrence of this particular log. This is required for troubleshooting and accurate tracking. |
| Type | Type is part of a Pharos-generated classification. Usually for Pharos errors this value is set to Apex. We'd like to ensure that all Pharos logs are tagged appropriately in your system. |
| Category | We'd like to ensure that all Pharos logs are tagged appropriately in your system. This value should be Pharos Error. |
| Functional Area | We'd like to ensure that all Pharos logs are tagged appropriately in your system. This value should always be Pharos. |
| Summary | Summary of the error. This is required for troubleshooting and accurate tracking. |
| Details | Full error message along with a stack trace. The stack trace may sometimes contain Salesforce record ids, which are salesforce generated keys to uniquely identify records within their system. This is required for troubleshooting and accurate tracking. |
| Total Occurrences | Total number of occurrences of this error. This is required for troubleshooting to understand the impact and frequency. |
| Reported By Name | Name of the user on whose behalf Pharos submits the automated error report. This user will be our main point of contact for troubleshooting should we need their assistance. |
| Reported By Email | Email of the user on whose behalf Pharos submits the automated error report. This user will be our main point of contact for troubleshooting should we need their assistance. |
Manual Error Reporting
To access the manual error reporting feature, navigate to a log record with either Category = Pharos Error or Functional Area = Pharos. These types of logs will have an "Error Report" button accessible from the record header. It's important to note that other types of logs will not surface this button.
Upon pressing the button you will be presented with an error report form similar to the following:
Comments
0 comments
Article is closed for comments.