Forum Discussion

Lewis_Beard's avatar
7 days ago
Solved

Collector Device Name should be a Hyperlink but isnt

I have a collector, that is up and functioning normally, on my Collectors page, and as we always do, it monitors itself. I can get to the resource by searching for it in the Resource tree, I can see the resource lists itself as the collector with the right collector number. The IP on the resource matches the IP of the collector when I log into the collector itself. So everything seems fine.

BUT on the Collectors page (UIv3) where you have Status, ID, Device Name, Description, Version, Manage, Logs, SDT, Resoruces, etc .... the Device Name is supposed to be a blue Hyperlink, same as it is for every other collector we have.

I cant figure out what little tricky thing is making this link not work. I feel like I may have asked here or somewhere before. What are the requirements for that collector to have the Device link to its own resource? It is for sure monitoring itself.

Thanks!

  • My understanding is that it need to monitor itself, I don't recall if there are other requirements anymore but I would check:

    • Quadruple-check that the system.collectorid and system.collectordesc matches itself.
    • Check if the device has the "collector" category atleast.
    • Check if the device has collector DataSources.
    • Check the Collector Events and Status for any weirdness.

    I actually setup the IP of collector devices as 127.0.0.1 so I don't have to worry about it potentially monitoring the wrong server (which screws up the collector DataSources), or situations where customer decide to re-IP the server without letting us know, and can also help cover some DR situations.

  • My understanding is that it need to monitor itself, I don't recall if there are other requirements anymore but I would check:

    • Quadruple-check that the system.collectorid and system.collectordesc matches itself.
    • Check if the device has the "collector" category atleast.
    • Check if the device has collector DataSources.
    • Check the Collector Events and Status for any weirdness.

    I actually setup the IP of collector devices as 127.0.0.1 so I don't have to worry about it potentially monitoring the wrong server (which screws up the collector DataSources), or situations where customer decide to re-IP the server without letting us know, and can also help cover some DR situations.

  • I should clarify that the "Device Name" on the collectors page has the device name correct there, but its just not a hyperlink as it should be.

  • I had already verified the first 3, and they are all true/as expected. BUT looks like the watchdog was down. I forgot that doesnt actually throw an alert. And the collector datasources didnt have any alerts there, so I didnt think to look for that.

    Thanks Mike!

    • Mike_Moniz's avatar
      Mike_Moniz
      Icon for Professor rankProfessor

      Did that fix the issue? I would be surprised if the watchdog windows/linux service status would affect it being linked or not.