server | v3 switch to v4  

Photon Dashboard

Photon makes use of Windows Performance Counters as well as custom in-memory counters to track server performance and statistics, e.g. CPU load, memory usage, current connection count, operation execution time, etc.

To display these counters either Windows Performance Monitor or the Photon Dashboard can be used. The Dashboard is a simple application that ships with Photon, integrates a small web server and displays all counters on a monitoring web site. Photon is publishing it's counter values to the Dashboard via UDP, so that the Photon Dashboard can run on a different server and display counters from various Photon instances.

Photon performance counters are easily extensible and the display options can be fully customized.

Photon Server: Photon Dashboard Overview


Photon's Performance Counters

In-Memory Counters

Photon's applications are using in-memory performance counters to track application-specific statistics, e.g. the number of current games. These counters don't show up in the Windows Performance Monitor, but they are broadcasted to the Photon Dashboard.

Check the 2nd part of this tutorial for more information on Exit Games' performance counters and how to add your own performance counters to your application: Photon Dashboard Customizing

Back To Top

Windows Performance Counters

As the Photon Core is written in C++, it can not make use of Exit Games' in-memory counters. To track performance data, it relies on native Windows Performance Counters instead.

If you want to make use of these counters, you need to install them before you start Photon. This can be done in Photon Control:

Photon Server: Photon Dashboard install Counter

Check Windows' Performance Monitor to see the installed counters:

Photon Server: Photon Dashboard Performance Monitor

Photon is writing data to these counters automatically once it is started.

Back To Top

Publish Counters To The Dashboard

Publishing In-Memory Counters

In order to display the counters at the Photon Dashboard, the counter data needs to be published on a specific UDP port, on which the Dashboard is listening for the data.

The Lite Application is making use of a "CounterPublisher" class to broadcast the in-memory counter data. It can be enabled / disabled and it's port and IP can be configured in the /deploy/Lite/bin/Lite.dll.config:

    <section name="Photon" type="Photon.SocketServer.Diagnostics.Configuration.PhotonSettings, Photon.SocketServer"/<


    <CounterPublisher enabled="True" endpoint="" protocol="udp" sendInterface="" updateInterval="1" publishInterval="10" /<


This example is using a multicast IP - please note that you need to define specific IPs if Photon and Photon Dashboard are in different networks.

Back To Top

Publishing Windows Performance Counters

The native Photon Core can not publish it's counters directly, because it is using Windows Performance Counters and not Exit Games' in-memory counter. Therefore, Photon ships with a separate "Counter Publisher" application, which acts as a kind of proxy: it reads the values from Photon's Windows Performance Counters, temporarily adds them to in-memory counters and publishes them.

In addition to the Photon Core Counters, the CounterPublisher Application reads and broadcasts some Windows System Counters, like the CPU load, memory usage etc.

The CounterPublisher Application is enabled by default; it's publishing behavior can be configured as described above, the settings can be found in the /deploy/CounterPublisher/bin/CounterPublisher.dll.config.

The following schema shows which types of performance counters are used by the different parts of Photon, and how they are published:

Photon Server: Photon Dashboard Photon Schema

Back To Top

The Photon Dashboard

The Photon Dashboard is a service that receives the performance counter data which is published by Photon's CounterPublisher. It's making use of the RRDTool library (see for more info) to store and display the data and it comes with an internal webserver to render HTML sites with performance graphs.

Back To Top


The Dashboard can be installed and started from Photon control:

Photon Server: Photon Dashboard Install Photon Server: Photon Dashboard Start

Back To Top

Web UI

The Dashboard comes with a built-in web server. By default, you can acess it on https://localhost:8088/, or you can use the Photon control to open the Dashboard:

Photon Server: Photon Dashboard open UI

In the upper left corner of the Dashboard site, you'll find a list of all machines that are publishing counter data to this Dashboard, as well as a list of all applications from which the published counters are originating. Choose the appropriate machine / application to find the counters you are interested in.

Photon Server: photon Dashboard UI

Back To Top

Configuration Options 

Use the configuration file at /deploy/bin_tools/dashboard/PhotonDashboard.exe.config to configure various Dashboard settings.

The IP and port for access to the Photon Dashboard web interface can be set in the "appSettings" section:

    <add key="ImagePath" value="Images"/>
    <add key="ImageUpdateInterval" value="10"/>

    <add key="WebIp" value=""/>
    <add key="WebPort" value="8088"/>

The IP and port at which the dashboard can receive performance counter data is set at the "endpoints" section. Make sure that the ports correspond to the ones you configured for the Counter Publisher. You can also add multiple entries here, e.g. if you want to receive data on several ports. An IP of "" means that the Dashboard is listening on all available network interfaces.

      <add  address="" port="40001" protocol="udp"/>

      <add  address="" port="40501" protocol="udp"/>

Back To Top


If graphs are not created or displayed as expected, check the following:

  • Is the Counter Publisher application enabled? Check the configuration at /deploy/CounterPublisher/bin/CounterPublisher.dll.config.
  • Are Counter Publisher and Dashboard configured to use the same IP, port and protocol for sending and receiving counter data?
  • Make sure that the appropriate ports are open in the firewall, if Counter Publisher and Dashboard are not running on the same server.
  • Make sure that the Dashboard has write access to /deploy/bin_tools/dashboard/Images and /deploy/bin_tools/dashboard/PerfData.
  • Check the log file at /deploy/bin_tools/dashboard/log for errors.

To Document Top