Cascaded Properties
So just looking at correlation again as I have some time, if I am correlating on say deployment.site for location which is set at the folder which is cascaded in LogicMonitor to the Components in the folder, but will Edwin see this or do I need to add the custom field to all devices rather than rely on cascading?
SteveBamford
4 comments
SteveBamford
OPOk I have confirmation deployment.site is being used successfully to correlate issues, it just wasn't so clear perhaps because of some of the other Models I had added.
When I removed the following it became a lot clearer.
Correlation by Manufacurer (Yes I know I can't spell)
Correlate by collector
Correlate by datapoint
I think it is more likely to be the top one that maybe confused things, but just goes to show how carefully you need to think about your models.
Callum Brown
Also worth mentioning that Edwin will also correlate on instance-level properties as opposed to just device level ones. However, when looking at the Insight, it does appear that a "device" has been included, juts owing to the different displays in Edwin vs core platform.
SteveBamford
OPThanks Chris I will do some more testing to see, it's just some of the correlating of alerts it is doing doesn't particularly make sense, I will check a few things and feedback, I had a brainwave as I was typing this which may be the reason 😀
Christopher Wallis
Hi SteveBamford​ ,
Edwin should be able to use inherited properties, so setting a property on an existing group should work. Edwin does sync custom properties from LM Envision every 4 hours, so if you add a new property it may take up to this time (depending on how lucky/unlucky you are!) for it to show in Edwin.
If you are having issues with this, let us know!
Chris