Author: Fred41
Author Website: https://github.com/fred41

Version: 29.08.2014

Short description: A little tool for monitoring (up to 4) arma3 server instances in a window
Date: 2014-08-29 17:13
Submitted by: Fred41


Comments: (3)
Rating:



 



Arma Server Monitor - Windows

by
Fred41


Description:
ASM is a little program, for monitoring some interesting values from multiple server (or HC) instances.
Performance related values like:
simulation cycles per second average (FPS)
simulation cycles per second minimal (FPSmin)
condition evaluations per second (CPS)
number of alive players (PL#)
number of alive server local AI units (AIL)
number of alive server remote AI units (AIR)
number of mission objects (OC[0..2], free configurable)
amount of allocated physical memory (MEM)
name of running instance
name of running mission
are displayed, simultaneously for multiple (up to 4) server instances, in a window.

The idea behind it, is to provide a fast and easy "state of health" overview at one go.

More information about this project can be found on the official Github page:
- github.com/fred41


Features:
- monitors up to 4 server (or headless client) instances simultaneous
- introduces a performance value CPS for FSM processing analysis
- very simple, compact and solid design
- almost no influence to cpu load
- easy to use (mini addon)
- customizable, moveable history graphs, up to 24h record to RAM (ringbuffer)
- logs to text file, individual for each instance, mission, interval configurable


Installation:
Please always update ALL files together (data structures of interface are sometimes changing)!

Extract into the ArmA 3 Directory, by default this is located in:
32-Bit - C:/Program Files/Steam/Steamapps/Common/ArmA 3/
64-Bit - C:/Program Files (x86)/Steam/Steamapps/Common/ArmA 3/
After extraction it should look like this:
Steam/Steamapps/Common/ArmA 3/@your_mod_folder_name

You can also use the "Arma 3 Alpha" folder in your "My Documents" folder. Your folder setup could than look like for example this:
mydocuments\Arma3 Alpha\@your_mod_folder_name\
mydocuments\Arma3 Alpha\@your_mod_folder_name\
mydocuments\Arma3 Alpha\@your_mod_folder_name\

Place the "userconfig" folder into your game install folder, usually:
"C:\Program Files (x86)\Steam\steamapps\common\Arma 3".

You'll also need to add a Launch Parameter to Steam, in order to do so right-click on ArmA 3 Alpha and click Properties and then Set Launch Options. In the window that opens enter in -mod=@your_mod_folder_name
For using multiple mods you would then do so like this:
-mod=@mod_name;@mod_name2;@mod_name3;@mod_name4;@mod_name5

Note:
You can also use -nosplash to get rid of the splash art and intro videos.


And of course you can also enable and disable community made addons and mods through the in-game Options Expansions menu if you do not want to mess with startup parameters!

When the above information still does not provide you with enough to learn how to install custom addons and mods you can always ask in our Guide On Installing Mods.


Included files:
ASM.pbo


Usage:
Run ArmaServerMonitor.exe from what directory you want, to monitor all your server (or HC) instances locally.
Additional, it is possible to connect to Arma Server Monitor from remote via TCP.
To watch your server from a remote device, you need an ASM instance on that device too and to configure it per start params as client.
Default start params for ArmaServerMonitor.exe are: -server -n1 -h127.0.0.1 -p24000
This means, ASM starts as monitoring server and listens at TCP port 24000, max. allowed remote clients = 1.

Example for client configuration: ArmaServerMonitor.exe -client -h201.178.1.102 -p24000

ASM starts as client and tries periodical to connect/read to/from your ASM server at 201.178.1.102:24000.
If your server is firewall protected, you have to open the selected TCP port on server.

You can activate the optional log feature, by adding -lfilenameprefix to your ASM start line.
By adding a -tinterval you can select the log interval in seconds (default 1). Values are ordered like this:
TimeStamp|FPS|CPS|PL#|AIL|AIR|OC0|OC1|OC2

To support monitors of different width, there is a -wxxx command line parameter, to set the width of the history graph in pixels/seconds.
This value should be set to a multiple of 60, or better of 300. Default is 900 pixels (-w900).

command line params:
s configure ASM as server (-s, default)
n allow n clients to connect (-n1, default)
c configure ASM as client (-c)
h hostaddress to bind or to connect to (-h127.0.0.1, default)
p port to listen or to connect to (-p24000, default)
l prefix for and activation of logfile (-lASMlog)
t interval for logging in seconds(-t1, default)
w width of historygraph in pixels/samples (-w900, default)
b enable bolder history graph lines, larger font for variables (-b)
Use RMB over value/progressbar area to configure user interface (popup menu).
Use RMB over the history graphs, to configure the visibility of individual graphs (popup menu).
Use LMB on history graph to adjust the offset in 24h ringbuffer, double click resets offset to zero.

If you prefer to run your DS instance(s) as service, you have to start ASM with admin rights

Additional hint:
to avoid @ASM listing in arma server browser, just install ASM.pbo in a3\addons folder.

More information about this project can be found on the official Github page:
- github.com/fred41


License:
Feel free to use the source code of ASMdll.dll, maybe as a start for your own projects.


Changelog:
29.08.2014
library and server application, by KillSwitch, now available for native linux °°
23.07.2014
changed library name for callextension commands, in fn_ASM.fsm, to lowercase (thx Killswitch, for hint)
24.05.2014
profile prefix based slot selection added
22.05.2014
removed old debug code from ASMdll.dll, DIR-value counting related fix
14.05.2014
for more then 4 instances (up to 16) a new commandline param, -o is introduced (for 4 blocks, of 4 arma server instances each)
28.04.2014
fix: monitoring NTI/NTO values, works now with A2, set enableAPImonitoring=2 in asm.ini (thanks Viba, for reporting and testing)
26.04.2014
fix: bug related to enableAPImonitoring, caused double slot usage with HC (thanks tankbuster, for report)
17.04.2014
enableAPImonitoring added to asm.ini to switch of API monitoring feature (NTI/NTO/DIR)
04.04.2014
- fix: AIR sometimes returned negative values (thanks dwarden for bug report)
22.03.2014
- added API values NTI, NTO & DIR, some fixes like: logging not stopped when mission ends


Forum topic:
- BI forums




Download from FTP #1:
Arma Server Monitor - Windows
Download from FTP #2:
Arma Server Monitor - Windows
Download from FTP #3:
Size : 1 MB   Downloaded : 1885 times     Report broken download link



Tags: No tags