====== EOS Console > Current Use  ======

This page describes the EOS Console tab "Current Use". \\

{{orbit_desktop:entrance_icon_2.png?nolink&25 |}} [[211:server:console:index|EOS Console]] > Current Use 

{{  eos:console:current_use:currentuse_clientlogins.png?nolink900  }}
===== Client Logins =====

The Client Logins tab lists all current connected Orbit desktop applications (Obit Client or Orbit GIS). \\
Using the "Force Logout" button a connection and license use can be stopped immediately from server side. \\
This list is created on logging into the EOS Console, using the "Refresh" button you can reload this list.

===== Server Load =====

The Server Load tab gives exact insights about the real-time server memory consumption. \\
Unfold the memory tree and review the memory consumption of each loaded resource. This overview is very useful on troubleshooting server memory issues.

===== MM Publisher =====

Activate and configure advanced logging for MM Publisher. \\

All Publisher use of mobile mapping resources can be registered in a predefined logging database. \\ 
This logging option has been developed to monitor the use of the MM Publisher and to support your business opportunities. The use of mobile mapping data via Orbit desktop clients is not licensed and will not be registered. More about MM Publisher licenses : [[211:server:publishers:logging_mm|]].

Flag "Activate Logging" to enable MM Publisher logging. \\
Flag "Database Logging" to select a [[211:server:console:resources:database|database connection]] to be used for logging. The database tables used for logging will be created automatically if missing. \\
If "Database Logging" is disabled Orbit will dump all logging information in text files on server : orbit/server/program/services/ext_publisher/logs

==== Logging Tables ====

If "Activate Logging" is enabled Orbit will create and update the tables "log_mm_publisher_license_exceeded" and "log_mm_publisher_current_use" once needed. The flags "Concurrent Users", "Throughput Volume" and "Publication Access" are optional and will create the tables as described below. 

**Activate Logging** \\
(1) Logs every request if your Orbit license is exceeded, when and why. \\
log_mm_publisher_license_exceeded : id, date_day, date_time, ip_address, seat_id, user, publication, project, run, image, restriction_type, restriction_value, count

(2) Logs every 15 minutes : \\
- the current state of concurrent users and server memory use (kilobytes), \\
- the summary of last 15 minutes for image throughput volume and data throughput (kilobytes). \\
log_mm_publisher_current_use : id, date_day, date_time, uptime, concurrent_users, memory_server, memory_panorama_projects, memory_panorama_service, throughput_volume, throughput_http_in, throughput_http_out

**Concurrent Users ** \\
(3) Logs every new concurrent user. \\
log_mm_publisher_user_logins : id, date_day, date_time, ip_address, seat_id, user, current_concurrent_users

**Throughput Volume** \\
(4) Logs every image request. \\
log_mm_publisher_image_requests : id, date_day, date_time, ip_address, seat_id, user, publication, project, run, image, current_throughput_volume

**Publication Access** \\
(5) Logs every publication login. \\
log_mm_publisher_publication_access : id, date_day, date_time, ip_address, seat_id, user, publication

The table values are clarified by the column names, just for a few columns some more information :
  * seat_id : a hardware identifier of the client computer
  * user, publication, project, run, image : Orbit user and mobile mapping definitions
  * restriction_type : "throughput_volume", "concurrent_use"
  * restriction_value : the maximum throughput volume or concurrent use as defined by your license
  * count : the actual requested throughput volume or concurrent use
  * uptime : uptime (seconds) of Orbit service