CODEWITHSUNDEEP
laravellaravel-5
simo
simo

Reputation: 24570

How to Log object?

I can see that Log facade is very useful. In the docs of laravel:

The logger provides the eight logging levels defined in RFC 5424: emergency, alert, critical, error, warning, notice, info and debug.

But, how would I log an instance of a model? like for example:

$user= User::find($user_id);

then, would it be possible to log the $user object?

Upvotes: 83

Views: 134912

Answers (6)

jannej
jannej

Reputation: 906

In Laravel 8 and beyond there is no need to use print_r() nor json_encode() in your log statements.

Use the second parameter to pass an array. For example:


Log::info('My message', ['user' => $user]);

// The Output will be

[2021-08-17 09:23:13] local.INFO: test {"user":{"App\\Models\\User":{"name":"Rosalia Mraz Jr.","email":"[email protected]","email_verified_at":"2021-08-17T07:23:13.604361Z","updated_at":"2021-08-17T07:23:13.000000Z","created_at":"2021-08-17T07:23:13.000000Z","id":29,"tax_rate":25}}}

Upvotes: 8

user3785966
user3785966

Reputation: 2980

You can log either by print_r or json_encode. json_encode is more readable.

For example:

use Illuminate\Support\Facades\Log;

Log::info(json_encode($user));

Upvotes: 42

Danbass07
Danbass07

Reputation: 29

This causes "allocated memory size exhausted" exception in some cases. (e.g native exception class) – Gokigooooks

Had same problem.

Log::info(print_r($request->user()->with('groups'), true ) );

Add ->get()

Log::info(print_r($request->user()->with('groups')->get(), true ) );

Upvotes: 0

Rob Fonseca
Rob Fonseca

Reputation: 3849

This will work, although logging the entire model will grow your log rather quickly.

Log::info(print_r($user, true));

The true in the second parameter of the print_r() method returns the information instead of printing it, which allows the Log facade to print it like a string.

Upvotes: 157

vkovic
vkovic

Reputation: 804

I've recently started using Laravel, so this certainly works in 5.3 and 5.4, not sure for earlier versions.

The quickest way I can think of (suits smaller objects) would be to cast object to array:

Log::debug((array) $object);

Yo may wonder how's this possible, first param of debug method (as well as error, notice and other logging methods in Log class) accepts string as first param, and we are passing the array.

So, the answer lays down deep in the log writer class. There is a method that gets called every time to support formatting the messages, and it looks like this:

/**
 * Format the parameters for the logger.
 *
 * @param  mixed  $message
 * @return mixed
 */
protected function formatMessage($message)
{
    if (is_array($message)) {
        return var_export($message, true);
    } elseif ($message instanceof Jsonable) {
        return $message->toJson();
    } elseif ($message instanceof Arrayable) {
        return var_export($message->toArray(), true);
    }

    return $message;
}

Also to clarify things little bit more, you can take a look into: https://github.com/laravel/framework/blob/5.4/src/Illuminate/Log/Writer.php#L199 and you'll see that formateMessage method is formatting the message every time.

Upvotes: 11

GiamPy
GiamPy

Reputation: 3560

No.

The first parameter must be a string (or a string object representation). If you wish to pass any other type of (raw) data or objects, you can always JSON encode them, and push them in the context settings, like so:

<?php 

$user = User::find($user_id);

\Log::error("Something happened to User {$user_id}.", ['object' => $user->toJson()]);

Or:

<?php

// User.php
[...]

class User 
{
    [...]

    public function __toString()
    {
        return "{$this->id}";
    }
}

// [...]
$user = User::find($user_id);

\Log::error("Something happened to User {$user}.", ['object' => $user->toJson()]);

You can find more information about the method signatures here.

Upvotes: 4

Related Questions