UIv4 instances when there are none?
Perhaps I just wasn't paying attention previously, but does the new UI show everything has an instance even when it's not a multi-instance DataSource now? Is that a recent change? It automatically jumps to the "instance" when you click on the DataSource entry so not really causing an issue but kinda threw me for a loop when I thought a DataSource I was working on was somehow creating instances when it shouldn't. Seems kinda odd and perhaps confusing when training on what instances are if everything looks like it has one.67Views9likes3CommentsChange Instance Name
Hi, I have noticed a few alerts are not generating ticket within our Connectwise Manage via the integration, looking in the log i can see a 400 error with the below payload: { "code": "InvalidObject", "message": "ticket object is invalid", "errors": [ { "code": "MaxLengthField", "message": "The field summary must be a string with a maximum length of 100.", "resource": "ticket", "field": "summary" } ] } I understand that the length restriction will be from connectwise, but is there a way to change the name of an instance within logicmonitor. The alert in question here will be around 104 characters in length. The instance for this is picked up via auto discovery from Unifi Access Point Datasourceand i cannot see a way to change the name of this. Thanks, JamesSolved96Views10likes3CommentsInstance Management - Alerts
Hi, Curious to know how people have managed setting alert thresholds for datasources where new instances will not be recognised. The notice I get is: “These changes will only apply to existing instances of this datasource on this device. They will not apply to instances added later” This is a challenge for large environments where it’s easy to forget this fact, and potentially miss monitoring new instances altogether. Keen to get feedback on any strategies used to address this issue.Solved78Views1like4CommentsAvoiding duplicate instances
Hi Throwing something out there for advice. There are a number of datasources that are subject to duplication of instance because you cannot safely turn on the automatically delete as legitimate instances may go down for longer than 30 days. This appears to be due to them being very dependent on the instancename, so if this is something the customer has the ability to change then it creates another instance during Active Discovery. My question is if anyone has an ideas on a complex datapoint (or some other means) that can detect that this instance has matching property to another instance. This could be say auto.device.mac_address or even the Instance Value as these always match between the duplicate instances. This is really bugging me now so I really need to find a proactive way to address them. The real downside is that you lose the historical data when it is actually the same device. What the ideal would be is if you could merge instance or at least delete the new and rename the old one to the new ones name so its not discovered again.114Views0likes4Comments