Project

General

Profile

Bug #6344

Filter out output of some art services

Added by Gianluca Petrillo over 5 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Infrastructure
Target version:
Start date:
05/23/2014
Due date:
% Done:

100%

Estimated time:
0.25 h
Spent time:
Occurs In:
Scope:
Internal
Experiment:
-
SSI Package:
art
Duration:

Description

Hello,

I am struggling to figure out how to exclude the output of services like Timing and SimpleMemoryCheck from one of the destinations of the messages, by means of FHICL configuration.

I am using a configuration like this one:

message: {
  destinations: {
    SpecialOutput: { 
      type:        file
      filename:   "SpecialOutput.log" 
      append:      false
      threshold:   INFO
      categories: {
        SpecialOutputCategory: { limit: -1 }
        default: { limit: 0 }
      }
    }
    LogStandardOut: {
      type:       "cout" 
      threshold:  "INFO" 
      categories:{
        default:{ }
      }
    }
  }
} # message service

And I would expect only output from SpecialOutputCategory to filter in the first output file.
But I get the output from the aforementioned services too.
Could you direct me to the right configuration?


Related issues

Related to art - Support #7559: Memory check issues for Sirius AClosed11/29/201109/30/2013

Related to art - Feature #7751: Implement new sqlite-driven memory check service Closed01/30/2015

Related to art - Feature #3598: Obtaining more information from Timing serviceClosed03/13/201309/30/2013

History

#1 Updated by Christopher Green over 5 years ago

  • Tracker changed from Support to Bug
  • Project changed from messagefacility to art
  • Category set to Infrastructure
  • Status changed from New to Accepted
  • Target version set to 1.13.00
  • Scope set to Internal
  • Experiment - added
  • SSI Package art added

We will be addressing this issue as part of the cleanup of these services for version:1.10.02.

#2 Updated by Christopher Green over 4 years ago

  • Related to Support #7559: Memory check issues for Sirius A added

#3 Updated by Christopher Green over 4 years ago

  • Related to Feature #7751: Implement new sqlite-driven memory check service added

#4 Updated by Christopher Green over 4 years ago

  • Related to Feature #3598: Obtaining more information from Timing service added

#5 Updated by Christopher Green over 4 years ago

  • Status changed from Accepted to Feedback

Although this issue can be resolved with an appropriate FHiCL configuration, we would encourage you to look at the new MemoryTracker and TimeTracker services, which will output their data to an SQLite database for analysis directly, rather than going via the imperfect medium of text messages to the logger.

Does this sound like a reasonable way forward for you?

#6 Updated by Gianluca Petrillo over 4 years ago

The functionality of the new Tracker services seem way superior.
I will give them a try as soon as they are released.

#7 Updated by Kyle Knoepfel over 4 years ago

  • Status changed from Feedback to Resolved
  • % Done changed from 0 to 100
  • Estimated time set to 0.25 h

#8 Updated by Christopher Green over 4 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF