Introduction
In this article, we'll review the core Salesforce objects used in the SightLane platform and their basic roles. A few additional minor objects are used in utility functions, but these represent the elements that should be familiar to Salesforce admins, developers, and architects. The following image represents the objects described in this article.
SightLane Objects
Monitor (sightlane.SL_Monitor__c) - A Monitor record is a collection of "settings" that determine how Events of a certain type will behave (including how and when they will be monitored). In addition, the monitor allows users to pre-configure Event Responses, Monitor Groups, Insight data, and other related records. Though the monitor is not strictly a "parent" to the Event, it is used to group similar events together in the SightLane interface.
Event (sightlane.SL_Event__c) - The Event object represents one single execution of a monitored process. For example, if you have defined a monitor that governs visibility behavior for one of your AutoLaunch Flows, then a new Event record will be created each time the Flow is executed. At the code level, an event can be recorded at any scope, from a single methods execution to a complex process that crosses multiple classes and transactions.
Archive (sightlane.SL_Archive__c) - The Archive is (almost) a clone of the Event object and is used to store older Events that are due to be purged from the system. Monitor developers can specify exactly how long it is before an Event record is "converted' to an Archive record AND exactly how long an archive record remains in the system before it is purged (deleted). Using this two-phased storage approach, teams can keep recent data right in front of them while preserving the ability to search for older monitoring data if it is needed.
| Note: Event and Archive objects do not have Master-Detail or Lookup Relationships to the Monitor object. This is done purposely to avoid data skew and UNABLE_TO_LOCK_ROW errors during periods of heavy monitoring activity. They each store the Salesforce ID of their associated monitor as a text field (called Monitor ID). |
Event Response (sightlane.SL_Event_Response__c) - This object holds configuration data regarding response actions for individual monitors. Responses have different types (email notification, Case creation, Flow execution, etc.) and are executed automatically following the completion of an Event. A more complete description can be found in the Response documentation articles.
Monitor Group (sightlane.SL_Monitor_Group__c) - Monitor Groups are simple objects that establish a unique name for a collection of logically related monitors (e.g., "Batch Jobs"). This allows SightLane to display groups of monitors together in functional categories, as seen in the Control Center.
Monitor Group Member (sightlane.SL_Monitor_Group_Member__c) - Monitor Group Members are junction objects that associate a Monitor with a Monitor Group. The relationship is many-to-many, and a Monitor can belong to multiple groups.
Insight (sightlane.SL_Insight__c) - Insights are a new and powerful capability that enables teams to share findings and lessons learned from Event analysis for the sake of solving future issues more quickly. The Insight object includes insight type, comments, links to external learning resources, and more.
Monitor Insights (sightlane.SL_Monitor_Insight__c)—If an Insight applies to every Event for a particular Monitor, it can be associated universally with all Events under that monitor. The Monitor Insight is a junction object that ties insights to the Monitors to which they apply.
Summary
The SightLane object model is designed to balance platform speed and efficiency with User convenience and accessibility. Understanding the basic pieces described in this article is a great first step toward determining how the SightLane platform can best help your Salesforce team and your organization.
Comments
Please sign in to leave a comment.