Difference between revisions of "Data Logger"

From MidasWiki
Jump to navigation Jump to search
 
(7 intermediate revisions by 2 users not shown)
Line 1: Line 1:
The Midas data logger serves multiple purpose of logging.
+
{{Pagelinks}}
# Its main task is to log experimental data to storage device[[Event_Filtering|(s)]] such as disk, tape, FTP with prior data compression.
+
<div style="column-count:4;-moz-column-count:4;-webkit-column-count:4">
# Serves the logging of the overall Midas system messages
+
* [[/Logger ODB tree]]
# Collect and log the history events
+
* [[mlogger]]
# Can log special information to an external mySQL database
+
* [[/Lazy ODB tree]]
 +
* [[Lazylogger]]
 +
</div>
  
The associated utility handling this Data logging is the [[mlogger]]. It runs on the backend computer, receiving events from the buffer manager. It supports three type of storage devices so far, i.e.
 
# Disk,
 
# Tape
 
# FTP channel to a remote computer.
 
  
Data can currently be written in five different formats :
 
* MIDAS binary,
 
* ASCII,
 
* ROOT
 
* DUMP
 
  
A built in compression (gzip) can be enabled
+
The Midas [[mlogger|data logger]] serves multiple purposes related to data logging.
 +
# On the fly data compression (if required)
 +
# Log experimental data to storage device'''[[Event_Filtering|(s)]]'''
 +
# Handles the overall Midas '''[[Message_System|System messages]]''' logging
 +
# Collect and log the '''[[History System|history events]]'''
 +
# Can log special information to an external '''[[Logging to a mySQL database|mySQL]]''' database
 +
 
 +
The data logger configuration is available in the ODB. Please refer to '''[[/Logger ODB tree]]''' for full feature descriptions.
 +
 
 +
The actual application handling this Data logging is the '''[[mlogger]]'''. It is intended to run on the backend computer (on the same node where the event buffers reside) for fast data access (no network involved).
 +
 
 +
 
 +
'''Note:''' There is a '''[[Lazylogger|Data Archiver]]''' application which provide a copy or move of the logger data. The destination being usually a remote location holding a large data storage, tape robot, etc... The reason for such secondary logger is to off-load the local disk or decouple the '''[[mlogger|Data Logger]]''' application from possibly slow storage device.
 +
 
 +
[[Category:Data Logging]]

Latest revision as of 17:49, 14 July 2015



The Midas data logger serves multiple purposes related to data logging.

  1. On the fly data compression (if required)
  2. Log experimental data to storage device(s)
  3. Handles the overall Midas System messages logging
  4. Collect and log the history events
  5. Can log special information to an external mySQL database

The data logger configuration is available in the ODB. Please refer to /Logger ODB tree for full feature descriptions.

The actual application handling this Data logging is the mlogger. It is intended to run on the backend computer (on the same node where the event buffers reside) for fast data access (no network involved).


Note: There is a Data Archiver application which provide a copy or move of the logger data. The destination being usually a remote location holding a large data storage, tape robot, etc... The reason for such secondary logger is to off-load the local disk or decouple the Data Logger application from possibly slow storage device.