• Home
  • Manage
  • Network zones
  • Migration
  • Deploy

Deploy network zones (migration)

When your plan for network zones is ready, it's time to implement them.

Prerequisites

To proceed with the procedure below, you need:

  • Planned network zones with defined names.
  • Enough ActiveGates in every network zone to deal with the planned load.

Procedure

  1. Activate the network zones feature in your environment. To learn how, see Activate network zones.
  2. Add a network zone to the configuration of every ActiveGate.
    1. Specify the ActiveGate's network zone in the ActiveGate configuration.
    2. Restart the ActiveGate main service.
  3. Add a network zone to the configuration of every OneAgent. Go zone by zone, editing the configuration of every OneAgent in one network zone before moving on to another This will assure transition without failovers.
    1. Specify the network zone via command-line interface. For instructions on cloud deployments, select the appropriate link in the expandable section.
      Deploy network zones in a cloud

      Kubernetes

      Deploy OneAgent on Kubernetes
      Deploy OneAgent on Kubernetes via DaemonSet
      Deploy OneAgent on Kubernetes for application only

      OpenShift

      Deploy OneAgent on OpenShift
      Deploy OneAgent on OpenShift via DaemonSet
      Deploy OneAgent on OpenShift for application only

      Amazon Web Services

      Deploy OneAgent on AWS Fargate
      Deploy OneAgent on Elastic Container Service
      Deploy OneAgent on AWS Elastic Beanstalk
      Deploy OneAgent on Elastic Kubernetes Service

      Azure

      Deploy OneAgent on Azure Virtual Machines
      Deploy OneAgent on Azure Kubernetes Service

      Cloud Foundry

      Deploy OneAgent on BOSH
      Deploy OneAgent on Pivotal Web Services
      Deploy OneAgent on IBM Cloud Foundry

      Google Cloud Platform

      Deploy OneAgent on Google Kubernetes Engine

      Heroku

      Deploy OneAgent on Heroku

    2. Restart your OneAgents in the following order
      1. Restart the services of OneAgents performing the full-stack monitoring.
      2. Restart OneAgent monitored applications, so that they pick up the new instrumentation.
      3. Restart application-only OneAgent deployments.
      4. Restart zRemote on ActiveGates.