Joe Tran

Members
  • Content Count

    127
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Joe Tran

  1. P.S. If I have not gone crazy in my line of thinking, please update the REST API Documentation to include descriptions/methods/models etc for /setting/alert/internalalerts resources. 😀👋
  2. I will admit that I had completely forgotten that External Alerting was a thing. When we first started with LogicMonitor (like 3+ years ago), someone at LogicMonitor had mentioned External Alerting as a potential solution for a random use-case and I had immediately disregarded out of hand--favoring a Custom HTTP Delivery integration instead. Fast forward to now and this post, and all this recent talk about self-heal and actions and an idea was sparked. Some internal partners are building automation tools to resolve issues and are pretty comfortable with some DIY. Originally, I had
  3. So they already renamed Devices to Resources. I can only hope this feature request is on the horizon 😉. Totally not wishful thinking, right? 😅
  4. I need to spend more time in a non-admin role 😑. It looks like all users, despite what is defined in "User Access" for their roles, are able to list other users via Dash Sharing and Reports Schedule. We feel that should not be the case. I would only want my coworkers to be able to do this, NOT my clients who should not be aware of each other (at least not through our monitoring application).
  5. I've opened a case with support and in the meantime, I've gone through all our client user accounts and disabled their access to Reports until we get this sorted out.
  6. I love the Reports UI but my users who have only View access to Reports or any given Report Group SHOULD NOT be able to see the reports generated by other users. The previously generated reports are great, but they are hosted in S3 and don't check against the user roles we have assigned to our users. We have a common set of reports that all of our clients use and when they run them on-demand in the old UI, that's all they get--that particular run. Client ABC can now see a version of a report that was run by Client XYZ by clicking on a link. Not good. Making all runs of a report available
  7. I like it. I made two modifications to our local copy: - disabled Active Discovery - changed the metric path from Resource=##WILDVALUE## to Resource=##system.aws.resourceid##:##WILDVALUE## Since adding a property is a manual step anyway, I figured keeping this LM resource as "cloudy" as possible better suited our needs. The scripted Active Discovery never created the DSI for me and that's probably because I didn't assign a collector to the monitor the LM Cloud resource.
  8. AWS lists that the Listener limit is on a per ELB basis. The AWS_ClassicELB_ServiceLimits datasource seems to intimate that the ListenerUsage is returning the total number of listeners for the given region. Is this useful information to capture on a regional basis or should this be refactored to apply to each classic ELB?
  9. Most of the Linux environments I work with are RHEL or CentOS and our prompts look like: [username@hostname ~]$ I can't seem to find a prompt pattern that works for both the closing square bracket and the dollar sign when writing a script using the com.santaba.agent.groovyapi.expect.Expect package. No amount of escaping seems to work like '\\]\\$' or ']\\$'. I do need the multi-character prompt because the output I want to parse will include errant $, but not ]$. Multi-character prompts are generally not a problem because I often have to expect a sudo password prompt using a 'use
  10. I've waffled on this feature a bit internally. Being able to see the request payloads would give the viewer access to see privileged credential information potentially.
  11. Honestly, I don't use glob in the Resource searching, but I can confirm it is behaving as @Mosh describes.
  12. CORRECTION to my last post. You'll want to iterate through 'items' list which is in the 'data' JSON-object.
  13. You could hypothetically use dynamic groups and helluva lot of regex to do that. The system.ips property appears to be one of those array properties, so use the join( ) function to combine them. Then use regular expression equality--- join(system.ips, ",") =~ "192\\.168\\.0\\.[0-2]?[0-9](?:,|$)" This should filter the group's membership to only include devices with IPs from 192.168.0.0 to 192.168.0.29.
  14. A couple things. If you are using the requests Python package, you can use the .json() method from the response class. The .content property will return bytes, and that just makes things more complicated than necessary. Assuming this is v1 REST API (because you are referencing the 'data' key from the response), is your API call hitting the /device/devices/{devId} or is it /device/devices resource path (i.e. are you GET'ing a specific device by id or a list of devices)? A GET for /device/devices should return a <class 'list'> object for the 'data' key or, as @Mike Moniz
  15. This will certainly help with ensuring our Collectors are adhering to our internal standards, but it looks like the PropertySource is "undergoing security review".
  16. It looks like if a collector goes down, the internal website check won't trigger the alert for website-overall, if we configure alert trigger to "at All test locations" and have more than one collector assigned to monitor the app. Strangely, I can see in the raw data and graphs that the website-Overall does switch value to 2 (i.e. not OK). We are an AWS shop and deploy collectors in each client's VPC AND from a collector that has routing to the client VPC (e.g. from the client's on-prem network). We were conducting DR testing where the AWS based collector was "killed" along with th
  17. Sorry for being unclear. I was attempting to consume instance level properties in a PowerShell collection script. The PowerShell Collection script tried assigning two ILPs to a variable-- one was a JSON formatted string (auto.events) and another was a plain ol' string (auto.logname). Like so: $events = '##AUTO.EVENTS##' $logname = "##AUTO.LOGNAME##" It took a little testing and debugging to figure out that my attempts to iterate through the JSON object were failing because the substitution engine were making these empty strings .
  18. It had been ages since I had to write a datasource in PowerShell so I haven't stayed up-to-date on the latest bells and whistles available. But I was very surprised to see that instance properties are still not supported. With the substitution engine and enhancements made on the Groovy-side, I would have thought this trivial to implement. Is supporting instance properties on the horizon for PowerShell scripting for Datasources?
  19. Is there a newer version of what @David Bond (LM) posted? The one listed above is "currently undergoing security review".
  20. First, huge--- HUGE--- thank you for publishing the REST API v2. I did notice that some GETs for some resources don't support filter querying--specifically historysdts. We want to filter based off of startEpoch and endEpoch. I would also love to see historysdts officially support for websites and website groups
  21. @Sarah Terry Fortunately, SF checkpoint is fine for our use cases but we do have to reconsider how our Website checks are configured. For some of our apps we will alert if >= 50% of checkpoints are in error and for our US-based client base, we only use the US-based checkpoints. We will have to revisit checkpoint assignments and alert triggers for our Website checks now. We do have hardware and therefore Collectors across the country. Is it possible to have a mix of the public and internal checkpoints assigned to the same Website check in the future? Obviously, certain features won't be
  22. Adding LAC-based checkpoints to the chorus as well as UK and Europe based checks.