John Dear

  • Posts

  • Joined

  • Last visited

  • Days Won



7 Neutral

1 Follower

About John Dear

  • Rank

Recent Profile Visitors

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

  1. I agree. The old UI is so much more intuitive, straight-forward, and easy navigation. I hope Lomo is taking this comment as constructive feedback. Thanks,John
  2. I wish to avoid alerts during multiple times of the day and night because of multiple daily maintenance windows on certain resources. There is the Alert Threshold Wizard that enables me to set the many time ranges we wish alerting enabled. But this is per Datapoint. I have multiple Datapoints within all my impacted Datasources that needs the same schedule. Is there a way to easily replicate the schedule without having to enter the multiple time ranges on each Datapoint? If we need to change the schedule, then I would have to modify each Datapoint individually on all affected Datasources to keep them in synch. I can use SDT to avoid notifications, but that throws an Alert regardless. Else, it would be nice to have a Monitoring schedule per Datasource and host. Thanks- John
  3. It would be good to add this feature. My current workaround is to write a VBSript using the FileSystemObject. It is working for me so far.
  4. I am very interested in this feature as well. Instead of having to manually view the Show associated hosts for a given datasource, it would be so convenient for us to simply see them as members of dynamic groups. Logicmonitor- is this a feature you would consider providing? I see that this original posting is over 20 months old with no other comments.
  5. Sometimes we would need to see datapoints expressed in different units, or summation of datapoint values. As a workaround, I am having to create these custom datapoints in datasources in order to use in the report configuration. Also, allow for the selection to use stacked and area charts.
  6. Also, if the voice alert goes to voice mail, the first portions of the voice alert is chopped, likely because it begins to play before the voice mail begins to record it. I tried adding buffer words at the beginning of the voice template, but it is annoying to our voice alert recipients to have to hear this fluff. We wish to use different custom voice templates for different alerting situations- how do we do that? Is the custom alert template configured in a Datapoint only used for email?
  7. Allow the admin the ability to simply disable/re-enable selected alert rules. This would allow us to assess the impact and saves us from having to remove/re-add the rule or reassign the priority to a high number. We can then check the impact by using \'\'Show alert routing\'\'. We have close to 100 rules (and growing) and this can help determine correct rule placement/settings, especially the way the rules are currently evaluated by Lomo. Another thing that would be helpful is adding a comment field for each rule. thanks.
  8. In addition to scheduled reports, we would be excited to see the feature to alert based on selected Access Log event, such as datasource updates, user role updates, agent config updates, Debug facility usage, etc. These and other events can be time-critical and any mistakes made by an administrator should be corrected asap. So having the ability to configure alerts based on specific activities would be very helpful. I see that this Feature Request is marked as Planned- when do we expect to see this? Thank you.
  9. Would it be possible for Lomo to add \'\'Month\'\' selection to the time-based escalation sub-chain selection criteria? This way, we can setup alert recipients on rotation basis by month. Or is there a better way to do this?
  10. In addition to controlling the speed of text-to-speech playback, we would need to ability to flag certain words such as hostname to be spoken one character at a time. Our hostnames are a series of alpha and numeric characters that do not make any sense if spoken like a word.
  11. Steve, that is a good idea. If I add the Latency Session Deviation to, for example, Latency Last Recorded, that would pretty much cover any monitoring gaps and any missed spikes in latency. Although the latency values will be inflated, it would show the worst possible case per ICA session. Well consider this approach further. Thanks.
  12. We have a need to monitor external websites using our internal Lomo collectors, not using the monitoring in the Services tab. We need to use our internal collectors to best test from the perspective of our users. When monitoring external websites from our internal collectors, it is preferable that the monitoring traffic goes through our proxy. This best mimics the path our users/services take and would be the most accurate way to monitor their experience. If there is a proxy failure, the monitor would catch that. I found out that the collectors do not work this way. If I set the proxy.enable=true in the agent.conf, only the SSL communications with Lomo occurs through our proxy. Any external website monitoring still goes direct, bypassing our proxy. Is there anyone able to monitor external website from their internal collectors and going through their proxy? How do you do it? Can using a script do what I need? Thanks,
  13. We have a need to collect Citrix ICA Latency data every 15 seconds. The most frequent interval I see is 1 minute. Is there a workaround or trick to collect more frequently? We may have an ICA Latency issue and want to avoid missing any spikes that can occur in between polls. If possible, can Lomo even display this data properly? I am looking at WMI- Win32_PerfRawData_CitrixICA_ICASession, the property is LatencyLastRecorded. If forum members have any other great ideas regarding ICA Latency to share, we are interested to hear them. Thanks, John.
  14. Create an collector/agent that runs on iDevices. This agent would monitor iDevice metrics such as CPU, Mem, Storage, Cellular state, wifi state, battery state, signal strength, etc. The agent would report data back to Lomo so we can see our iDevices on our portal. Thanks.