Proxying onprem packages


On this page are examples with screenshots on how to repository the RPM packages for our on-prem package repository. The URLs differ for Debian-based Apt packages, you can find them here.

Examplary setup

To demo the setup, we use the following two machines:

  • - a machine running Nexus.
  • - a machine reading from Nexus.

As you can see, Nexus started, and we logged in as an administrative user:

logged in as admin in Nexus

Configuring a new repository

To configure the proxy repo, open the repo oversight:

create a new repository

Since we host this repository and you’re reading from it, choose a yum (proxy) repository type in the next pane:

choose yum proxy

Setting up the proxy repository

Enter a descriptive name so that other administrators know precisely what this repository does. In this example, we’ll pick instana-onprem-rpm-mirror. If you want to copy and paste the URL, you can find it here.

remote storage

Also, the repo URL goes without the agent key credentials; they are configured at the bottom of the screen:


Gather the required repository URl

After clicking “Create repository”, you are directed to the list of all the repositories we created. If we click on the newly created yum proxy repository, we’re being given the URL to the repo. In our case, it was and was created from the name we picked above. In a proper setup with authentication and https, it looks different.

Installing the onprem repository

To install the repository on the on-prem instance, we log into the machine, become root, and edit the repo config file in /etc/yum.repos.d/instana-product.repo (feel free to call the repo file whatever you like). Here we enter the options as such:

configuring the repository

  • name: A name for the mirror.
  • baseurl: The URL given when we open the configured repository in nexus on the top of the details page.
  • priority: We recommend 500 as a priority. This is important: Please notice that when you pick too low a priority, you can install a different version of third-party software that is required to run our setup (e.g., Kafka or Clickhouse).
  • enabled: Whether or not the package manager should scan and therefore use the repository.

Does it work?

Find out by issuing the repoquery command, which is part of the yum-utils package. On RHEL7 it is installed by default:

configuring the repository