Forum Discussion

Lewis_Beard's avatar
Lewis_Beard
Icon for Professor rankProfessor
30 days ago

hdsId ... minor API question

Apologies if this question seems frivolous or unimportant, but it has always bothered me that the designation for the "device datasource ID" in the API documentation, hdsId, starts with the letter "h".

I get that it is the device-specific datasource ID that is unique, for that datasource, to the device. I use it all the time in API calls. But it sort of bugs me that it is hdsId and not ddsId.

I'm sort of wondering if any long-term users or employees know why the letter "h" is used in the API documentation, and not "d". If it were ddsId then I would have naturally assumed that the d was meant to be "device". I could even understand rdsId where the "r" was for resource.

But nothing is clicking for hdsId. Anybody happen to know? Or did I miss it somewhere in the documentation?

2 Replies

  • Totally feel this. I’ve always assumed hdsId stood for something like "Host DataSource ID", since LogicMonitor used to refer to monitored devices as hosts. Even though the UI now uses the term “device,” the backend API has held on to some legacy terminology—probably for consistency or backward compatibility.

    So while ddsId (device datasource ID) would definitely be more intuitive today, I guess hdsId is just a leftover from the early days of LogicMonitor. A little odd, but not without its historic charm.

    Would love it if someone from LogicMonitor confirmed this officially, though—if nothing else, it’d help us sleep better at night knowing what the “h” really means

    • Lewis_Beard's avatar
      Lewis_Beard
      Icon for Professor rankProfessor

      Nice. I was unaware of host being an older term for what became devices, and now I guess the most modern is resource. Host makes sense. I was thinking almost in terms of a local implementation of an abstraction or template, and I was mentally fishing around for a word that started with "h" that might fit. I should have realized it was something like host.

      While you say host is just your best guess based on history, it fits so well that I'll probably roll with that in terms of how I think of it, even if LogicMonitor posts that its something more esoteric. :)