1. UNICOS LHCLoggingDB Josef Hofer EN/ICE/SCD

2. Agenda The LHC Logging Database Purpose of the LHCLogging component Basic concepts Advanced concepts Logging configuration Logging detail information System integrity Current status / Next steps

3. The LHC Logging Database What is the LHC Logging Database? (LDB) Long term data storage and biggest DB at CERN How much data does it contain? ~ 1 million signals from different sources ~ 1 TB of new data per week > 20 years of filtered data How is the database used? > 700 clients (onsite and offsite) > 100 custom applications analysing data Generic visualisation tools: e.g. “TIMBER” Data insertion and extraction via PL/SQL Java APIs

4. The LHC Logging System

5. Purpose of the LHCLogging component Ensure that data is being transferred from PVSS to LDB Provide an easy way of configuration to specify which data shall be transferred to LDB Display detail information for monitoring to see which data is currently being transferred Trigger alarms if data transfer to LDB does not work

6. Basic concepts LHCLogging “old” LHC Logging DB Local Archive ValArch PVSS System C++ Application unLHCLogging manager HTTP XML Java API Data flow

7. Basic concepts LHCLogging “old” unLHCLogging manager HTTP XML UI-Panels: Configuration & diagnostics Configuration & Diagnostics Data flow LHC Logging DB Local Archive ValArch PVSS System C++ Application Java API

8. Why do we have to reinvent the wheel ? Maintenance of “old” logging requires a lot of effort Performance was not sufficient for QPS Gain robustness by eliminating number of failure points

9. Basic concepts LHCLoggingDB Data flow LHC Logging DB Oracle RDB Archive or MDB PVSS System DB Link LDB data transfer mgr. No Java application server! No custom PVSS manager! Employ existing and maintained mechanism used by measurement DB

10. Basic concepts LHCLoggingDB LHC Logging DB Oracle RDB Archive or MDB PVSS System DB Link LDB data transfer mgr. UI-Panels: Configuration & diagnostics PL/SQL API Employ existing and maintained mechanism used by measurement DB No Java application server! No custom PVSS manager! Configuration & Diagnostics Data flow

11. Advanced concepts LHCLoggingDB PVSS Systems UI-Panels: Configuration & diagnostics Oracle RDB Archive or MDB LDB data transfer mgr. DB schema 3 DB schema 2 DB schema 1 Configuration & Diagnostics Data flow

12. Advanced concepts LHCLoggingDB LHC Logging DB Oracle RDB Archive or MDB DB Link RDB jobs LDB data transfer mgr. Data transfer is performed by “transfer jobs” Up to 16 transfer jobs per database Each job manages multiple elements Jobs run every 5 minutes: Query value changes on RDB Archive Push archived values to Logging DB Caution: Max. chunk size per element! Configuration & Diagnostics Data flow

13. Advanced concepts LHCLoggingDB TSValue 2014/05/19 02:34:150.074 2014/05/19 02:33:590.068 2014/05/19 02:33:170.072 2014/05/19 02:32:120.069 2014/05/19 02:28:160.065 TS job runTS last loggedRecs 2014/05/19 02:35:00 2014/05/19 02:30:002014/05/19 02:28:164 2014/05/19 02:25:002014/05/19 02:24:224 2014/05/19 02:20:002014/05/19 02:17:123 2014/05/19 02:15:002014/05/19 02:14:015 MDB: LVS: *LVS: Log Variable Status

14. Advanced concepts LHCLoggingDB function: TransferJob(): do every 5 minutes for all elements e assigned to job j TS_Latest = getLatestTsFromLvs(e); data = queryDataFromMDB(e, TS_Latest, TS_Now); TS_Latest = pushDataToLDB(data); setLatestTsToLvs(e, TS_Latest); end function; function: TS pushDataToLDB(data): if data.len() > 3000 then transfer(data,0,2999); TS = data[2999].getTS(); else transfer(data,0,data.len()-1); TS = data[data.len()-1].getTS(); end if return(TS); end function;

15. Advanced concepts LHCLoggingDB NAMEDESCRIPTION SCADARProduction systems EN/ICE QPSRProduction systems QPS only TESTTest systems for development Currently available RDB Archives

16. Logging configuration Possible types of configuration Register new elements for logging Update already registered elements Unregister elements from logging Change settings of transfer manager Create/Import/Export configuration files

17. Register new elements for logging Use standard logging configuration file in.text or.xml format [_ValueArchive_0] dpe=dpname10.actVal alias= name=HeatingCircuit10:FlowTemperature description=Flow temp. heating circuit 10 hierarchy= format= dpe=dpname11.actVal alias= name=HeatingCircuit11:FlowTemperature description=Flow temp. heating circuit 11 hierarchy= format=

18. Register new elements for logging Select config file and click “Check” to verify 1

19. Register new elements for logging Enter additional information

20. Register new elements for logging Click on “Append” to register data

21. Logging detail information List of all registered elements

22. Logging detail information Transfer history of selected element

23. Logging detail information Transfer job details of selected job

24. Logging detail information Element history of selected element

25. System Integrity RDB Change RDB system integrity plugin to Avoid rash killing of the archive manager Employ a simple way of checking Provide additional functions which will be used by system integrity of LHCLoggingDB

26. System Integrity RDB Perform system integrity checks in a polling loop Kill manager only if it is blocking longer than a specific time Monitor state of database connection and buffer usage Do a round trip check for several test data points Set alarm data point according to the output of each check

27. System Integrity LHCLoggingDB Create new plugin to be able to: Ensure that all transfer jobs are running Check if all registered elements are being processed by the responsible transfer job Check if transfer jobs are able to handle the amount of data that is produced by each signal (max. chunk size should never be reached) Do a round trip check for specific test data points (only one per data category to not kill the DB)

28. System Integrity LHCLoggingDB Perform system integrity checks in a polling loop Take RDB system integrity status into account Check transfer history by searching for recent timestamps Do a round trip check for several test data points Set alarm data point according to the output of each check

29. Current status / Next steps Completed tasks Display detail information for monitoring Verification and Import of configuration files (.text and.xml) Current tasks Develop system integrity plugin to automatically check logging and trigger alarms on error Next tasks Implement possibility to update or delete already registered elements (cooperation with BE/CO) Implement creation & export of config-files Improve usability