A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://cloud.google.com/stackdriver/docs/solutions/agents/ops-agent/installation below:

Installing the Ops Agent on individual VMs

Key Point: Now you can install all of the Google Cloud Observability agents across your entire fleet of Compute Engine Linux VMs in a single step. With one command, you can create a policy that governs new and existing VMs, ensuring proper installation and optional auto-upgrade of the agents. For more information, refer to the Managing Agent Policies guide.

The Ops Agent collects logs and metrics on Compute Engine instances, sending your logs to Cloud Logging and your metrics to Cloud Monitoring.

Before you begin

To install the agent, ensure that you have the following:

Install the agent automatically during VM creation

For more information, see Install the Ops Agent during VM creation.

Install the agent from the command line Note: First verify that all conditions are met in the Before you begin section.

To install the agent using the command line, use the following instructions.

Install the latest version of the agent

To install the latest version of the agent, complete the following steps.

Linux

  1. Open a terminal connection to your VM instance using SSH or a similar tool and ensure you have sudo access.

  2. Change to a directory you have write access to, for example your home directory.

  3. Download and run the agent-installation script by using the following commands:

    curl -sSO https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.sh
sudo bash add-google-cloud-ops-agent-repo.sh --also-install

    After it is installed, the agent is started automatically.

Windows

  1. Connect to your instance using RDP or a similar tool and login to Windows.

  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selecting Run as Administrator.

  3. Run the following PowerShell commands:

    (New-Object Net.WebClient).DownloadFile("https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.ps1", "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1")
Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall"
Installing a specific version of the agent

To install a specific version of the agent, complete the following steps.

Linux

  1. Open a terminal connection to your VM instance using SSH or a similar tool and ensure you have sudo access.

  2. Change to a directory you have write access to, for example your home directory.

  3. Download the agent installation script:

    curl -sSO https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.sh

    When running the add-google-cloud-ops-agent-repo.sh script, you can also set the following flags:

    See the script comments for more information and example usage.

  4. Add the agent's package repository and install the agent:

    1. To list the available agent versions, see List all agent versions.

    2. For production environments, you might want to pin to a major version to avoid installing major versions that might include backward incompatible changes. To pin to a major version, run:

      sudo bash add-google-cloud-ops-agent-repo.sh --also-install \
  --version=MAJOR_VERSION.*.*

      For example, to pin to the 1.x.x of the agent, run:

      sudo bash add-google-cloud-ops-agent-repo.sh --also-install \
  --version=1.*.*

    3. To install a specific version of the agent, run:

      sudo bash add-google-cloud-ops-agent-repo.sh --also-install \
  --version=MAJOR_VERSION.MINOR_VERSION.PATCH_VERSION

You can delete the installation script after it runs successfully.

If you have trouble with the installation, refer to the Troubleshooting page.

Windows

  1. Connect to your instance using RDP or a similar tool and login to Windows.

  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selecting Run as Administrator.

  3. Download the agent installation script:

    (New-Object Net.WebClient).DownloadFile("https://dl.google.com/cloudagents/add-google-cloud-ops-agent-repo.ps1", "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1")

    When running the add-google-cloud-ops-agent-repo.ps1 script, you can also set the following flags:

    See the script comments for more information and example usage.

  4. Add the agent's package repository and install the agent:

    1. To list the available agent versions, see List all agent versions.

    2. For production environments, you might want to pin to a major version to avoid installing major versions that might include backward incompatible changes. To pin to a major version, run:

      Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall -Version MAJOR_VERSION.*.*"

      For example, to pin to the 1.x.x of the agent, run:

      Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall -Version 1.*.*"

    3. To install a specific version of the agent, run:

      Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall -Version version-number"

      For example:

      Invoke-Expression "${env:UserProfile}\add-google-cloud-ops-agent-repo.ps1 -AlsoInstall -Version 1.0.1"

You can delete the installation script after it runs successfully.

If you have trouble with the installation, refer to the Troubleshooting page.

Install the agent by using the Google Cloud console Note: First verify that all conditions are met in the Before you begin section.

You can install the Ops Agent on one or more Compute Engine VMs by using the Google Cloud console from the Cloud Monitoring or Compute Engine pages.

Cloud Monitoring

In the Google Cloud console, go to the VM Instances dashboard page:

Go to VM Instances dashboard

If you use the search bar to find this page, then select the result whose subheading is Monitoring.

The List view on the Inventory tab on the dashboard lists all VMs and includes a status column for your agent, as shown in the following screenshot:

The Agent column reports the following values:

You can install the Ops Agent by doing the following:

You can also install or update the Ops Agent from the VM Details page for a specific VM.

When possible, the agent is installed by using an Ops Agent OS policy. For more information, see Manage VMs covered by the Ops Agent OS policy. Ops Agent OS policies aren't supported on all versions of all operating systems. In this case, clicking Install/Update Ops Agent provides a series of commands to run in Cloud Shell.

The Ops Agent collects both metrics and logs by default. You can change this default behavior by configuring the Ops Agent.

Compute Engine

  1. In the Google Cloud console, go to the VM instances page:

    Go to VM instances

    If you use the search bar to find this page, then select the result whose subheading is Compute Engine.

  2. Click the name of the VM on which you want to install the agent.

  3. Click the Observability tab.

  4. Click Install Ops Agent.

    When possible, the agent is installed by using an Ops Agent OS policy. For more information, see Manage VMs covered by the Ops Agent OS policy. Ops Agent OS policies aren't supported on all versions of all operating systems. In this case, clicking Install/Update Ops Agent provides a series of commands to run in Cloud Shell.

    The Ops Agent collects both metrics and logs by default. You can change this default behavior by configuring the Ops Agent.

    If the agent installation remains Pending for more than 10 minutes, then there might be a problem in applying the Ops Agent OS policy or starting the agent. For troubleshooting information, see Agent diagnostics tool for automatic installation policies.

Verify that the Ops Agent is running

To verify that the Ops Agent is running, you can use either of the following:

Use VM Instances dashboard

In the Google Cloud console, go to the VM Instances dashboard page:

Go to VM Instances dashboard

If you use the search bar to find this page, then select the result whose subheading is Monitoring.

The List view on the Inventory tab on the dashboard lists all VMs and includes a status column for your agent.

The Agent column reports the following values:

Use gcpdiag

For information about using gcpdiag, see Verify agent status by using gcpdiag.

Optional tasks

This section describes how to perform common maintenance tasks.

Configure an HTTP proxy

If you use an HTTP proxy for proxying requests to the Logging and Monitoring APIs, do the following:

Linux

  1. Edit the following configuration file (create the file if it doesn't already exist):

     /etc/systemd/system.conf

  2. Add the following to the file:

     DefaultEnvironment="HTTP_PROXY=http://proxy-ip:proxy-port" "HTTPS_PROXY=http://proxy-ip:proxy-port" "NO_PROXY=http://metadata.google.internal"  # Skip proxy for the local Metadata Server.

  3. Reload the environment variables:

     sudo systemctl daemon-reload

  4. Restart the agent by running the following command on your VM instance:

     sudo systemctl restart google-cloud-ops-agent"*"
Windows

  1. If you use an HTTP proxy, run the following command from an administrator command prompt. This sets the HTTP_PROXY and HTTPS_PROXY environment variables so that the agent can send data using outbound HTTPS:

    setx HTTP_PROXY http://proxy-ip:proxy-port /m
setx HTTPS_PROXY http://proxy-ip:proxy-port /m
setx no_proxy "metadata.google.internal,169.254.169.254" /m
Determine the agent version

To determine the version of the Ops Agent on your system, run the following commands on your VM instance:

Google Cloud console

To see the version of your Ops Agent on a VM:

CENTOS / RHEL

Run the following command on Red Hat or CentOS Linux:

rpm --query --queryformat '%{NAME} %{VERSION} %{RELEASE} %{ARCH}\n' google-cloud-ops-agent
DEBIAN / UBUNTU

Run the following command on Debian or Ubuntu:

dpkg-query --show --showformat '${Package} ${Version} ${Architecture} ${Status}\n' google-cloud-ops-agent
SLES / SUSE

Run the following command on SUSE:

rpm --query --queryformat '%{NAME} %{VERSION} %{RELEASE} %{ARCH}\n' google-cloud-ops-agent
WINDOWS

Run the following command on Windows:

googet installed google-cloud-ops-agent
Restart the agent

You must restart the Ops Agent to pick up changes in configuration files. To restart the agent, use the following instructions.

LINUX

Run the following command on your instance:


     sudo systemctl restart google-cloud-ops-agent
Windows

  1. Connect to your instance using RDP or a similar tool and login to Windows.

  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selecting Run as Administrator.

  3. Run the following PowerShell command:

Restart-Service google-cloud-ops-agent -Force
Upgrade the agent

To upgrade the Ops Agent to the latest release, use the following instructions:

Note: If you upgraded your instance's Linux operating system to a new major release, then you should first remove the agent and then re-install it using the procedures on this page, instead of completing these upgrade procedures. Google Cloud console

You can upgrade the Ops Agent by using Cloud Monitoring installation instructions. For more information, see Install the agent by using the Google Cloud console.

Linux

To upgrade the agent to the latest version, run the following command:

sudo bash add-google-cloud-ops-agent-repo.sh --also-install

To upgrade the agent to the latest point release of a specific major version, run the following command:

sudo bash add-google-cloud-ops-agent-repo.sh --also-install \
  --version=MAJOR_VERSION.*.*
Windows

To upgrade to the latest agent release:

  1. Connect to your instance using RDP or a similar tool and login to Windows.

  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selecting Run as Administrator.

    Note: If you're upgrading your agent from a version earlier than 2.0.3 to version 2.0.3 or later, the upgrade removes the old config file. If you customized your agent configuration, be sure to save a backup of your configuration file before upgrading, and then to apply the necessary changes to the configuration file after the upgrade. 
    Copy-Item -Path "C:\Program Files\Google\Cloud Operations\Ops Agent\config\config.yaml" -Destination "C:\Program Files\Google\Cloud Operations\Ops Agent\config\config.bak"

  3. Run the following PowerShell commands to remove your installed agent and to run the installation command:

    googet -noconfirm remove google-cloud-ops-agent
googet -noconfirm install google-cloud-ops-agent
List all agent versions

To list the available versions of the agent, run the following command:

CENTOS / RHEL

List the available versions of the agent:

sudo yum list --showduplicates google-cloud-ops-agent
DEBIAN / UBUNTU

List the available versions of the agent:

sudo apt-cache madison google-cloud-ops-agent
SLES / SUSE

List the available versions of the agent:

sudo zypper search -s google-cloud-ops-agent
WINDOWS

List the available versions of the agent:

googet available google-cloud-ops-agent
Uninstall the agent

To remove the Ops Agent and its configuration files, use the following instructions.

Note: If the Ops Agent was installed during VM creation, see Manage VMs covered by Ops Agent OS policy.

After you uninstall the agent, the Google Cloud console might take up to one hour to report this change.

Linux

Run the following command:

sudo bash add-google-cloud-ops-agent-repo.sh --uninstall

Optionally, to remove the repository in addition to uninstalling the agent, append --remove-repo to the previous command.

Windows

To uninstall the Ops Agent, follow the following steps:

  1. Connect to your instance using RDP or a similar tool and login to Windows.

  2. Open a PowerShell terminal with administrator privileges by right-clicking the PowerShell icon and selecting Run as Administrator.

  3. Run the following PowerShell command:

    googet -noconfirm remove google-cloud-ops-agent
VMs without remote package access

Installing the Ops Agent requires access to remote package repositories, for both the agent package and (on Linux) its dependencies.

If you are using VPC-SC or a private network, the network configuration might also affect your ability to install agent dependencies from upstream repositories. The agent packages themselves are accessible by using Private Google Access. This can be configured following Enable Private Google Access.

If your VM host's security policy denies access to remote package repositories, we recommend creating a custom VM image with the agent pre-installed and disabling package management in that image.

What's next

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4