/sensu-go/6.12/operations/maintain-sensu/ Recent content in Maintain Sensu on Sensu Docs Hugo -- gohugo.io en-us /sensu-go/6.12/operations/maintain-sensu/upgrade/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/upgrade/ To upgrade to the latest version of Sensu Go: Install or upgrade to the latest packages or Docker image. NOTE: If you’re upgrading a Sensu cluster, upgrade all of your Sensu backends before you run the sensu-backend upgrade command in step 5. For systems that use systemd, run: sudo systemctl daemon-reload Restart the Sensu agent: sudo systemctl restart sensu-agent Restart the Sensu backend: sudo systemctl restart sensu-backend Run a single upgrade command on one your Sensu backends to migrate the cluster: sensu-backend upgrade To skip confirmation and immediately run the upgrade command, add the --skip-confirm flag: sensu-backend upgrade --skip-confirm NOTE: If you are deploying a new Sensu cluster rather than upgrading from a previous version, you do not need to run the sensu-backend upgrade command. /sensu-go/6.12/operations/maintain-sensu/migrate/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/migrate/ This guide includes general information for migrating your Sensu instance from Sensu Core and Sensu Enterprise to Sensu Go. For instructions and tools to help you translate your Sensu configuration from Sensu Core and Enterprise to Sensu Go, review the Sensu Translator project. NOTE: The information in this guide applies to Sensu Enterprise as well as Sensu Core, although we refer to “Sensu Core” for brevity. The step for translating integrations, contact routing, and LDAP authentication applies to Sensu Enterprise (but not Sensu Core), and it is designated as Sensu Enterprise-only. /sensu-go/6.12/operations/maintain-sensu/tune/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/tune/ This page describes tuning options that may help restore proper operation if you experience performance issues with your Sensu installation. NOTE: Before you tune your Sensu installation, read Troubleshoot Sensu, Hardware requirements, and Deployment architecture for Sensu. These pages describe common problems and solutions, planning and optimization considerations, and other recommendations that may resolve your issue without tuning adjustments. Latency tolerances for etcd If you use embedded etcd for storage, you might notice high network or storage latency. /sensu-go/6.12/operations/maintain-sensu/troubleshoot/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/troubleshoot/ Service logging Logs produced by Sensu services (sensu-backend and sensu-agent) are often the best place to start when troubleshooting a variety of issues. Log file locations Linux Sensu services print structured log messages to standard output. To capture these log messages to disk or another logging facility, Sensu services use capabilities provided by the underlying operating system’s service management. For example, logs are sent to the journald when systemd is the service manager, whereas log messages are redirected to /var/log/sensu when running under sysv init schemes. /sensu-go/6.12/operations/maintain-sensu/disaster-recovery/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/disaster-recovery/ This page explains how to restore your Sensu configuration for disaster recovery. The disaster recovery processes include steps for creating backups of your Sensu configuration, but you must make backups before you need to use them. Read best practices for backups for more information. The instructions for restoring Sensu assume that your primary Sensu deployment is down and you need to bring up a new one to take its place. /sensu-go/6.12/operations/maintain-sensu/license/ Mon, 01 Jan 0001 00:00:00 +0000 /sensu-go/6.12/operations/maintain-sensu/license/ Activate your commercial license If you haven’t already, install the backend, agent, and sensuctl and configure sensuctl. Log in to your Sensu account at account.sensu.io and click Download license to download your license file. Save your license to a file such as sensu_license.yml or sensu_license.json. With the license file downloaded and saved to a file, you can activate your license with sensuctl or the /license API. NOTE: For clustered configurations, you only need to activate your license for one of the backends within the cluster.