Production issues reporting - Revision history

Lymon Flowers: Add redirect

2025-05-26T16:22:55Z

Add redirect

← Older revision		Revision as of 18:22, 26 May 2025
Line 1:		Line 1:
	BGA implemented several production issues reporting tools:		#REDIRECT [[Studio logs]]BGA implemented several production issues reporting tools:

	* Syntax errors reporting		* Syntax errors reporting

Lymon Flowers: /* Events list view */ Add event list page

2025-05-21T15:57:43Z

Events list view: Add event list page

← Older revision		Revision as of 17:57, 21 May 2025
Line 138:		Line 138:

	===== Events list view =====		===== Events list view =====
			[[File:Issue events list.png\|frameless]]

			When clicking on the "Other events" tab, you will see the following view, which allows you to inspect a specific event. Usually, it is not needed since default event provides enough context, but it can still be used to compare several events.

Lymon Flowers: /* Issue detail view */ More screenshots on issue details

2025-05-21T15:53:03Z

Issue detail view: More screenshots on issue details

← Older revision		Revision as of 17:53, 21 May 2025
Line 78:		Line 78:

	[[File:Issue details.png\|frameless\|785x785px]]		[[File:Issue details.png\|frameless\|785x785px]]

			This page is separated into several blocks.

			====== Main information ======
			[[File:Issue main informations.png\|frameless]]

			This contains the main information of the issue, as seen in issues list:

			* '''Type of error''' (warning, error, exception name, etc.)
			* '''Description of error'''
			* '''Error ID'''
			* More detailed information and counters:
			** '''Priority:''' Sentry estimate of the criticality of this issue
			** '''Count:''' number of events
			** '''User count:''' approximate number of users impacted by this issue
			** '''First seen'''
			** '''Last seen'''

			====== Culprit ======
			[[File:Issue culprit.png\|frameless]]
			This summarizes where and the issue happens, with a source file position and a release.

			====== Stack trace ======
			[[File:Issue stack trace.png\|frameless]]

			This block contains information particularly useful to debug an issue. By default, only stack trace elements pertaining to the game code are shown. It is possible for frontend errors to toggle this behavior and show BGA frontend stack trace elements.

			Every element of the stack trace is clickable to see a hint on exactly when the execution was. Please note that some of this code is minified and hence is not very readable. However, it can still provide useful information. We plan to perhaps unminify this code later.

			====== Request ======
			[[File:Issue request details.png\|frameless]]
			This block contains details on the request, namely:

			* '''URL:''' complete URL of the request, but without the query string
			* '''Method:''' could be <code>GET</code> or <code>POST</code>
			* '''Query:''' all query parameters if any

			====== Tags ======
			[[File:Issue tags.png\|frameless]]

			List any relevant tags regarding this event.

			====== Statistics ======
			[[File:Issue statistics - histogram.png\|frameless]]

			This block contains an histogram of the issue events depending, either during last day or last month. Every bar is clickable.

			[[File:Issue statistics.png\|frameless]]

			Then, we have donuts-like statistics with a breakdown of the first 10 occurrences for:

			* browsers
			* device family
			* OSes
			* users
			* tables

			The more a stats impacts a browser, user or device brand, the more it is suspect that the issue is specific to them.

	===== Events list view =====		===== Events list view =====

Lymon Flowers: /* Views */ Add more details

2025-05-21T13:05:55Z

Views: Add more details

@@ Line 6: / Line 6: @@
 All of these are available at the bottom of your game studio page.  Access your game studio page (for instance: [https://studio.boardgamearena.com/studiogame?game=medina https://studio.boardgamearena.com/studiogame?game=xxx]) and scroll to the "'''Errors in production'''" block:
-[[File:Error reporting.png|center|thumb]]
 == Syntax errors reporting ==
@@ Line 47: / Line 48: @@
 ==== Views ====
 ===== Issues list view =====
 ===== Issue detail view =====
 ===== Events list view =====

Lymon Flowers: Add more context

2025-05-21T10:45:41Z

Add more context

@@ Line 9: / Line 9: @@
 == Syntax errors reporting ==
-This is the simplest reporting tool.  It only reports
+This is the simplest reporting tool.  It only reports PHP syntax errors.  When clicking on the button, you will be redirected to a page that lists all game servers and will display any syntax error.  Any of these is a fatal error and should be addressed with a new release.
 == Unexpected errors reporting ==
 == Backend & frontend issues reporting ==

Lymon Flowers: Basic layout

2025-05-21T10:14:05Z

Basic layout

New page

BGA implemented several production issues reporting tools:

* Syntax errors reporting
* Unexpected errors reporting
* Backend & frontend issues reporting

All of these are available at the bottom of your game studio page. Access your game studio page (for instance: [https://studio.boardgamearena.com/studiogame?game=medina https://studio.boardgamearena.com/studiogame?game=xxx]) and scroll to the "'''Errors in production'''" block:
[[File:Error reporting.png|center|thumb]]

== Syntax errors reporting ==
This is the simplest reporting tool. It only reports

== Unexpected errors reporting ==

== Backend & frontend issues reporting ==