No designated place for traceback in message item #471

Activity

1. ArturMoczulski

   self-assigned this

   on Sep 28, 2019
2. brianr commented on Sep 30, 2019

   

   brianr

   on Sep 30, 2019

   Member

   More actions

   @ArturMoczulski FWIW: at the API level, the current idea for these is that "message" items that contain tracebacks would be reported as tracebacks containing an explicit message. In those the message goes in trace.exception.description.
3. zanderwar commented on Apr 8, 2020

   

   zanderwar

   on Apr 8, 2020

   More actions

   +1 Please, this would be really great and I personally need it to go alongside SQL errors that I catch, and can only get the backtrace to appear in occurrences as @ArturMoczulski mentions
4. zanderwar commented on Apr 8, 2020

   

   zanderwar

   on Apr 8, 2020

   Last edited by zanderwar

   More actions

   This is good enough for me atm

   function reportSqlError($sql, $error)
   {
   	$message = "SQL ERROR: {$error}\n\n";
   
   	// maintain the layout, but reduce any excessive tabs or spaces
   	$message .= preg_replace('/\t\s?/m', '', trim($sql)) . "\n\n";
   
   	// build backtrace
   	$e = new Exception();
   	$trace = explode("\n", $e->getTraceAsString());
   
   	// reverse array to make steps line up chronologically
   	$trace = array_reverse($trace);
   
   	// remove {main}
   	array_shift($trace);
   
   	// remove call to this method
   	array_pop($trace);
   
   	// renumber items
   	$length = count($trace);
   	$result = array();
   
   	for ($i = 0; $i < $length; $i++)
   	{
   		$result[] = ($i + 1)  . ')' . substr($trace[$i], strpos($trace[$i], ' ')); // replace '#someNum' with '$i)', set the right ordering
   	}
   
   	$message .= implode("\n", $result);
   
   	\Rollbar\Rollbar::log(\Rollbar\Payload\Level::CRITICAL, $message);
   }
   

   
5. troygilbert commented on Sep 5, 2023

   

   troygilbert

   on Sep 5, 2023

   More actions

   Glad I'm not the only one suffering this issue, but so sad to see it's been like this for 4+ years!? I don't understand why the backtrace can't be used identically to what happens when there's an exception thrown? Is there any movement on this from the Rollbar PHP maintainers?
6. danielmorell

   assigned

   danielmorell

   and unassigned

   ArturMoczulski

   on Sep 15, 2023
7. danielmorell commented on Sep 15, 2023

   

   danielmorell

   on Sep 15, 2023

   Collaborator

   More actions

   Let me see if I can get this in either v4.1 or v4.2. For now, I will aim at v4.1.
8. danielmorell

   added this to the v4.1.0 milestone on Sep 15, 2023
9. troygilbert commented on Jan 3, 2024

   

   troygilbert

   on Jan 3, 2024

   More actions

   Any movement on this?

   As a stopgap, are there any tools that can prettify the data contained in the backtrace field? I thought it was PHP serialized, but I'm unable to deserialize it, so I must be missing something.
10. danielmorell

    modified the milestones: v4.1.0, v4.2.0 on Mar 1, 2024
11. danielmorell

    added

    Status: 3 - ConstructionThe request is being worked on.The request is being worked on.

    on Mar 1, 2024
12. danielmorell

    modified the milestones: v4.2.0, v4.3.0 on Nov 25, 2025
13. danielmorell commented on Oct 16, 2026

    

    danielmorell

    on Oct 16, 2026

    Collaborator

    More actions

    I was thinking about this and have a few ideas.

    The Rollbar backend is designed to accept different types of items. Typically, if you were to send a log message you would do something like this...

    Rollbar::log(Level::INFO, 'Message from app');

    However, what you send determines the "type" of item that is sent to the Rollbar backend by the SDK. If an exception is the item being sent a full stack trace is included by default.

    This sends a log that contains a full stack trace...

    Rollbar::log(Level::INFO, new Exception('Message from app'));

    The main downside is that this shows up labeled "Exception: Message from app". This is probably not the ideal way to identify a "log" from your app. But this is also easy to change.

    /**
     * Not intended for throwing, just for sending to Rollbar.
     */
    class BacktraceLog extends Exception {}
    
    Rollbar::log(Level::INFO, new BacktraceLog('Message from app'));

    This now creates a new item in Rollbar titled "BacktraceLog: Message from app". It includes a full stack trace and message that was logged.
14. danielmorell commented on Nov 6, 2026

    

    danielmorell

    on Nov 6, 2026

    Collaborator

    More actions

    After an internal conversation we have determined to make this something supported by the core SDK. It will be resolved in v4.3.0.