All Activity

This stream auto-updates     

  1. Last week
  2. Collector IP address / Interface

    Hmm not sure, wouldn't expect collector/java to force an interface. I didn't see anything obvious in the collector config files either.
  3. Collector IP address / Interface

    I understand what you're sating but the iSCSI interface on my server doesn't have a default gateway assigned. Windows wouldn't normally be using it try and send traffic to a routed IP address. My only thought is that LogicMonitor is forcing this interface to be used.
  4. Collector IP address / Interface

    Perhaps you can use routing tables on the collector host itself? At the OS level.
  5. Reports as body of email instead of attachment

    I agree that this as a built-in feature would be really great. In general, I find LogicMonitor's reporting capabilities, outside of graphing, to be really lacking. I've written scripts to retrieve the data I need for reports via the API. I have some jobs that dump data to a SQL database specifically for reporting purposes. It can be done but does require a lot more effort than should be required.
  6. Custom ConfigSource Issues

    And of course I kept plugging away and go it. It isn't pretty but it works. // import the logicmonitor expect helper class import com.santaba.agent.groovyapi.expect.Expect; // get the hostname and credentials from the device property table hostname = hostProps.get("system.hostname"); userid = hostProps.get("config.user"); passwd = hostProps.get("config.pass"); // initiate an ssh connection to the host using the provided credentials ssh_connection =, userid, passwd); // wait for the cli prompt, which indicates we've connected ssh_connection.expect("> "); // send a command to show the tomcat log file size, along with the newline [enter] character ssh_connection.send("enable\n"); // wait for the cli prompt to return, which indicates the command has completed ssh_connection.expect("# "); ssh_connection.send("terminal length 0\n"); ssh_connection.expect("# "); // capture all the text up to the expected string. this should look something like ssh_connection.send("show configuration\n"); ssh_connection.expect(" # "); cmd_output = ssh_connection.before(); // now that we've capture the data we care about lets exit from the cli ssh_connection.send("exit\n"); // wait until the external process finishes then close the connection ssh_connection.expectClose(); println cmd_output;
  7. Custom ConfigSource Issues

    I am having to write a custom configsource for Steelhead Riverbeds. There isn't a way to sftp a file off so I am having to write an expect script in groovy. I am trying to cobble together something using the Cisco Generic RunningConfig as a stepping stone, but I just can't get it off the ground. If I run it via the ConfigSources page with Test Script I get this. If I run it via collector debug and !groovy I get Any help would appreciated. Oh yeah the formatting of the cli. And what I have so far. import com.santaba.agent.groovyapi.expect.Expect; host = hostProps.get("system.hostname"); user = hostProps.get("config.user"); pass = hostProps.get("config.pass"); // open an ssh connection and wait for the prompt, user, pass); cli.expect("#"); // ensure the page-by-page view doesn't foul the config output cli.send("terminal length 0\n"); cli.expect("#"); // display the config cli.send("show configuration\n"); cli.expect("##\n") // logout from the device cli.send("exit\n"); cli.expect("#exit"); // collect the output config=cli.before(); // close the ssh connection handle then print the config cli.expectClose(); println config; And now what I have so far
  8. Hi, I have a number of switches and routers and want to create a report to view specific interfaces on these devices that relate to a certain solution. For example; if I want to have a report which shows interfaces relating to Internet breakout only I'd want a couple of CORE interfaces and the same on firewalls and routers. All I can seem to find is a report which shows interface bandwidth for all interfaces on multiple devices which isn't what I need. Any suggestions? Thanks. Pete.
  9. Collector IP address / Interface

    Is it possible to specify an IP address or interface that the Collector should use for ping and website checks? The server that I have a Collector on has 2 IP address, for general network and a second for iSCSI connected to a storage network. I'm getting a few false alarms because the collector is trying to ping using the iSCSI IP address. Anyone know of a solution rather than moving the Collector to another server? Thanks,
  10. Office365 Monitoring

    Awesome!!! great work. Cant wait for this to give a try..
  11. ManageEngine ServiceDesk Plus MSP Integration

    Hello, Sorry for the extreme delay. First things first. After upgrading Servicedesk plus 9.4 it started to behave differently. I've been in contact with Manage Engine and I've been in contact with Logic Monitor. We are looking for another ticket system.There is just too much arguments for leaving Servicedesk plus MSP version. However, after the upgrade SDP stopped receiving alerts. I troubleshooted for a very long time and found out that I couldn't use some of the tokens. Not happy about that at all. I also started using a type of json instead of the xml version. You need to set the integration to raw and use urlencodes as content-type. Do not use JSON because SDP cannot interpret that. Below is an integration for new alerts that we found was working. If you put this in a json verifier on internet it will fail right away but it is in this format SDP wants the data. format=json&data={ "operation": { "details": { "requesttype": "Incident", "priority": "Low", "urgency": "Low", "mode": "Other", "subject": "***##LEVEL##*** | ##ALERTID## | ##HOST## | ##DATASOURCE##", "description": [ "Host: ##HOST##", "\nLM AlertID: ##ALERTID##:", "\nDatasource: ##DATASOURCE##", "\nDatapoint: ##DATAPOINT##", "\nDatapoint Description: ##DPDESCRIPTION##", "\nLevel: ##LEVEL##", "\nStart: ##START##", "\nDuration: ##DURATION##", "\nValue: ##VALUE##", "\nClearValue: ##CLEARVALUE##", "\nReason: ##DATAPOINT## exceeds ##THRESHOLD##", "\nGroup: ##GROUP##", "\n\nCustomer Location: ##location##" ], "category": "[Category]", "subcategory": "[SubCategory]", "requester": "Logic Monitor", "site": "", "group": "Server Management", "account": "" } } } You also need to set the alert integration to get the ticketnumber from SDP. It looks like this. The others look like the setting above. Enjoy!
  12. This is a pretty important feature needed and I see no feedback from LM at all. This one seems like it would be pretty simple to add as an option to the report configuration -- please add ASAP. It is hard enough to get folks to pay attention to reports without having them have to go through additional effort to do so. I would much rather see this than whatever effort was applied to rename Devices to Resources.
  13. Export Netflow from Windows Server to LogicMonitor

    That is what it was, the IP has to be put in not localhost. Thank you!
  14. AKCP DataSources

    AKCP DataSource locators: AKCP Airflow: 4MZTXG AKCP Dry Contact: ZFD72C AKCP Humidity: MYFX6L AKCP Switch: XD379J AKCP Temperature: 7RJDJH
  15. Export Netflow from Windows Server to LogicMonitor

    Not sure about the netflow stuff but with wireshark (which also uses winpcap) it might not support using Perhaps try using the lan ip?
  16. Issues With Creating A Datasource

    This was it. Thank you! Next yeah I will work on using the encoder to fix future issues. @Michael Rodrigues I went with MIke's suggestion and yeah that worked. Thanks!
  17. Issues With Creating A Datasource

    Taking Mike's advice, you might just try swapping out your filter string with the URLEncoded version: "startEpoch%3E%3A1538370000%2CendEpoch%3C%3A1541048399%2Ccleared%3A*"
  18. Export Netflow from Windows Server to LogicMonitor

    Are there any trouble shooting steps? I have installed both Winpcap and confirmed it is running and getting traffic by using the winpcapdump. The Server has LogicMonitor installed on it so the Flow Exporter is pointing to local host port 2055 (default I think) and the collector is set to get netflow data, but no data is showing in the Traffic tab. Is there something else I can look at? Also I did change the config file to use nf5 and not nf9. I've also tried to change localhost in the file to the IP of the interface.
  19. Issues With Creating A Datasource

    Since it's part of a URL you might have to use urlencode rather than htmlentieies. So ">" would be "%3C". There is also in Groovy. I would look at perhaps using something like pairs << ("${k}=${URLEncoder.encode(v, "UTF-8")}") in your packParams() function.
  20. Issues With Creating A Datasource

    It is the > in the filter. I tried converting to htmlentities and that didn't work. I tried escaping it and that didn't work either. Any ideas? I am still learning Groovy.
  21. Is it possible to check an FTP site using an internal web check, and using Groovy script in the request / response? This URL ( seems to indicate the commands that can be used, as if it's limited in some way. I can't think of another way to check the alive-ness of an FTP site somewhere on the web via LogicMonitor, if the device isn't in LogicMonitor itself. Any ideas? Thanks, Roland.
  22. DFSR Replication Backlog

    I used the old one and it does'nt work, can't find any instances on the DFSR replica partners. Are there any update to this DS??
  23. SNMP Trap Event Consolidation

    Reviving an old thread, but we're currently reevaluating EventSource suppression logic. Some of the other EventSource types already use a timeout like mechanism to avoid duplicates, but we don't do anything like that for SNMP traps. The general idea right now is to let the user decide which duplicate fields indicate a duplicate event, and suppress anything within the "effective interval" of the original alert. I think it makes sense to have the timer reset logic be optional. I also like the idea of providing more visibility on how many events were suppressed. We've also had a fair number of requests for a mechanism like the DataSource "trigger interval", where we only trigger an alert if we see the same event N times in the interval. Anyways, any additional feedback is appreciated.
  24. Issues With Creating A Datasource

    I haven't tested your code but I would try doing some testing and attempt to narrow down which part exactly is causing the issue. For example does your code work fine if you remove all the parameters from the URL? And if you remove just the filter part? My gut feeling would look at the non-alphanumeric characters in your filter and there might be differences between how REST calls work in PS vs Groovy. Perhaps they need to be escaped. You might also want to simplify your code, just for testing, in case there are issues with function parameters or the like.
  25. Radical Suggestion for Web Sites

    Seconded - this is a great idea.
  26. Device Group membership

    @Tanvir devices already have a property system.staticgroups that can be used to match group membership in a custom query. Additionally, properties set at the group level will be inherited by the devices within that group.
  1. Load more activity