Log messages using LWC with lightning/logger

-

The lightning/logger module offers a convenient way to enhance the observability of your Lightning web components by using the Custom Component Instrumentation API. You can use the log() function to create custom messages and log them from your components to Event Monitoring. It is important to note that lightning/logger can only be used in the Lightning Experience, and is not available in the Salesforce mobile app. To use lightning/logger, you must ensure that Event Monitoring is enabled in your org and that the "Enable Lightning Logger Events" toggle is set to On. The lightning/logger module has only one method, log().

This isn't supported for Aura components

According to Salesforce documentation, this change is only available for customers who have purchased Salesforce Shield or Salesforce Event Monitoring add-on subscriptions.

Enable Event Monitoring Settings



















Here's an example from Salesforce

In JavaScript, import the log from lightning/logger and use it in the handleClick function. In this example, clicking on the button creates an object that is passed to Event Monitoring.The following example logs a click from within a button component. The log() function can be used for any event.

LWC HTML

<template>
    <lightning-button label="Approve" onclick={handleClick}>
    </lightning-button>

</template>

LWC JS 

import { LightningElement } from 'lwc';
import { log } from 'lightning/logger';

export default class HelloWorld extends LightningElement {
    handleClick() {
        let msg = {
            type: "click",
            action: "Approve"
        }
        log(msg);
   }

}

Once an Event Log is created from LWC, using the following query,

SELECT Id, EventType, CreatedDate, LogFileLength, LogDate, ApiVersion, LogFileContentType, Sequence, Interval, LogFile FROM EventLogFile WHERE Interval = 'Hourly' AND EventType = 'LightningLogger'

We can use the ELF Browser application by clicking this link: https://salesforce-elf.herokuapp.com. Note: Salesforce Event Log File Browser is not an official Salesforce tool.





Resources

Lightning Logger Event Type

lightning/logger Documentation

Event Monitoring

Get Started with Event Monitoring

Monitor Component Events with Custom Component Instrumentation API

Comments

Post a Comment

Popular posts from this blog

Introduction to Salesforce Agent Script: Build Predictable AI Agents

-
Image
Please visit here for more details - https://ayaninsights.com/guestblogs/introduction-to-agent-script/ In my latest blog, I introduce Salesforce Agent Script and explain how it helps teams build AI agents that are more predictable, controlled, and aligned with business processes. Large language models are flexible, but relying only on natural-language instructions can sometimes produce inconsistent results. Agent Script addresses this challenge by combining the conversational capabilities of an LLM with structured business logic. The blog explains how developers can use conditions, variables, actions, topics, and transitions to control how an Agentforce agent behaves. Agent Script supports familiar logic such as if/else conditions, value comparisons, sequential actions, and checks for missing data. I also cover its core structure, including system settings, configuration, global variables, languages, connections, and topic blocks. The start_agent topic acts as the entry point for each...
Read more

Anti-Patterns in Salesforce Agentforce: What to Avoid When Building AI Agents

-
Image
Salesforce Agentforce is powerful because it allows teams to build AI agents that can understand user intent, retrieve grounded information, execute actions, and support business workflows across Salesforce. But like any powerful platform, the quality of the implementation matters. A good Agentforce implementation does not start with “How many things can the agent do?" It starts with “What problem should the agent solve reliably?” That is where anti-patterns come in. Anti-patterns are common implementation habits that look useful at first but eventually create confusion, poor user experience, inconsistent answers, or hard-to-maintain agents. Below are some of the most common Agentforce anti-patterns and how to avoid them. 1. Trying to Build One Agent That Does Everything One of the biggest mistakes is designing a single agent to handle every business process, every department, and every possible customer question. At first, this feels efficient. One agent, many use cases. Bu...
Read more

MCP vs. Traditional APIs: Choosing the Right Integration Approach

-
Image
Enterprise integration has traditionally been built around APIs. Applications send structured requests, services process them, and predictable responses are returned. This model has supported everything from payment processing and customer portals to mobile applications and large-scale system integrations. The rise of AI agents introduces a different integration challenge. An AI agent does not always follow a fixed sequence designed in advance. It may need to determine which system to use, discover the operations available to it, gather relevant context, and select the appropriate action based on a user’s request. This is where the Model Context Protocol, or MCP, becomes relevant. MCP and traditional APIs are related, but they solve different problems. APIs expose system capabilities. MCP provides a standardized way for AI applications to discover and use those capabilities as tools and contextual resources. Understanding this distinction is important when designing enterprise AI solut...
Read more