Studio logs - Revision history

Thoun: /* BGA Production Logs */

2026-02-10T08:21:20Z

BGA Production Logs

← Older revision		Revision as of 08:21, 10 February 2026
Line 74:		Line 74:
	# Scroll to the bottom of the page		# Scroll to the bottom of the page
	# Click the `Display recent errors from production` button		# Click the `Display recent errors from production` button
	## [[File:~~How-to-access-bga-production-server-logs~~.png\|~~500px~~]]		## [[File:Production errors buttuns.png\|frameless\|458x458px]]
	==Backend & frontend issues reporting==		==Backend & frontend issues reporting==
	This is the next generation reporting tool. It is based on Sentry, a tool that aggregates any frontend and backend errors encountered by users. It allows modern statistics and gives more context.		This is the next generation reporting tool. It is based on Sentry, a tool that aggregates any frontend and backend errors encountered by users. It allows modern statistics and gives more context.

2025-05-26T16:22:18Z

Merge with Production issues reporting

@@ Line 1: / Line 1: @@
 {{Studio_Framework_Navigation}}
-Logs allows you to check out what happened recently on server and to debug your game.
+BGA implemented several production issues reporting tools:
+* Syntax errors reporting
-BGA Studio logs are available directly from your game development interface. You can also navigate to them: https://studio.boardgamearena.com/1/mygame/mygame/logaccess.html?table=######, where you replace mygame and ###### accordingly.
+* Unexpected errors reporting
+*Backend & frontend issues reporting
 == BGA request&SQL logs ==
@@ Line 74: / Line 75: @@
 # Click the `Display recent errors from production` button
 ## [[File:How-to-access-bga-production-server-logs.png|500px]]
 [[Category:Studio]]

2024-05-07T22:55:36Z

BGA unexpected exceptions logs

@@ Line 54: / Line 54: @@
 == BGA unexpected exceptions logs ==
 In this log you can check the last Unexpected exceptions from your game.
@@ Line 72: / Line 64: @@
 You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they
 are real warnings or errors (only the error log level will appear in production).
 [[Category:Studio]]

2024-05-07T22:48:03Z

BGA unexpected exceptions logs

← Older revision		Revision as of 22:48, 7 May 2024
Line 54:		Line 54:

	== BGA unexpected exceptions logs ==		== BGA unexpected exceptions logs ==

			=== How to access the server logs ===

			# Navigate to your game page on the Studio website
			## e.g. <nowiki>https://studio.boardgamearena.com/studiogame?game=YOURGAMEID</nowiki>
			# Scroll to the bottom of the page
			# Click the `Display recent errors from production` button
			## [[File:How-to-access-bga-production-server-logs.png\|500px]]

	In this log you can check the last Unexpected exceptions from your game.		In this log you can check the last Unexpected exceptions from your game.

2024-04-18T06:58:47Z

replace usage of self:: by $this->

← Older revision		Revision as of 06:58, 18 April 2024
Line 50:		Line 50:

	You can use special PHP methods in your PHP code to left some trace in this log:		You can use special PHP methods in your PHP code to left some trace in this log:
	* ~~self::~~trace( "your message here" ); // Display "your message here" in the log		* $this->trace( "your message here" ); // Display "your message here" in the log
	* ~~self::~~dump( "My variable", $variable_to_dump ); // Display the content of $variable_to_dump in the log		* $this->dump( "My variable", $variable_to_dump ); // Display the content of $variable_to_dump in the log

	== BGA unexpected exceptions logs ==		== BGA unexpected exceptions logs ==

2024-01-17T09:21:47Z

BGA request&SQL logs

← Older revision		Revision as of 09:21, 17 January 2024
Line 10:		Line 10:
	* When you want to check what SQL requests has been built during a request.		* When you want to check what SQL requests has been built during a request.
	* When you want to debug your PHP code using "self::trace"		* When you want to debug your PHP code using "self::trace"
	* When you want to know why a request takes too ~~many~~ time.		* When you want to know why a request takes too much time.

2022-05-16T23:17:02Z

← Older revision		Revision as of 23:17, 16 May 2022
Line 64:		Line 64:
	You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they		You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they
	are real warnings or errors (only the error log level will appear in production).		are real warnings or errors (only the error log level will appear in production).


			[[Category:Studio]]

2020-10-17T22:14:37Z

Link to access logs (when can't get to in game)

← Older revision		Revision as of 22:14, 17 October 2020
Line 1:		Line 1:
	{{Studio_Framework_Navigation}}		{{Studio_Framework_Navigation}}

	~~BGA Studio logs are available directly from~~ your game ~~development interface~~.		Logs allows you to check out what happened recently on server and to debug your game.

	~~Logs allows~~ you ~~to check out what happened recently on server~~ and ~~to debug your game~~.		BGA Studio logs are available directly from your game development interface. You can also navigate to them: https://studio.boardgamearena.com/1/mygame/mygame/logaccess.html?table=######, where you replace mygame and ###### accordingly.

	== BGA request&SQL logs ==		== BGA request&SQL logs ==

2020-04-15T21:16:18Z

Added navigation

← Older revision		Revision as of 21:16, 15 April 2020
Line 1:		Line 1:
			{{Studio_Framework_Navigation}}

	BGA Studio logs are available directly from your game development interface.		BGA Studio logs are available directly from your game development interface.

2016-10-14T12:28:13Z

BGA unexpected exceptions logs

← Older revision		Revision as of 12:28, 14 October 2016
Line 62:		Line 62:
	The SQL log is very verbose and sometimes it too hard to extract your tracing from it, in this case you can use error log for tracing temporarily.		The SQL log is very verbose and sometimes it too hard to extract your tracing from it, in this case you can use error log for tracing temporarily.
	You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they		You can add debug statement using self::warn() which will appear in that the log. Do not leave these tracing method calls after you done debugging unless they
	are real warnings or errors.		are real warnings or errors (only the error log level will appear in production).