• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

124 Excellent


About Mosh

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Actually ignore this. Support have shown me that we can control this via the LogicModules settings in a role. I panicked and thought it was going to be visible to all.
  2. 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.
  3. 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.
  4. 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.
  5. This is more for info. I noticed today that in v136, negative GLOB expressions are not working in alert widgets. I have a ticket open (it's urgent for us). @Sarah Terry
  6. Not actually sure who my CSM is now, so unlikely it will be in the system.
  7. I've also requested this in the past. And, I also have need to be able to do it via the API, for example, when our workflow detects a ticket has been closed but the alert remains.
  8. Hi @mkerfoot, have sent you a message with a YouTube link on how to get started with Google Apps Script web apps.
  9. Would be good to have STDOUT and STDERR as standard tokens. Though as they could contain a lot of content, would need a special view, opens in a new dialog to scroll through the content ideally in a console font, rather than the current method of viewing properties using the Info tab.
  10. 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.
  11. 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 }"
  12. Another reason why I'd like to pass the alert message through a script first would be for SSL cert alerts. Rather than "SSL cert will expire in n days" I would prefer to have it say "SSL cert will expire on <date>". With a alert message script we could perform that calculation.
  13. 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.
  14. I like the idea, but I would want the option to hide it by default or limit its visibility based on a role.