Joe Tran

Members
  • Content Count

    127
  • Joined

  • Last visited

  • Days Won

    14

Everything posted by Joe Tran

  1. We recently received and deployed a datasource we got from @Jake Cohen that also displays the number of Cloud devices monitored by a Collector, which is important for my leadership to understand our account utilization/commit metrics. I would highly encourage "LogicMonitor Portal Metrics DataSource from the LogicMonitor Repository using locator code J7RGZY" also incorporate this datapoint.
  2. As a longtime SolarWinds user, they have NOT always had this capability innately. But they have always had a workaround similar to what is available to LogicMonitor--proliferate the number of logical objects you would have to maintain that controls alert trigger delays. In SolarWinds, this would be Alert Definitions. Not ideal. Hypothetically you could have used a component-level configuration field (notes or description) and used that in a complex SQL/SWQL-based alert definition to achieve this. Also not ideal. In SolarWinds SAM, they have added (in the past couple of years) the ability
  3. Looks like I am missing the "ListTagsForResource", but that action is also missing from the IAM Policy Visual Editor . I think TPTB that control IAM for my organization may have excised anything that didn't pop up as valid via the visual editor. Thanks, @Sarah Terry. I'll have the aforementioned TPTB re-do the policy.
  4. I chain two propertysources together--one to set an autoProp, and another to write that autoProp to location via REST API. The location property isn't prefaced by system, so it can't be set in just the one propertySource--i don't think. In the example below, the autoProp is called "auto.loc". import org.apache.http.HttpEntity import org.apache.http.client.methods.CloseableHttpResponse import org.apache.http.client.methods.HttpPatch import org.apache.http.impl.client.CloseableHttpClient import org.apache.http.impl.client.HttpClients import org.apache.http.util.EntityUtils import java
  5. Hi, @Sarah Terry. It is not. It is, of course, picking up the tags that get passed down to the EC2 instances the Elastic Beanstalk spins up, but those tags do not appear on the Cloud device representing the environment itself.
  6. Elastic Beanstalk tagging has been around since 2014 and AWS Lambda Function tagging is relatively recent as well. Would it be possible to get the Cloud Collector to start importing the tags as systemProperties like other AWS resources that support tagging?
  7. Since we're posting !groovy workarounds---here is one I'm using for telnet: hostname = 'internal.server.local' port = 22 try { s = new Socket(hostname, port) println "Connected to $hostname on port $port" s.close() return(0) } catch (ConnectException ce) { println ce.toString() return(1) } catch (BindException be) { println be.toString() return(4) } catch (NoRouteToHostException re) { println re.toString() return(2) } catch (PortUnreachableException pe) { println pe.toString() return(3) } catch (Exception e) { println e.toString() re
  8. I would like to see a !tcp <host> <port> OR a !telnet <host> <port> like command in the Collector Debug utility. It should return back the connection status and response time.
  9. Just got off a chat with Support---it should be coming with v2 of the REST API and that should be happening soon... right? Riight?!
  10. REST API. Fetch the IDs using a filter based on the name of the Website check and iterate through the fetched IDs to delete.
  11. Scenario -- I have a device group with a mix of AWS EC2 with Local Collector, EC2 with only the cloud collector, RDS instances, and Load Balancers. I went and created a device inventory report to grab some info about EC2 tags. It asks for a datasource, so I've tried a few--"Ping", "HostStatus", "AWS_EC2". No matter which I select, the resulting report has all devices--EC2, ELBs, RDS--regardless of the datasource selection. So obviously the datasource selection in this report type doesn't mean what I think it means. So what is this option used for?
  12. We went the pricey route and use PagerDuty to act as a middleman. This is largely something we did because this functionality wasn't supported out of box. It does look like the ServiceNow-Slack integration is available now, if you're on Kingston and have the IntegrationHub module--https://docs.servicenow.com/bundle/kingston-servicenow-platform/page/administer/integrationhub/reference/slack-spoke.html The company I work for just deployed Kingston and I'm told the module is available (but not deployed). So I have some "fun" times ahead championing this internally.
  13. There is a default limit of 2 . I've been bitten by this one before and I have not encountered anything with LogicMonitor's REST API that goes much beyond 4, but better safe than sorry.
  14. No worries. This is my first time contributing to a public project . And yes, I did test it . Verbose output using current: > $test_collector_details_update = Update-LogicMonitorCollectorProperties -AccessId $AccessId -AccessKey $AccessKey -AccountName $AccountName -CollectorId $CollectorName -PropertyNames collectorGroupId,escalatingChainId,description,resendIval -PropertyValues 3,1,'TestCollectorNewName',0 -Verbose 2018-07-18T17:32:36: Beginning Update-LogicMonitorCollectorProperties. VERBOSE: 2018-07-18T17:32:36: Finished updating $resourcePath. The value is /setting/coll
  15. I see that you've added this to Github . I've created two PRs to address issues I've been having with 1.0.0.26. I'm assuming the Public directory scripts are "bundled" when releases are created and uploaded to PowerShell Gallery.
  16. I would love to see a token that references other datapoints as a "workaround" in this use case. In the Staff example, the token would be ##actual_value## in the customized alert messaging for the complex datapoint.
  17. Collector or Collector Group-specific set of credentials used as a token in a Custom HTTP Integration, which triggers some form of self-heal (attempt to RDP/SSH into the Collector, restart services, or reboot the server, etc).
  18. Good to see customProperties in the Collector REST API. But properties that mask their values in the UI should respect that masking when fetching that information from the API.
  19. This sounds like an Alert Threshold report. This will give you the datasource name, instance, and when it triggers at what severity. When looking at the Alerts tab on a Device or Website OR when looking at the Alerts report OR when configuring an Alert List widget, there will be a table that lists the alerts according to the Filters configured above the table. You're looking for the Cleared filter, which is found under the More option. Toggling the Cleared filter to "All" will get you both historical and active alerts.
  20. Exactly. Or I'll take a OS-agnostic Collector if we're making a wishlist Having a Linux Collector would that can monitor Windows devices would solve this "problem" too.
  21. What's the outlook on the Windows Docker Collector?
  22. Sounds a good use case for defining a cluster alert. You would still need to set the global datasource definition to alert on no data. Your host cluster alert definition can control if individual node/device alerts will trigger alert actions. Works best if all NFS mounts are from the same source. https://www.logicmonitor.com/support/devices/device-groups/cluster-alerts/
  23. My organization originally committed to only creating tickets for CRITICAL level alerts, but naturally marching orders came down to create tickets at WARNING with vastly different set of ticket parameters. The kicker--do this only for specific LogicModules. I figured this was easy enough, until I saw that I wasn't able to select multiple LogicModules for any given alert rule. These LogicModules varied names and datapoints. Creating a glob expression that is not going to cause someone to go cross-eyed would be herculean feat. So instead of adding multiple alert rules with the same set of
  24. Hi @Brandon, It actually does! I was not aware of the toProperties() method. Thank you!
  25. You would create a new LogicModule > DataSources template. The Apply To expression should be set there. This makes the subsequent datasource available (or automatically applied if you choose to use Active Discovery) to Windows servers that have your desired services running. The rest of the Datasource would be designed to poll for your services and alert thresholds. There are many ways to do that. You can use a WMI collector (like in the WinService- datasource which you can clone and play with). OR if you feel adventurous you can use a Script collector and use Groovy or PowerShell (or