Very chatty
The platform's logging framework is useful, but it emits a great deal of internal execution detail and is not well optimized for the Apex you actually wrote. Finding your own code in the output is work.
Live on AppExchange
Logging as a Service
Out-of-the-box logging support for Salesforce — for leadership, for the engineering community, and for business users. Visibility into custom functionality built on the platform, delivered as a trusted AppExchange managed package.
The problem
Three specific gaps in Salesforce's own logging.
Cannot be left on
Platform logging is enabled for a specific window rather than run continuously. So it is usually off at the moment the interesting event occurs, and you are reduced to reproducing the problem.
Not component-aware
It cannot be narrowed to one component, so it cannot be tuned to the part of the system under suspicion. For managed packages, retrieving logs at all can require Salesforce Support.
What LaaS is
LaaS provides out-of-the-box logging and troubleshooting support for developers, packaged as a Salesforce AppExchange managed package. It is intended to help while you are building custom functionality, and again later when you are diagnosing test and production issues.
It is a component-based logging infrastructure that can be tuned at run time, and it can monitor at user, group (profile), and org level.
There are no free lunches. Logging carries its own overhead in CPU, heap memory, and governor limits — the same limited resources as the code being logged. LaaS is tunable precisely so you can spend that budget deliberately rather than everywhere at once.
Who it is for
Any Salesforce platform developer can use the framework directly. Product support teams use it to troubleshoot customer issues, and managed packages gain insight into problems without going through Salesforce Support.
Leadership
CTOs, VPs, directors, managers
- Visibility into the quality of what engineering — in-house or system integrator — has built
- 5–15% saving in development and maintenance cost
- Traceability to business transactions, supporting SOX and internal audit
Engineering
Architects, developers, testers
- A standard framework available from day one
- Easier development, debugging, and interface troubleshooting
- No going back in time to find the root cause of a test or production issue
- 20–50% saving on production debugging, without changing production to add field-history tracking or asking customers for reproduction steps
Business users
Users, customers, auditors
- No need to supply steps to reproduce — engineering gets notified with detail in real time
- 10–25% less time spent reporting issues encountered in normal use
- On-demand compliance detail for SOX and internal audit
On the roadmap
Logging outside Salesforce
- Email support for a daily summary — activity overview and any exceptions reported
- External storage: saving logs to Amazon, Box, or Google Drive
- Output suitable for log aggregators such as Splunk
Cache
- A separate platform cache, so logging does not consume the user cache quota
Please base any buying decision on current functionality. The roadmap may change in response to user feedback and platform limitations.
Ready to try it?
The setup guide covers installation, the logging API, configuration, and reading the logs.