LogCentral man page

LogCentral — Central logging service for distributed applications


LogCentral - service using the publisher/subscriber model, where components publish tagged messages and tools get back appropriate messages .


LogCentral [options] ...


LogCentral gathers and publishes the messages to the subscribers. Messages are tagged, the LogCentral service only sends suscribers filtered messages.

Before starting the LogCentral, you must:

  • launch a CORBA Naming Service.
  • launch log forwarders if needed
  • launch LogCentral service

[Remark: LogCentral must be launched before the log tools/components]


-config [name]

The configuration file for the LogCentral service. First, LogCentral will use the file provided by command-line, then read environment variable $LOGCENTRAL_CONFIG and in last resort, it will look for a file named "config.cfg" in current directory.

Configuration File

You can pass a configuration file to LogCentral using command line options through the -config option. Configuration file lists several classes of tags describing the messages. A minimal configuration will look like this:


[DynamicTagList] [StaticTagList] [UniqueTagList] [VolatileTagList]

The general tag accept the following parameters: * 'port=xxx', specifies the port to use

  • 'MinAge=xxx', defines the minimum period of time that messages will be stored in the LogCentral
  • 'DynamicStartSuffix=START', expands tags with START. See DynamicTagList.
  • 'DynamicStopSuffix=STOP', expands tags with STOP. See DynamicTagList.

The other four categories configure the state manager of the LogCentral. It is important to know that all tags will be expanded with two suffixes to generate pairs of tags.

  • VolatileTagList, should contain all the monitored tags. Not essential but it may be requested by some tool.
  • UniqueTagList, should contain tags that will overwrite the previous messages of this tag


  • Launching the LogCentral
LogCentral -config ./LogCentral.cfg


The LogCentral uses CORBA as its communication layer. While it's a flexible and robust middleware, its deployement on heterogeneous networks still is delicate and may require using ssh tunnels.


GRAAL INRIA Rhone-Alpes 46 allee d'Italie 69364 Lyon cedex 07, FRANCE Email: <diet-dev@ens-lyon.fr> WWW: http://graal.ens-lyon.fr/DIET

See Also

omniNames(1), logForwarder(1)



haikel.guemar@sysfera.com, kevin.coulomb@sysfera.com

License: GPLv3

Referenced By

DIETtestTool(1), logForwarder(1), testComponent(1).

2011-05-11 0.1