Documentation (logging) — Tailscale

Cited by

Facts read from this source

• Log streaming destination Report an error

  “Each Tailscale agent in your distributed network streams its logs to a central log server (at log.tailscale.com).”

• Tamper detection Report an error

  “Because every connection requires two endpoints, and both endpoints log every connection, it's possible to detect lost or tampered logs by comparing the double entries of each endpoint.”

• Windows log location Report an error

  “Logs are stored in C:\ProgramData\Tailscale (or, more generally $env:ALLUSERSPROFILE\Tailscale).”

• Network flow logs admin console Report an error

  “Network flow logs are available from the admin console when enabled.”

• Client logging opt out Report an error

  “You opt out of client logging on each device individually, using the --no-logs-no-support flag for the tailscaled daemon or the equivalent TS_NO_LOGS_NO_SUPPORT environment variable. This disables telemetry and opts the device out of any support that would require that telemetry for debugging.”

• Windows opt out env var only Report an error

  “On Windows, only the environment variable is available.”

• Macos opt out flag limitation Report an error

  “On macOS, the flag works only with the command-line open source tailscaled variant, not the Standalone app or the Mac App Store app.”

• Network flow logs plan availability Report an error

  “Network flow logs are available for the Premium and Enterprise plans.”

• Flow logs siem streaming Report an error

  “Flow logs can be configured to stream to a security information and event management (SIEM) system.”

• Flow logs content scope Report an error

  “These logs strictly do not contain any information about client operations or contents of network traffic.”

• Configuration audit logs Report an error

  “Configuration audit logs record actions that modify a tailnet's configuration, including the type of action, the actor, the target resource, and the time.”

• Audit logs default and retention Report an error

  “Configuration audit logs are enabled by default for all tailnets, and are available for the most recent 90 days.”

• Audit logs siem streaming Report an error

  “Audit logs can be configured to stream to a security information and event management (SIEM) system.”

• Audit log access Report an error

  “All users who have access to the admin console can inspect configuration audit logs in the Logs page of the admin console, and can filter these logs to find specific events.”

• Local ssh session logs Report an error

  “Local SSH session logs are not supported as of version 1.48.0.”

• Ssh session recording Report an error

  “You can use Tailscale SSH session recording to streaming recordings from the server device.”

• Kubernetes operator logs Report an error

  “The Kubernetes Operator's reconciliation logs are centrally collected for debugging.”

• Kubernetes operator log access Report an error

  “You can access logs locally using the kubectl logs command.”

• Kubernetes operator opt out Report an error

  “If you deployed the Kubernetes Operator with Helm, add the TS_NO_LOGS_NO_SUPPORT environment variable to the operatorConfig.extraEnv section:”

Scores citing this record

• The DevOps Engineer Logs, audit trail & incident response
• The DevOps Engineer Pricing transparency
• The IT Lead Logs, audit trail & incident response
• The MSP Technician Logs, audit trail & incident response
• The Operations Manager Logs, audit trail & incident response
• The Information Security Officer Logs, audit trail & incident response
• The Information Security Officer Pricing transparency
• The Skeptic Logs, audit trail & incident response