object versioning

Recommended Posts

There are currently far too many opportunities to commit errors in LM from which is is difficult to recover since there is no version tracking.  Ideally, it would be possible to revert to a previous version of any object, but especially very sensitive objects like logicmodules, alert policies, etc.  I have created my own method of dealing with this, which leverages the API to store JSON streams of all critical elements regularly, changes committed via git (certain adjustments to the original results are needed to avoid a constant update stream).  Recovery would be very manual, but at least possible.  This would be far more useful within the system itself.


  • Upvote 3

Share this post

Link to post
Share on other sites

Hi Mark,

Certainly an understandable request.  While not intrinsic in LM itself, it is possible to manage some aspects of your account in a programatic and versioned way via our integrations with Terraform and Ansible.  Beyond that, there is work underway that will help with some of what you mention:

  • Undelete for hosts and groups (upcoming release v103)
  • "safe import" for data sources (various aspects coming out over the next 2 quarters)
  • LM Exchange:  a versioned history of data sources from within an account (Q3/Q4).  Safe import is a pre-requisite to this.


Share this post

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.