The System Monitor displays runtime status and system information when the Designer is connected to a running solution, whether local or remote.

Access: Runtime → System Monitor

Parent Page: Runtime Designer UI (Reference)


Monitor Access Methods

Designer Access

Navigate to Runtime → System Monitor when connected to runtime.

Browser Access

No installation required:

http://ServerIP:Port/html5/?Monitor=Runtime

Example:

Port defaults: 3101 (Production), 3201 (Development)

System Information Properties

Profile and Licensing

PropertyDescriptionExample
Info.ProfileNameCurrent execution profileProduction
Info.EvaluationModeRunning in evaluationTrue/False
Info.EvaluationTimeRemainingTime left in evaluation02:45:30
Info.License.SerialNumberLicense serialABC-123-456
Info.License.LicensedProductProduct/Family/ModelFrameworX-5000

Product Information

PropertyDescription
Info.Product.CompanyProduct company name
Info.Product.NameProduct name
Info.Product.VersionProduct version in use

Solution Details

PropertyDescription
Info.Solution.CurrentBuildBuild number
Info.Solution.DateModifiedLast modification
Info.Solution.ProductVersionProduct used for editing
Info.Solution.RequiredLicenseProduction license needed
Info.Solution.TargetFrameworkPlatform requirement
Info.Solution.VersionIDConfiguration version

Server Information

PropertyDescription
Server.ComputerNameServer hostname
Server.DateStringCurrent server time
Server.OSVersionOperating system
Server.TStartupStartedTimeSolution start time
Server.SystemMonitor.UptimeRunning duration

Runtime Status

PropertyDescription
Server.IsRunningAsServiceWindows service mode
Server.IsRunningOnDockerDocker container mode
Server.NumberOfTagsLoadedTags in memory

License Verification

Critical checks for production:

CheckRequirementWhere to Verify
Evaluation ModeMust be FalseInfo.EvaluationMode
License MatchSolution ≤ LicenseRequiredLicense vs LicensedProduct
ProfileMust be ProductionInfo.ProfileName

License Warning Signs

  • EvaluationMode = True
  • EvaluationTimeRemaining shown
  • License mismatch warnings
  • Wrong execution profile

Using Monitor Data

Health Checks

Monitor these indicators:

  • Uptime for stability
  • Tag count for memory usage
  • License status for compliance
  • Profile for environment

Troubleshooting

SymptomCheckAction
Solution stopsEvaluationTimeRemainingApply license
Wrong dataProfileNameSwitch profile
Performance issuesNumberOfTagsLoadedOptimize tags
Connection problemsComputerNameVerify server

Remote Monitoring

Setup Requirements

  1. Solution running on server
  2. Port accessible through firewall
  3. Network connectivity
  4. Browser on monitoring station

URL Construction

http://[ServerAddress]:[Port]/html5/?Monitor=Runtime

Components:

  • ServerAddress: IP or hostname
  • Port: Runtime port (profile-specific)
  • Path: Always /html5/?Monitor=Runtime

Integration Points

The System Monitor data comes from runtime objects:

  • Server object properties
  • Info object properties
  • Real-time values
  • Automatic updates

Best Practices

Regular Monitoring

  • Check uptime daily
  • Verify license status
  • Monitor tag count growth
  • Track version changes

Production Deployment

  • Confirm Production profile
  • Verify license compliance
  • Document system specs
  • Monitor initial hours

Remote Access

  • Secure monitor URLs
  • Limit access permissions
  • Use HTTPS when possible
  • Monitor access logs

See Also





In this section: