You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
our main services each have their current SMF log file: nexus, DNS, etc.
every zone has SMF log files for various services
CockroachDB has its own set of log files somewhere else
Live logs are in the corresponding zones and you can find most of them with svcs -L (but not the CockroachDB ones). For each of these we also have the archived logs. But because these are in zones that themselves have unique names, even on a single-system deployment, it can be hard to find, say, "the current log file for Nexus" or especially "all the Nexus log files for timestamp T".
Here's an idea: say we ship a GZ tool called oxlog:
# prints the names of the latest Nexus log files from all Nexus zones
oxlog --latest nexus
# prints the names of the archived Nexus log files from all Nexus zones
oxlog --archived nexus
# prints the names all Nexus logs (current and archived) from all Nexus zones
oxlog --latest --archived nexus
# prints the names of all Nexus log files for a specific zone
oxlog --latest --archived --zone ZONE_ID nexus
I'm thinking we'd use this similar to how we use svcs -L, like:
# Search all Nexus log files for a particular request id
grep SOME_REQ_ID $(oxlog --latest --archived nexus)
# Watch activity for all Nexus instances on the system
tail -f $(oxlog --latest nexus)
Maybe it could take timestamp filters too? That's trickier to implement though.
The text was updated successfully, but these errors were encountered:
Finding the log was a bit of a challenge, required running find /pool/ext -name 'oxide-sled-agent:default.log*' | xargs ls -al | less and looking for a file mtime of Nov 30 in the output (note times are in UTC, so if were doing this later in the day it could have been Dec 1).
We have lots of log files:
Live logs are in the corresponding zones and you can find most of them with
svcs -L
(but not the CockroachDB ones). For each of these we also have the archived logs. But because these are in zones that themselves have unique names, even on a single-system deployment, it can be hard to find, say, "the current log file for Nexus" or especially "all the Nexus log files for timestamp T".Here's an idea: say we ship a GZ tool called
oxlog
:I'm thinking we'd use this similar to how we use
svcs -L
, like:Maybe it could take timestamp filters too? That's trickier to implement though.
The text was updated successfully, but these errors were encountered: