Logging#
Hyperion logs to a number of different locations. The sections below describe the locations that are configured via environment variables for a standard server install.
Graylog#
Graylog is the recommended way to view logs. It is used for more centralised logging which is also more easily searched and archived. Log messages are sent to the Hyperion graylog stream.
To find different severity of message you can search for level: X. Where X is:
3: Errors messages - usually causing Hyperion to have stopped. Note that no diffraction is currently logged as an error but this doesn’t stop Hyperion, only skip the sample. This will be improved by DiamondLightSource/mx-bluesky#427.4: Warnings - usually not a major problem6: Info - Just telling you what Hyperion is doing
Startup Log#
When hyperion_restart() is called by GDA, it will log the initial console output to a log file. This log file
location is
controlled by the gda.logs.dir property and is typically /dls_sw/<beamline>/logs/bluesky.
Log files#
By default, Hyperion logs to the filesystem.
The log file location is controlled by the LOG_DIR environment value. Typically this can be found in
/dls_sw/<beamline>/logs/bluesky
Debug Log#
The standard logs files do not record all messages, only those at INFO level or higher, in order to keep storage
requirements to a minimum.
In the event of an error occurring, then trace-level logging for the most recent events (by default 5000) is flushed
to a separate set of log files. Due to the size of these files, they are stored separately from the main log files
. These logs are located in /dls/tmp/<beamline>/logs/bluesky by default, or
otherwise as specified by the DEBUG_LOG_DIR environment variable.