• Skip to main content
  • Skip to secondary menu
  • Skip to primary sidebar
The Blog of Jorge de la Cruz

The Blog of Jorge de la Cruz

Everything about VMware, Veeam, InfluxData, Grafana, Zimbra, etc.

  • Home
  • VMWARE
  • VEEAM
    • Veeam Content Recap 2021
    • Veeam v11a
      • Veeam Backup and Replication v11a
    • Veeam Backup for AWS
      • Veeam Backup for AWS v4
    • Veeam Backup for Azure
      • Veeam Backup for Azure v3
    • VeeamON 2021
      • Veeam Announces Support for Red Hat Enterprise Virtualization (RHEV/KVM)
      • Veeam announces enhancements for new versions of Veeam Backup for AWS v4/Azure v3/GVP v2
      • VBO v6 – Self-Service Portal and Native Integration with Azure Archive and AWS S3 Glacier
  • Grafana
    • Part I (Installing InfluxDB, Telegraf and Grafana on Ubuntu 20.04 LTS)
    • Part VIII (Monitoring Veeam using Veeam Enterprise Manager)
    • Part XII (Native Telegraf Plugin for vSphere)
    • Part XIII – Veeam Backup for Microsoft Office 365 v4
    • Part XIV – Veeam Availability Console
    • Part XV – IPMI Monitoring of our ESXi Hosts
    • Part XVI – Performance and Advanced Security of Veeam Backup for Microsoft Office 365
    • Part XVII – Showing Dashboards on Two Monitors Using Raspberry Pi 4
    • Part XIX (Monitoring Veeam with Enterprise Manager) Shell Script
    • Part XXII (Monitoring Cloudflare, include beautiful Maps)
    • Part XXIII (Monitoring WordPress with Jetpack RESTful API)
    • Part XXIV (Monitoring Veeam Backup for Microsoft Azure)
    • Part XXV (Monitoring Power Consumption)
    • Part XXVI (Monitoring Veeam Backup for Nutanix)
    • Part XXVII (Monitoring ReFS and XFS (block-cloning and reflink)
    • Part XXVIII (Monitoring HPE StoreOnce)
    • Part XXIX (Monitoring Pi-hole)
    • Part XXXI (Monitoring Unifi Protect)
    • Part XXXII (Monitoring Veeam ONE – experimental)
    • Part XXXIII (Monitoring NetApp ONTAP)
    • Part XXXIV (Monitoring Runecast)
  • Nutanix
  • ZIMBRA
  • PRTG
  • LINUX
  • MICROSOFT

VMware: How to solve the error with Telegraf and vSphere “Task Name: Remote View Manager, Status: The request refers to an unexpected or unknown type”

28th March 2019 - Written in: vmware

Greetings everyone, if you have followed this blog for quite some time, I am sure you have stopped by the blog entry about How to Monitor a vSphere Environment using Grafana, InfluxDB and telegraf. That blog post has tons of comments, and feedback from all of you around the Globe, which is great. Lately I’ve started receiving some comments about a common error that some of you have seen once deployed the solution, the error should say something like this:

Task Name: Remote View Manager, Status: The request refers to an unexpected or unknown type

And it will look this on the vSphere Client, thanks to Stuart Kennedy for the screenshot:

This is due to an old telegraf version you might be using, and the solution it is quite simple, upgrade to the latest telegraf version.

How to upgrade to the latest version of telegraf

The first thing you can do, for your own knowledge, it is to check which version you are running, it is as easy as run the next command:

telegraf --version

The telegraf version with the fix for vSphere to avoid the notification it comes starting telegraf v1.10.1, so if you do not have it just yet, keep reading.

You can upgrade with the service running, but just to be on the safe side, let’s stop the telegraf service now:

service telegraf stop

And now depending if you have installed from the repository, or from the packages you should follow the relevant step for you.

If you have installed telegraf from the repository, just run the usual commands of your distro to update and upgrade the packages:

Debian/Ubuntu

apt-get update && apt-get upgrade

RedHat/CentOS

yum update && yum upgrade

If running from the packages, download and install it depending your OS:

Debian/Ubuntu

wget https://dl.influxdata.com/telegraf/releases/telegraf_1.10.1-1_amd64.deb
sudo dpkg -i telegraf_1.10.1-1_amd64.deb

RedHat/CentOS

wget https://dl.influxdata.com/telegraf/releases/telegraf-1.10.1-1.x86_64.rpm
sudo yum localinstall telegraf-1.10.1-1.x86_64.rpm

During the install it is more than probable that the system will ask you if you want to replace your config with the new one from the package, let’s say N just to be on the safe side:

Configuration file '/etc/telegraf/telegraf.conf'
 ==> Modified (by you or by a script) since installation.
 ==> Package distributor has shipped an updated version.
   What would you like to do about it ?  Your options are:
    Y or I  : install the package maintainer's version
    N or O  : keep your currently-installed version
      D     : show the differences between the versions
      Z     : start a shell to examine the situation
 The default action is to keep your current version.
*** telegraf.conf (Y/I/N/O/D/Z) [default=N] ? N

And finally you can start the service again:

service telegraf start

As easy as this is, please try it and let me know if the error is gone after you have run all the needed steps.

Filed Under: vmware Tagged With: grafana vmware, telegraf, telegraf grafana, telegraf vmware, telegraf vsphere

Reader Interactions

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

  • E-mail
  • GitHub
  • LinkedIn
  • RSS
  • Twitter
  • YouTube

Posts Calendar

March 2019
M T W T F S S
 123
45678910
11121314151617
18192021222324
25262728293031
« Feb   Apr »

Disclaimer

All opinions expressed on this site are my own and do not represent the opinions of any company I have worked with, am working with, or will be working with.

Copyright © 2025 · The Blog of Jorge de la Cruz