Allow same Device Names (different groups)

Makes sense - it will save you time if we suggest a unique name if there is a conflict.  I'll open a ticket for this - it wont get released for at least 5 months, most likely, as there is a big UI rewrite going on, and it will be done as part of (or after) that..

So we could do that now - if you modified the alert message template so it didn't just say HOST but said HOST in groups GROUPS it would then include the groups that a host is in, in the alert message.  Of course, that would need to be done for all the alert messages, in all the DataSources..... (We may be able to do a bulk update for that on the backend, if you want.) The alternative would be to use the new email custom alert delivery method (which is just about to be released) which uses a global template for all alerts -but then you lose the datapoint specific information in each alert message (e.g. sequential table scans are generally an indication of a missing index stuff that is in a lot of messages.)

We are still in the trial phase, but we are migrating from another monitoring software where nothing was dynamic. We got around this in the other software package by manually renaming every device for each customer with customername-devicename syntax. so it became customerA-ciscoasa5505, customerA-sqlserver, customerA-server9 etc.  We carried this same logic forward into LogicMonitor, and use the customername to automatically organize our remote devices into customer groups. so we basically rename everything to a known syntax, then have the dynamic groups organize everything for us, and it works great.

I'd like to throw in my voice on this as well. We've found that we cannot maintain the naming convention we've always used with our clients when they look at LM. Client A and Client B have servers named SBS, and that's what both the client and our techs expect to see when looking at the dashboards, etc. The way the system works now, we are essentially forced to prefix the name like clientb_SBS, which is definitely less awesome. Also - a nod to Logic Monitor support rep Joseph Skupniewicz. He did a great job answering my questions today.

Is there any update on the duplicate name being addressed? Is it going to be in the next UI release we were recently contacted about being in beta? As we grow our client base this is certainly becoming a bigger issue. Thanks!

Greg and Brendan - how would you like this addressed? The Displayname for a host has to be globally unique - otherwise if you are looking at a dashboard and see an alert for a server SBS - how could you know which device it is related to? (Assuming you are an admin that can see all devices.) Suggesting a new name with the group name prepended in event of a conflict is our plan - but sounds like that is not what you envision?

I think the easiest way would be group_name/device_name, this seems to be the way most monitoring tools manage it, or they allow you to create devices with the same name in different groups.

Id be perfectly OK with naming multiple things SBS, but the dashboard or any other out-of-context display widget referring to it as /SBS, just so long as *we* dont have to name the host differently. In this way it is inferred through the group, which means no added friction for determining names when adding or managing hosts.

We need servers to be easily identified by customers, for example 'mail server' 'exchange server' 'ad server'.

These may be used for each customer, of which we have 50....so you can see this can very quickly get confusing and difficult to manage.

I spoke to someone at LM a while ago who said devices were going to get a UID, making it possible to have the same device name used multiple times. Is this not happening?

Any update on this? Come on guys, it's been ages...!