All Activity

This stream auto-updates     

  1. Yesterday
  2. 대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽
  3. 대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽
  4. 대전출장샵 카톡 kn02 홈피 kan05.net 대전콜걸 대전퇴폐업소 대전오피스걸 대전키스방 대딸방 립카페 만남클럽 부산출장샵 카톡 kn02 홈피 kan05.net 부산콜걸 부산퇴폐업소 부산오피스걸 부산키스방 대딸방 립카페 만남클럽 계룡출장샵 카톡 kn02 홈피 kan05.net 계룡콜걸 계룡퇴폐업소 계룡오피스걸 계룡키스방 대딸방 립카페 만남클럽 공주출장샵 카톡 kn02 홈피 kan05.net 공주콜걸 공주퇴폐업소 공주오피스걸 공주키스방 대딸방 립카페 만남클럽 논산출장샵 카톡 kn02 홈피 kan05.net 논산콜걸 논산퇴폐업소 논산오피스걸 논산키스방 대딸방 립카페 만남클럽 당진출장샵 카톡 kn02 홈피 kan05.net 당진콜걸 당진퇴폐업소 당진오피스걸 당진키스방 대딸방 립카페 만남클럽 보령출장샵 카톡 kn02 홈피 kan05.net 보령콜걸 보령퇴폐업소 보령오피스걸 보령키스방 대딸방 립카페 만남클럽 서산출장샵 카톡 kn02 홈피 kan05.net 서산콜걸 서산퇴폐업소 서산오피스걸 서산키스방 대딸방 립카페 만남클럽 아산출장샵 카톡 kn02 홈피 kan05.net 아산콜걸 아산퇴폐업소 아산오피스걸 아산키스방 대딸방 립카페 만남클럽 천안출장샵 카톡 kn02 홈피 kan05.net 천안콜걸 천안퇴폐업소 천안오피스걸 포천키스방 대딸방 립카페 만남클럽
  5. LogicMonitor PowerShell module

    Oh, you don't need the hash table. When I run with the property capitalization, the cmdlet works fine. For "display name", you need to use "displayName". Update-LogicMonitorDeviceProperties -AccessId $lmAccessId -AccessKey $lmAccessKey -AccountName <account name> -DeviceId <id> -PropertyNames displayName -PropertyValues <new name>
  6. LogicMonitor PowerShell module

    Your experience is interesting, because I update the displayName property of our new collectors several times a week. In the script we use to deploy collectors, I use the following code: $BlockLogging = $true # Just used for this example, to prevent the steps from being written to the event log. $collectorProperties = @{"displayName" = "testdevice"; "hostGroupIds" = "<a valid group ID>"} Foreach ($keyValuePair in $collectorProperties.GetEnumerator()) { Try { $lmResponse = Update-LogicMonitorDeviceProperties -AccessId $lmAccessId -AccessKey $lmAccessKey -AccountName <account> -DeviceId <device ID> -PropertyNames $keyValuePair.Key -PropertyValues $keyValuePair.Value } Catch { $message = ("{0}: Unexpected error updating the property: {1} on {2}. The value should be: {3}. The specific error is: {4}." -f (Get-Date -Format s), $keyValuePair.Key, $hubLongName, $keyValuePair.Value, $lmResponse) If ($BlockLogging) {Write-Host $message -ForegroundColor Red} Else {Write-Host $message -ForegroundColor Red; Write-EventLog -LogName Application -Source $EventLogSource -EntryType Error -Message $message -EventId 5417} } } If you put the displayName property into a hash table like I did, do you have the same problem? I'll try to find some time to create the other cmdlet you suggested.
  7. Last week
  8. Our organization is new to LM, and I was working on an issue today that required looking at different time spans to see the delta over a week, month, and longer for a particular trend. I noticed that the "Custom" option in the drop-down list above was grayed out, so I looked at other graph types and found they all were grayed out for Custom. I consulted the Help topics but didn't find an explanation, so I contacted support. They explained that prior to expanding the Graph, I could utilize the Time Range tab at the top of the page to specify my custom time span. At that point, Custom in the drop-down is enabled for selection and returns the specified range. My two suggestions or request for enhancements would be to please trigger the Time Range screen (attached) upon selection of Custom from the drop-down menu, and also that after I viewed the Custom time span, if I selected any other predefined span (like Last 30 days), Custom was again grayed out, and I had to return to the previous screen to set it once more. This made the process of viewing last 4 weeks, then 5, then 6 up through last 12 weeks very inefficient and ungainly to navigate through.
  9. Hi all, I'm trying to find ideas, scripts, processes for a function our customer approached us with. In short, they want LM to place a call once per hour to the Interactive Voice Response application to ensure the IVR system answers the call, prompts are being displayed, and host database connection is established. My only is guess is to somehow create a Datasource that runs a script to interact with an API that somehow makes a phone call and then displays information as a result. I would like to know if this already part of LM or would need to be heavily developed in-house or is even remotely possible to implement. If you have had any success with this type of monitoring, I'd appreciate your insight. Thanks much
  10. Timezone per user account

    Hi all, This has been prioritized again for 2018. To provide a little background: Changing the way data is displayed in the UI is relatively easy, but once data is outside of LogicMonitor (i.e. alert messages, report content) it is no longer dynamic. To change content based on recipient is much more complex, and we don't have a good solution for this (yet). The last thing we want to do is create inconsistencies that further complicate the issue we're trying to solve, which is why this project was put on hold in the past. We know how important it is to support our customers with global resources, we just want to make sure we do it right. With that in mind, and to ensure things go smoothly this time around, we are considering approaching this in phases: 1. Ability to view data in the UI (dashboards, devices, alerts) in user-specific time zone. All configuration operations (scheduling SDT, escalation chains, report delivery, report content, etc) are still done in the account/global time zone (this would be explicitly indicated in the configuration window). Alert messages (i.e. ##START## token) also remain in the account/global time zone. 2a. Ability to configure events (SDT, escalation chains, collector upgrade, report delivery, etc) in user-specific time zone (or possibly user-specified time zone via time zone picker). Each configuration will record and display in the time zone it was set in. 2b. Ability to configure report content (SLA period, time range, etc) in user-specific time zone (or user-specified). Resulting report will be the same regardless of recipient. 3. Ability to receive alert messages and reports in recipient's time zone. We're interested to hear your feedback in terms of these phases as we work through the requirements. What is your highest priority? What percentage of your problems are solved by phase 1 alone? What are your biggest concerns? If alert messages are in a different time zone than your portal data, how does this affect your workflow? Feel free to shoot me an email at ali.holmes@logicmonitor.com. -Ali
  11. LogicMonitor PowerShell module

    @mhashemi I looked at the verbose output of your command and it actually it looks like the issue is that you are using the PATCH method which only allows updating of custom properties. If you were to change this to a PUT and instead use the path for properties, it would allow any property to be updated. https://www.logicmonitor.com/support/rest-api-developers-guide/devices/update-device-properties/
  12. LogicMonitor PowerShell module

    @mhashemi also, just FYI (though I don't need to use it at the moment) Get-LogicMonitorServiceProperties does not seem to work for me. I would also think a nice compliment to this would be a new Update-LogicMonitorServiceProperties cmdlet (if you get time for it)... though the first issue I mentioned I would think is more valuable to me. Thanks in advance!
  13. LogicMonitor PowerShell module

    @mhashemi thank you for creating this. One question/issue.... should Update-LogicMonitorDeviceProperties support updating any system properties? I tried to use this to update system.displayname and though the command says successful, nothing is changed. In addition if I do system.foo, it says it works but actually doesn't. However, any other property name (e.g. foo.system) works fine. There is something about system.X properties that the update cmdlet (or API) doesn't seem to like. Thoughts?
  14. Hello, I have made a support request (98189) already about this and learned that setting SDT via a Port "Description" is possible through the API. For those that are not API-savvy, I thought making a feature request to do this in the Lomo GUI might be a good idea. I would like to see if the possibility of setting SDT in the Lomo GUI can pull up something like a search page for matching criteria. It could be tags, device names, port descriptions, etc. The use case is for when I do VMware Host Updates, I have to set 11 SDT's individually. 4 for each Core Switch (we have 2, so 8 total there), one for each Fiber HBA interface on the Fiber switch (we have 2, so 2 there), and on the ESX-Host at the Monitored vCenter level (1). That sometimes is time consuming and would be nice to have it done once on many things that match... that the user could select the matching objects. It would be nice to search and enter in "Blade1-Chassis1" and set SDT for things that match a "Description" with that matching information. Then, have it present matched areas and then I can select, set an SDT time-frame and do it once. How nice is that? Is that something that is available to do now, or is this something you would consider making a "feature request" on? Thanks for your time, Aaron
  15. Time Zone setting at the User level

    Ali, Thank you for your post and I will follow up with a direct email to you. Eric Feldhusen
  16. Groovy - Ignore SSL Issue

    Alright, disregard that old code, whoooo, that's a lot harder to do than what you pointed me at @Michael Rodrigues, i can't believe I missed that in the support documentation. Anyways, got it working this way. Thanks! import com.santaba.agent.groovyapi.http.*; import groovy.json.JsonSlurper; def hostName = hostProps.get("system.hostname"); def user = hostProps.get("viptela.user"); def pass = hostProps.get("viptela.pass"); slurper = new JsonSlurper() // instantiate an http client object for the target system httpClient = HTTP.open(hostName, 443); // use an authentication API call to initiate a session // specify the url to which we want to post url = "https://"+hostName+"/j_security_check"; def payload = 'j_username=' + user + '&j_password=' + pass; // do the post def postResponse = httpClient.post(url, payload,["Content-Type":"application/x-www-form-urlencoded"]); // does the response indicate a successful authentication? if ( !(httpClient.getStatusCode() =~ /200/) ) { // no -- report an error, and return a non-zero exit code println "authentication failure"; return(1); } // we are now authenticated. Subsequent GETs with the httpClient will pass in the session cookie url="https://"+hostName+"/dataservice/alarms/count"; def getResponse=httpClient.get(url); // print some data //println httpClient.getResponseBody(); arrayLines = slurper.parseText(httpClient.getResponseBody()); println "count:" + arrayLines.data.count[0]; println "cleared_count:" + arrayLines.data.cleared_count[0];
  17. Groovy - Ignore SSL Issue

    @Michael Rodrigues to give you an example, I copied the PURE datasource groovy script (as I have to cache a cookie). It's the hostname verification that seems to be the issue and Viptela is a little weird in their self signed certs, having one of our engineers look at it and trying to figure out if we can sign it with the fqdn for the friendly name. It looks like the link you provided has an easier way to get the cookie data, so i'll look and rewrite this code below to follow those examples. import groovy.json.JsonSlurper; hostName = hostProps.get("system.hostname"); user = hostProps.get("viptela.user"); pass = hostProps.get("viptela.pass"); // init some stuff base_url = "https://" + hostName; slurper = new JsonSlurper() cookie = getSession(); // now run a command to get info from the server api_commmand = "/dataservice/alarms/count"; api_url = new URL(base_url + api_commmand); connection = api_url.openConnection(); connection.setRequestMethod("GET"); connection.setDoOutput(true); connection.setRequestProperty("Content-Type", "application/json"); connection.setRequestProperty("Cookie", cookie); arrayLines = slurper.parseText(connection.content.text); println "count:" + arrayLines.data.count[0]; println "cleared_count:" + arrayLines.data.cleared_count[0]; return(0); /* * getSession - get session cookie * * @return string cookie */ def getSession() { def cookie; api_commmand = "/j_security_check"; api_url = new URL(base_url + api_commmand); connection = api_url.openConnection(); connection.setRequestMethod("POST"); connection.setDoOutput(true); connection.setRequestProperty("Content-Type", "application/x-www-form-urlencoded"); // write out apitoken as a HTTP POST def out = new OutputStreamWriter(connection.getOutputStream()); out.write('j_username=' + user + '&j_password=' + pass); out.close(); // loop through http header fields for (int i = 1; (headerName = connection.getHeaderFieldKey(i)) != null; i++) { // is this the cookie field? if (headerName.equals("Set-Cookie")) { // yes. get the cookie data cookie = connection.getHeaderField(i); } } return(cookie); }
  18. Time Zone setting at the User level

    Hi all, This has been prioritized again for 2018. To provide a little background: Changing the way data is displayed in the UI is relatively easy, but once data is outside of LogicMonitor (i.e. alert messages, report content) it is no longer dynamic. To change content based on recipient is much more complex, and we don't have a good solution for this (yet). The last thing we want to do is create inconsistencies that further complicate the issue we're trying to solve, which is why this project was put on hold in the past. We know how important it is to support our customers with global resources, we just want to make sure we do it right. With that in mind, and to ensure things go smoothly this time around, we are considering approaching this in phases: 1. Ability to view data in the UI (dashboards, devices, alerts) in user-specific time zone. All configuration operations (scheduling SDT, escalation chains, report delivery, report content, etc) are still done in the account/global time zone (this would be explicitly indicated in the configuration window). Alert messages (i.e. ##START## token) also remain in the account/global time zone. 2a. Ability to configure events (SDT, escalation chains, collector upgrade, report delivery, etc) in user-specific time zone (or possibly user-specified time zone via time zone picker). Each configuration will record and display in the time zone it was set in. 2b. Ability to configure report content (SLA period, time range, etc) in user-specific time zone (or user-specified). Resulting report will be the same regardless of recipient. 3. Ability to receive alert messages and reports in recipient's time zone. We're interested to hear your feedback in terms of these phases as we work through the requirements. What is your highest priority? What percentage of your problems are solved by phase 1 alone? What are your biggest concerns? If alert messages are in a different time zone than your portal data, how does this affect your workflow? If you prefer, you can shoot me an email at ali.holmes@logicmonitor.com. -Ali
  19. I've created a test DS which polls current state (1-6) from devices and will alert if the delta is larger than 0. This works however the alert will clear automatically after x number of consecutive polls since it looks at the delta vs previous datapoint. Wondering if there's a better way to do this. here's the OID - .1.3.6.1.4.1.9.9.106.1.2.1.1.15.##WILDVALUE##
  20. Groovy - Ignore SSL Issue

    Hey @Tom Lasswell, the built-in Groovy Http library should work against hosts with self-signed certs: https://www.logicmonitor.com/support/terminology-syntax/scripting-support/access-a-website-from-groovy/ If you're using the Apache HTTP libraries, it is possible to skip/customize hostname verification, but if you just need to do some simple GETs and POSTs, the LM-provided one is the way to go.
  21. More Granular Role Access

    We found this past week it is far worse than we originally thought. Even within a portal for a single company, it is not possible to provide access to different teams by role to delete a device based on group membership, even though that group is marked for Manage within the user's role. Delete is blocked if the device also exists in some other group they do not have Manage on, but this is very common as devices are placed in some groups for alert routing, location binding and so forth -- providing the same access to those is tantamount to full admin access. When we brought this behavior to support we got the canned "it is supposed to work that way, not a bug" response I am so fond of. As a result, we end up either having to make everyone admins or we have to handle those tasks for them. IMO, this is a bug, not a desirable feature, but here we are...
  22. Another +2 Being able to do more with the reporting would be a plus
  23. Groovy - Ignore SSL Issue

    To all those out there doing groovy scripting. Looking for a way to ignore the SSL errors for self signed certificates where it doesn't match the hostname. I found some code snippets but the LM collector doesn't appear to like it too much by disabling SSL verification in a groovy script. Anyone out there run into this and have an idea on how to get around it? [02-21 11:13:19.608 EST] [MSG] [WARN] [script-running-2::script.running:Task:232203255:{url removed}:Viptela General_:script:1:7] [GroovyScriptExecutor.execute:79] Failed to execute the script with Invocation exception, CONTEXT=, EXCEPTION=CertificateException: No name matching {url removed} found com.logicmonitor.common.sse.utils.exception.ScriptExecutingFailedException: CertificateException: No name matching {url removed} found at com.logicmonitor.common.sse.utils.GroovyScriptHelper.execute(GroovyScriptHelper.java:186) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at com.logicmonitor.common.sse.executor.impl.GroovyScriptHelperWrapper.execute(GroovyScriptHelperWrapper.java:88) at com.logicmonitor.common.sse.executor.GroovyScriptExecutor.execute(GroovyScriptExecutor.java:70) at com.logicmonitor.common.sse.SSEScriptExecutor$ScriptExecutingTask.call(SSEScriptExecutor.java:263) at com.logicmonitor.common.sse.SSEScriptExecutor$ScriptExecutingTask.call(SSEScriptExecutor.java:242) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) at java.lang.Thread.run(Thread.java:748) Caused by: java.security.cert.CertificateException: No name matching {url removed} found at sun.security.util.HostnameChecker.matchDNS(HostnameChecker.java:221) at sun.security.util.HostnameChecker.match(HostnameChecker.java:95) at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:455) at sun.security.ssl.X509TrustManagerImpl.checkIdentity(X509TrustManagerImpl.java:436) at sun.security.ssl.X509TrustManagerImpl.checkTrusted(X509TrustManagerImpl.java:200) at sun.security.ssl.X509TrustManagerImpl.checkServerTrusted(X509TrustManagerImpl.java:124) at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1496) at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
  24. Meraki - NetFlow

    Hi Todd, Apologies for the delayed response - I've had some limited success (in the last couple weeks) with exporting Netflow data from a Meraki MX65 to the latest version of our collector. I don't know that we are 'officially' supporting, but I would encourage you to give it a shot and report back. We made some substantial enhancements to Netflow (in the UI as well as the backend) in our v.99 release. Cheers, Kerry
  25. Interface utilization percentages

    Hey Jeff, I believe @Andrey Kitsen answered your question over here: But let me know if you're still looking for any information here(!) Best, Kerry
  26. Please make it so that the Alert Tuning tab is not visible unless the user has manage device rights.
  1. Load more activity