Downgrade Wavefront | DX OpenExplore Proxy.
search cancel

Downgrade Wavefront | DX OpenExplore Proxy.

book

Article ID: 283161

calendar_today

Updated On:

Products

Insights Observability DX OpenExplore

Issue/Introduction

Proxy crashed due to JRE out-of-memory.  Proxy version not compatible with existing metric filter rules.

Resolution

The proxy is one of the key mechanisms to ingest data into Wavefront & DX OpenExplore.  When upgrading your proxy, it is best to have a rollback plan to deal with unexpected issues after upgrade.

While we advised to reach out to support for assistance proxy issues, downgrading the Proxy to the previous known good version, is many times the fastest way to resume ingestion while a cause and solution can be identified and released.

Standalone Proxy

Command used to downgrade depends on the proxy version installed. Here are three common OS command examples. Reach out to you OS support for additional assistance.

  • Linux: sudo apt-get update/install
  • Linux (RPM): yum update
  • Mac OS: brew update

In this example we are going to downgrade using Debian based distro commands. Quick install instructions for Debian or RPM can be found here, Wavefront proxy packages.

  1. Revert back to the desired version by installing the respective proxy package, you may have first to set wavefront repository.
    sudo apt-get install wavefront-proxy=<desiredVersion>
  2. Restart the wavefront-proxy:
    service wavefront-proxy restart
  3. Check the service status:
    service wavefront-proxy status
  4. Running the above status command will output to the status to the screen (Sample below). Make sure the proxy shows active (running) with no errors are showing,
    wavefront-proxy.service - LSB: Wavefront Proxy
    Loaded: loaded (/etc/init.d/wavefront-proxy; generated)
    Active: active (running) since <Date/Time> UTC; 2h 14min ago
    Docs: man:systemd-sysv-generator(8)
    Process: 10747 ExecStart=/etc/init.d/wavefront-proxy start (code=exited, status=0/SUCCESS)

Container Proxy

observability-for-kubernetes utilizes an Operator deployment type for its proxies. Each version of the Operator deploys only a specific version of the Proxy. 

Please work with your Kubernetes Admin regarding the underlying Kubernetes environment. Questions about your underlying Kubernetes environment are out of scope of this document.

  1. Go to Releases, and find the previous release version of the Operator related to the version of Proxy you want to install, for example v2.0.3. 

  2. To install the Operator version needed run this command:
    kubectl apply -f https://github.com/wavefrontHQ/observability-for-kubernetes/releases/download/PREVIOUS_VERSION/wavefront-operator.yaml
  3. Check the container status after running.
    kubectl get pods -A 

Additional Information

Proxy Troubleshooting
Wavefront Proxy Packages - Quick install instructions for:
Observability for Kubernetes Operator - Downgrade
wavefrontHQ / observability-for-kubernetes, Release Versions