• Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Mosh

  1. Please make the access to Exchange via the nav bar limited to actual Administrators. This option should not appear for resource managers. For us Enterprise customers, we would like to make sure that only members of the Administrators role can have access to LM Exchange.

  2. 20 hours ago, David Lee said:

    Hi Mosh,

    Been a while hope you are okay, and yes thanks for pointing this out, we have already seen this and raised an urgent ticket for resolution, please feel free to hop onto chat for more information if you need it,


    David Lee

    UK Team Lead, Technical support

    Hi David!

    I'm well thanks, hope you are too. 

    For info, I also just noticed that if I add *State* as a Datapoint GLOB it causes my alert widget to complete fail to display anything (in one of my tests it also zapped the column settings I had).  As a workaround to the negative GLOB issue, I was adding specific expressions (see attached) and that's how I came across this.


    GLOB bug.png

  3. I noticed today that the alert widget had defaulted to having Static Threshold and Dynamic Threshold set as enabled.  This messed up our dashboard column widths and layouts and we had to go through and reconfigure them.

    Please, please, please do not default new columns to enabled. New things should be disabled by default.

  4. 1 hour ago, mkerfoot said:

    @Mosh Any chance you could make some thorough directions on how to replicate your custom google apps dashboard? I am very interested in making something like this but don't even know where to begin.

    Hi @mkerfoot, have sent you a message with a YouTube link on how to get started with Google Apps Script web apps.

  5. At the moment, when a graph is defined on a datasource, the graph always appears against the DS object under the resource object. We would like to have the ability to define graphs on a DS but be able to not display them on the resource.  Use case, we have graphs that we use for debugging that are added and removed when no longer needed.  Would be easier if we could keep the graph but simply disable it.

  6. At the moment, when a collector executes a PowerShell script, the command line of the PowerShell process will expose credentials (the <removed> parts below example).

    The better way to do this would be to save the strings to temporary files (this would be done by the collector agent), and the PowerShell scripts should read the content from the files and pass as arguments to the script cmdlet.  The problem with passing them in the command line is they are exposed in memory and malware could steal the credentials.

    PowerShell.exe -NoLogo -NonInteractive -InputFormat text -OutputFormat text -Command "& {$Password = ConvertTo-SecureString '<removed>' -AsPlainText -Force;$Credential = New-Object System.Management.Automation.PsCredential '<removed>', $Password;Get-WmiObject -NameSpace "ROOT\CIMV2" -Class Win32_PerfRawData_PerfOS_Processor -ComputerName "" -Credential $Credential -Filter name='''_Total''' | Format-List }"

  7. Just the ability to pass the alert message through a scripted function that returns a string back the alert handling process would meet many people's requirements in this space.  The alert message script could be part of the data source same as discovery and collection scripts. At datapoint level would be nice, but even at module level, it would be fine as we could if()...else or switch() case for data points.

  8. We organise our resources into groups that are our business services. We also use the device groups to define a hierarchy of the business service groups, so we have device groups that are used as taxonomy groups, simply to do nothing other than organise our hierarchy, and will never have any resources assigned to them.  However, it's possible to accidentally drag and drop resrouces into these 'taxonomy' groups, or for a user to mistakenly select one of these groups.

    What I would like is to have a special resource group type which is used for defining resource group taxonomy only and cannot have resources assigned to it.  The group's icon should also be different so that it is easy to know that this is a taxonomy group.