Web.Based.Monitoring Status

William BadgettCMS Web Based

Monitoring2006.08.10

1

Web.Based.MonitoringStatus

William Badgett, Steve MurrayFermilab

Zongru WanKansas State University

LHC@FNAL Meeting



2

WebBasedMonitor, goals

• Integrate information from across all CMS• Environmental, Trigger, DAQ, Luminosity, etc.

• Extend “CMS Page 1” to provide more information to the CMS collaboration

• Ability to “drill down” to get more details• Links to sub-detector pages already in

development

• Tools for remote ShiftCrew• Also useful for remote experts

• Plotting “Value versus Time” in CMS database

• Ability to plot anything vs. anything• Light-weight web interface



3

Structure, directed servlets

• Additional “Expert Tier”– Underlying infrastructure for more general

pages – General database browser

• For people who know a little SQL and would like to create new web pages – need to know where data are

– Basic low level servlets• Tools for creating new pages, use Java inheritance to

make it easy

– Not intended for ShiftCrew direct use– DatabaseBrowser, SlowControlBrowser,

RootBrowser• β versions already in place



4

WebBasedMonitor, front-page

http://cmsdaq.cern.ch/cmsmon/



5

DatabaseBrowser, example



6

DatabaseBrowser, example

Automatic conversion from database table data to root

TTree



7

DatabaseBrowser, root conversion



8

GenericBrowsing

• Disparate set of database tables– Barely controlled chaos

• No standard history model– Sub-detector specific tables– Need meta-data tables to describe them

• Have settled on schema• Implementing user interfaces

– General case of “Value versus Time” servlets can be extended to many data source

• DAQ, Trigger, Lumi, Conditions, etc.



9

SlowControlBrowser

Since cmsomds erased, no data in standard PVSS tables



10

RunSummary pages

• Top level point to inquire about runs • Form with popular selection criteria

– By run or run range √– Date and time range √– Trigger√ and run configuration

• LTC MTCC triggers only– Events collected √– Luminosity accumulated– Subdetector status √

• Presence in readout

√ Implementedhttp://cmsdaq.cern.ch/cmsmon/

click on “RunSummary”



11

RunSummary query page

Easy click for last 24

hours

Subdetectors

Triggers

LHC info to be implemented



12

RunSummary, multi-run query

Multi-run query results

Can also run in test-only mode with wget command

line



13

RunSummary, single run

• Clickable measurements– Drill-down capability

• Plot creation– Provides root TTree and

histogram object in file– Resizeable on resubmit



14

LHC Logging

• Equivalent to AcNet logging• Contains many interesting CMS data• E.g. magnet temperature, current• Accessible from protected P5 network and our web

browser• More abstract database schema (easier to browse)• Fold into current CMS browser



15

Conclusion

• Propose implementing standard meta-data tables to describe wealth of data in CMS database– Based on ECAL and WBM proposals– Have schema in hand; testing– Implementation in progress

• RunSummary actively being used– & extended

• Will hook into LHC logger– Can LHC@FNAL benefit?

• Have a look!

http://cmsdaq.cern.ch/cmsmon/

Documents

Web.Based.Monitoring Status