> For the complete documentation index, see [llms.txt](https://logbox.ortusbooks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://logbox.ortusbooks.com/master/usage/using-a-logger-object/usdtostring-and-extrainfo-argument.md).

# $toString() and ExtraInfo Argument

When using any of the logging methods like `info()`, `debug()`, `warn()`, etc, they all take two arguments:

1. The message to log 
2. An `extraInfo`argument which can be anything you like. 

This `extrainfo` argument can be a simple value, a CFC, a complex object and pretty much anything you like. The appenders get this `extraInfo` argument and process it into their appropriate destinations by serializing its value. This is done by using the following algorithm:

1. If it is a simple value, then just use it.
2. If it is an object then check if the object has a method called `$toString()`. If the method exists, then call `$toString()` and use its return value.
3. If it is an object with no `$toString()` method, then marshall its representation into XML format.
4. If it is a complex variable like a struct, query, array, etc, then marshall it into JSON format.

As you can see from the algorithm above, you can use the `extraInfo` argument to your benefit to save serialized representations of data to the appenders and then retrieve or re-inflate them later. The `$toString()` convention is great because you have complete control on how a CFC will serialize to its string representation. Let's see an example on a simple CFC:

```javascript
// User.cfc
component{

    function $toString(){
        // return my representation as a comma list of values of my properties
        return "#getName()#,#getAge()#,#getEmail()#";
    }
}
```

So when this object is sent to a logger's method, it will detect it is an object and the `$toString()` function exists and call it for serialization.

```javascript
user = userService.getUser( rc.id );

// need to log it.
if( log.canDebug() ){
    log.debug( "User just got logged in right now!", user );
}
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://logbox.ortusbooks.com/master/usage/using-a-logger-object/usdtostring-and-extrainfo-argument.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.