Forrest Evans - LM

LogicMonitor Staff
  • Content Count

    32
  • Joined

  • Last visited

Everything posted by Forrest Evans - LM

  1. Forrest Evans - LM

    1 to Many fail-over load balancing Feature request

    Hi Akash, We are close to releasing a new feature that will include functionality to spread fail-over of devices among multiple collectors. ~Forrest
  2. Forrest Evans - LM

    Integration with Atlassian Statuspage

    Hi DarrylG, I've added this as a feedback ticket in our feature request queue. I believe a few customers might have done this previously. If I can find details I'll reshare them here. ~Forrest
  3. Forrest Evans - LM

    LogicMonitor CMDB integration

    Our official ServiceNow CMDB Integration is now available. https://www.logicmonitor.com/servicenow-cmdb/
  4. Hi Joe, We have an active project to address this issue which will allow RBAC permissions to be applied to the User Listing. ~Forrest
  5. Forrest Evans - LM

    ServiceNow Runbooks

    Hi Samuel, Sending specific alerts from LogicMonitor to ServiceNow is handled through our Alert Rule / Escalation Chains. https://www.logicmonitor.com/support/settings/alert-settings/escalation-chains/ https://www.logicmonitor.com/support/settings/alert-settings/alert-rules/ ~Forrest
  6. Forrest Evans - LM

    Better slack integration?

    Hey Joe, This is actually on our Integrations Road Map for 2019. Look for a much richer integration later this year that will include actions like ACK/SDT and a chatbot to get information back from LogicMonitor. ~Forrest
  7. Forrest Evans - LM

    integration data transformation via Groovy

    Hey Mark, For the PagerDuty situation and their V2 of the API we are aware of this and working with PagerDuty on some updates to our Integration. I hear you on the on the bigger picture item though and will enter a feedback ticket in our system to track the request. ~Forrest
  8. Forrest Evans - LM

    Add device to Collector with least devices in rest api

    Hi Paul, We are actively working on an enhancement to LogicMonitor to support Load Balanced Collectors. One of the key features is that when adding a device you can pick a Collector Group instead of an individual collector. More to come in the next month or two! ~Forrest
  9. Forrest Evans - LM

    Snapshot 'Age'

    Hi Will, For #2, on the latest version of that datasource there is a field for snapshot_age_hours, which, by default doesn't have an alert threshold but if applied could alert if a particular snapshot is over a certain age. #1 is a bit more tricky since it would require an aggregate measure across multiple instances. It could be done with a scripted datasource but but the good news is we are working on an upcoming feature that will be a much better way to solve this. More to come when we are ready to release. ~Forrest
  10. Forrest Evans - LM

    Radical Suggestion for Web Sites

    Hi Mosh, Not quite as radical as you think!! We've considered this in the past and the workflow and UI/UX benefits are definitely there. We are working on 2019 roadmap planning and it's on the list to be discussed. ~Forrest
  11. Forrest Evans - LM

    Log Streaming Feature Request

    Hi Horace, At this time LogicMonitor supports EventSources to alert on your log entries, but sounds like you are looking for something more in depth. I've sent you a direct message to try and connect and discuss further. ~Forrest
  12. Forrest Evans - LM

    integration association restriction

    Hi Mark, We are actively discussing options and ideas around this internally and hope to address it in the next calendar year. ~Forrest
  13. Forrest Evans - LM

    Add Mutiple data points at a time....not one by one

    I've seen customers export the datasource XML file and programmatically generate the <datapoint> node for all the new data points you want to add. You can then import the updated XML file and the datasource is updated with all the new data points. ~Forrest
  14. Forrest Evans - LM

    Allow Automated Reports to Generate Regardless of User

    Hi Anthony, I've submitted a ticket to look into this for you. ~Forrest
  15. Forrest Evans - LM

    SDT EventSources

    I'll enter a ticket and get this looked at.
  16. Forrest Evans - LM

    Prevent Alert Widget Data Refresh During Column Resize

    Hey @Mosh. This will be fixed in the upcoming v110 release.
  17. Forrest Evans - LM

    Ability to stream StatsD like stats/metrics to LM

    The LogicMonitor Product team is actively looking for feedback from customers on this. If you are interested in talking with a Product Manager about your use cases for StatsD or any other Push Metric needs please reply here and we can setup a time to talk. ~Forrest
  18. Forrest Evans - LM

    Dashboard local times

    For everyone following this thread, User Based Timezones was released with version 108. You can read more about it here: https://www.logicmonitor.com/release-notes/v-108-release-notes/ ~Forrest
  19. Forrest Evans - LM

    Timezone per user account

    For everyone following this thread, User Based Timezones was released with version 108. You can read more about it here: https://www.logicmonitor.com/release-notes/v-108-release-notes/ ~Forrest
  20. Forrest Evans - LM

    Add timezone column listview in Users view

    Hey Mosh, Good idea. I've added a ticket to track your request. Don't forget that the feedback submission from inside your LM portal comes straight to the Product team as a ticket too! ~Forrest
  21. Forrest Evans - LM

    Ability to apply retroative SDT-like windows to adjust SLA numbers

    Hey All, We have had the request for retroactive SDT in the past. LogicMonitor doesn't plan on adding this feature because allowing retroactive entries kinda takes the S out of SDT. The intention is to have those entires scheduled ahead of time so that alerts are suppressed and SLA numbers are accurate based on previously scheduled downtime entries. We will look into iqmsjoel's comment about mid-month data vs. data that is missing but was actually polled for. ~Forrest
  22. Forrest Evans - LM

    SDT EventSources

    Hi Joe, This is possible today if you navigate to the Syslog Event source under the device and use the SDT tab and add a new scheduled downtime entry. https://www.logicmonitor.com/support/devices/devices-page-overview/scheduled-down-time-sdt-tab/ ~Forrest
  23. Forrest Evans - LM

    How can I hide the Debug option?

    This is scheduled to be released in version 104. (Mid-May) ~Forrest
  24. Forrest Evans - LM

    Retiring TLS 1.0 Support

    Your data and infrastructure security is LogicMonitor’s top priority. To ensure the most secure environment possible, we are updating the TLS protocol handling for LogicMonitor accounts to align with current best-practices for high security environments. On April 19, 2018, LogicMonitor will be retiring support for an older TLS cipher suite as well as support for the 1.0 version of the TLS protocol. While we expect this change to have minimal impact, there is a possibility this change would affect access to your account in the following ways: Web Browsers Support for TLS 1.1 and 1.2 protocols have been available in major web browsers for years, including: Google Chrome > v.21 (2013), Mozilla Firefox > v.26 (2013), Microsoft Internet Explorer > v10 (2013), Microsoft Edge (all versions), Apple Safari > v.6 (2014) Those using older versions of MSIE (< v.11) will need to enable support for TLS 1.1 by following these instructions. API Access If you have written scripts or programs to interface with our API, they will have to support TLS v1.1 and above. Many languages are dependent upon OpenSSL which has supported TLS 1.1 since 2012. Collectors Customer collectors have supported TLS 1.1 since 2015 and should have automatically upgraded to the Minimum Required Collector (24.002) as of June 29, 2017. If you have collectors that have not been automatically upgraded to this version, please contact Customer Support. Proxies If your Collectors or Web Browsers have been configured to use a network proxy, you will need to ensure the proxy software also supports TLS 1.1 or 1.2 protocols. Important Next Steps Ensure users of your LogicMonitor portal are using current browsers Verify scripts utilizing the REST API are capable of TLS 1.1 at a minimum Confirm all collectors are at the Minimum Required version (24.002) Confirm that any Network Proxy used by your collectors supports TLS 1.1 or 1.2 If there are any questions, please feel free to reach out to our Support team through your LogicMonitor portal or respond to this email.
  25. Forrest Evans - LM

    Custom Alert Message - Auto Fill

    Thanks for the feedback and good idea Patrick. When we look at revamping the Alert Messaging capabilities we'll definitely take this into considerations. ~Forrest