This, for example, would change the interval to 15 seconds. If you want to change them, the command would be: fmsadmin set serverconfig statsinterval=15 The default settings of logging every 30 seconds and keeping the log size at 40MB is usually sufficient. Next, I will verify what the logging interval is and how big the log size setting is: fmsadmin get serverconfig: That client stats log as well as the top call stats log will turn themselves off on every FileMaker Server restart, but the regular stats.log will remain on after issuing this command. While you are there you can also enable the Client Stats log: fmsadmin enable clientstats Figure 5 – Verifying the logging interval and log size setting In FileMaker Server 17, you can only do so from the command line on the server itself – or through a secure tunnel to the command line on the server (see Figure 4): Figure 4 – Turn on the stats.log in FileMaker Server 17 (click image to enlarge)
#Filemaker pro 17 download install
The very first thing I do when I install a new FileMaker Server or log into one already running is turn on the stats.log. (I really wish it wasn’t.) Because we do not get visual reminders of of this in the new Admin Console, you may easily forget about it. However, it is also still turned off by default.
#Filemaker pro 17 download download
To view any of the logs, you must download them (see Figure 3): Figure 3 – Download log files in FileMaker Server 17 Admin Console (click image to enlarge) Finding the stats.log in FileMaker 17Īs per my previous blog post on missing features in FileMaker 17 illustrates, you may think the stats.log is no longer available in FileMaker Server 17. In the FileMaker Server 17 Admin Console, you can only toggle the top call stats log.
That is not so anymore in the new FileMaker Server 17 Admin Console. The statistics themselves were visible in the Console too as shown in Figure 2: Figure 2 – Statistics shown in FileMaker Server 16 Admin Console (click image to enlarge) In FileMaker Server 16, the toggle to enable this log was in the Admin Console as shown below: Figure 1 – Toggle for stats.log in FileMaker Server 16 Admin Console (click image to enlarge) Without this log, you are, in effect, flying blind. It will inform you if it is safe to use more PSoS or more server-side schedules or add a few WebDirect users. The stats.log also will help you plan and extrapolate whether the current server can handle any new load you have in mind. The information in that log will help you troubleshoot performance bottlenecks in your solution. Does the network card give me enough bandwidth?.It delivers invaluable information on how your deployment is behaving across the four traditional bottlenecks of any server: There is no log file more important on your FileMaker Server then the ‘stats.log’.
0 kommentar(er)
