Logging¶
The logs from the services are captured by systemd/journald and they can most easily be
accessed using the hubctl log command, but can also be retrieved by administrators in the
usual way using standard journalctl commands or ingested into monitoring systems using
standard connectors.
The hubctl log command has support for filtering the output by time, number of lines and by specific services.
hubctl log [service...] [flags]
Below are the list of flags that can be specified to limit the log messages that are returned. The dates can be specified in systemd-time format, as with journalctl.
| Option | Short | Description |
|---|---|---|
-n INTEGER |
--lines INTEGER |
Number of log messages to show |
-S DATE |
--since DATE |
Show log messages not older than the specified date |
-U DATE |
--until DATE |
Show log messages not newer than the specified date |
-r |
--reverse |
Show latest log messages first |
For example, to see the last 50 log records from the authentication service, use the command
hubctl log auth -n 50
To see the full list of Altair SLC Hub services, use the command:
hubctl service status
In Windows, the log files are written to disk in the [var directory] directory by the service wrapper. The service wrapper may be configured to adjust the log rotation.
These can be viewed directly by the administrator.