David Medina

LogicMonitor Staff
  • Content Count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About David Medina

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Rharrelson, Sorry to hear you are having difficulty getting Syslog messages to work with your LogicMonitor account. Can you let me know what your case number is which you recently worked on this with our Support team? I can take a look at the case notes and get back to you via the ticket to see if there is anything we might have missed. Thanks.
  2. Hello Everyone, I just saw this and wanted to confirm what Mike was referring to. If I have a datapoint, such as CPUBusyPercent, that has an "Alert trigger interval (consecutive polls)" set to 4 AND I set "If there is no data for this datapoint:" to trigger an alert, the No Data alert would trigger after 4 consecutive polls, just as the regular thresholds would that are set on the datapoint. If you wanted to extend the time to trigger a No Data alert, or have a specific amount of consecutive polls for No Data, you can always set the No Data alert on a datapoint that has no threshold, adjust the "Alert trigger interval (consecutive polls)" to what you deem appropriate, and it will respect the amount of consecutive polls set before triggering a No Data alert. For the most part this can be any datapoint you choose on the datasource, as usually when you are getting No Data, it is not just that one specific datapoint, it is usually the whole protocol not responding (WMI, SNMP, JDBC, etc.). Hope that clears this up, let us know if you have any other questions related to this.
  3. Dave, If you want to be able to see the instance description names on a graph you would want to use the token ##DSIDESCRIPTION##. Here is my device and you can see my interfaces have a Descriptions of Description1, Description2, and Description3. When you are building your lines for your Custom Graph Widget, the default tokens are set to ##HOSTNAME##_##DATASOURCENAME##_##INSTANCE##. Here you will see that I changed the line definition to ##INSTANCE##_##DSIDESCRIPTION##, with ##DSIDESCRIPTION## being the token used to add the description name for the instance. Now your graphs will include the interface instance name and its description. You can learn more about the tokens available to use in this help document. https://www.logicmonitor.com/support/settings/logicmodules/tokens-available-in-datasource-alert-messages/ If the datasource used does not provide an automatic way to add descriptions, you can manually add instance description names by going to the device, clicking on the Datasource, clicking on the Instances tab, finding your instance, click the Manage icon, then once the manage instance window is open you can edit the description. Make sure to uncheck the "Allow Active Discovery to overwrite the description." option. More can be found on updating instances below. https://www.logicmonitor.com/support/devices/device-datasources-instances/instances-tab/#Editing-Instance-Name-Wildcard-Description-amp-Gro
  4. Hello, LogicMonitor is continuously working on improving our infrastructure resiliency. As a step in that direction, LogicMonitor will be changing the IP address your account endpoint resolves to. As a reminder, your account endpoint is used when accessing your account via a web browser as well as by the LogicMonitor collectors in your account in order to report metrics data back to our data centers. In normal operations your LogicMonitor account is homed to a single data center /24 IP network address block. Currently all customer endpoints within their /24 block resolve to a X.X.X.192 address. The network block for your account will not change, but the specific IP address in this network range will. Furthermore, the IP address will become dynamic, rotating between a number of addresses within the block. This change will be transparent, requiring no manual changes on your behalf. However, if you have IP restrictions on firewall or proxy devices that do not incorporate the entire network block for your data center, collectors may become blocked from reporting data, resulting in collector down notifications and a halt in data collection from that collector. As a reminder, if you do have IP address restrictions in place, it is best practice to incorporate all LogicMonitor public IP addresses & DNS names into your firewall or proxy in order to accommodate all possible disaster recovery scenarios. We will start the migration towards the end of November. You will receive a one week notification beforehand, as well as another notification on the day of the migration. If you have any questions please feel free to contact customer support via the normal channels.
  5. David, Thank you for the feedback. We currently have a product improvement ticket in for this and hope to offer it in the future. Thanks for sharing your interest. Until then, you can always use the HTTP_Page datasource, that provides response times and Status of any webpage you specify.
  6. Hello, Are you talking about the options listed under Alert Settings? Those would be configured if you wanted to use a custom or alternative alerting method, or relaying the alerts to some type of ticketing board. If you are not, then you do not need to set them. These settings are not based on whether you are using a trial account or not. If you need help setting up alert configurations please click the chat with an engineer button, or submit a support ticket email. You can find the email link below. Thanks. https://support.logicmonitor.com/customer/portal/emails/new