Forum Discussion

nichharris's avatar
nichharris
Icon for Neophyte rankNeophyte
22 days ago

Device Notes Tab

Currently, my team tends to attach small important notes for devices (firewalls, servers, switches, etc.) in the Description box.

These notes might indicate if the device is supposed to be decommed soon, which vault the device's credentials are stored in, if the device is fully managed, who/manages owns the device, who deployed the device, or various other things.

The description box is not designed for this. So, there are obviously many issues with it. No accountability, no formatting, no separation, etc.

Could we please request a feature where each device in LM has its own proper "Notes" tab?


Notes could be time-stamped, author-stamped, edited, or deleted.

Examples:

"Device is scheduled to be decommissioned in 2 months.     -User123 4/30/2025 18:00:00UTC"

"Device is not managed. No creds available. Alert client in event of issues.     -User567 4/05/2025 03:00:00UTC"

"Power Supply replaced on 2/10/2024.     -User567 2/10/2024 10:00:00UTC"

Below shows where a note has been added to the Description Box for this device, indicating the PSUs were reseated on 4/30/2025. If there were a Notes tab, this snippet could be put there instead. Anyone seeing that device afterward would see that User123 made that note today at 2pm. Someone could add an additional note a few months later indicating those PSUs have been replaced, while removing the old note. 


If there is already a feature similar to this (or one in the works), please let me know.

lmfeature

5 Replies

Sort By
      • nichharris's avatar
        nichharris
        Icon for Neophyte rankNeophyte
        15 days ago

        Thanks for the reply. Not exactly what I'm looking for though. The biggest issue would be only Admins can add Ops Notes. Also, it would be nice to add notes that don't need time stamps: where a jumpbox is, where creds are, who owns/runs various applications on servers, random relevant notes, why device isn't on new firmware, if device is maybe slated for decommission, or things that may not be static enough (or not noted well) through device properties. 

  • pgordon's avatar
    pgordon
    Icon for Expert rankExpert
    14 days ago

    I like this idea and would love to see it too

    For now though, perhaps you can add a custom property (or two or more) to capture this? Not the most straight forward way of documenting the information but you'd have it attached to the device

    Or possibly make a custom multi-instance datasource that you add the details to?

    I'm not sure, I'm thinking out loud and have only added custom properties to devices before. And the custom properties I added were for things that don't tend to change.

    • nichharris's avatar
      nichharris
      Icon for Neophyte rankNeophyte
      6 days ago

      We use custom multi-instance datasources/properties for static information as well. Wouldn't want to put notes there, at least if conforming to our current environment standards. 

      The properties have no immediately viewable accountability or timestamp either. If you put in a custom property, the only way I know it's you is by reading the Audit logs (that only go out for one year). When was the note created (assuming user didn't timestamp it)? Who created the note (assuming the user didn't sign it)? When was the note last edited? I now have a note, but have to drill in the Audit logs first to see if it's even valuable and/or valid, assuming it was put in less than a year ago.

      Ultimately, just looking for that Notes tab. If nothing else, simply for the convenience. Also, the aggregate time that would be saved over a long period while viewing/triaging thousands of devices. Looking to make engineers' and techs' lives easier while reducing clicks-to-resolution across the board.