• Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

6 Neutral

About Keimond

  • Rank

Recent Profile Visitors

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

  1. Thanks I have reached out to support for their suggestions!
  2. Has anyone enabled SSL on JMX and gotten it to work ? Following directions on Tomcat | LogicMonitor, I can make it work with authentication but "" If I set that to true I'm getting "Fail to get the jmx result - java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is: Received fatal alert: handshake_failure" I have also tried to pass "" and "" with no luck. SSL to my web page (using the same keystore) works fin
  3. Sorry I discovered one more item while trying to set this up for a customer. So I added a complex data point for CPU Wait Percentage... then I went back to the device I needed the threshold on and set a custom threshold there... however, I can't set a custom consecutive polls there.. this should be allowed. For example, Maybe on our DB servers we want to be alerted if the CPU has been over 80% for 10 minutes but on web servers we want to be alerted if the CPU has been over 75% for 15 minutes. The only way I could do that today is to create a new data source which isn't a huge deal brea
  4. I have a request to alert on > 40 on cpu wait after 15 minutes... my polling is at the default one minute and I'd like to leave it at that, but consecutive polls is a drop down menu and let's me select 10 then 20... which means I can only alert at 11 or 19 minutes.. can this field allow a person to set a custom number please ?
  5. Example, we have a graph showing the current number of connected users.. I have another datapoint that derives those values so I can see the number of new users that connected between polls. I want to see a bar graph over x time ( like 24 hours ) and see the total number of new connections per x time ( like 1 hour ) Here's a decent example.. Or maybe I want to stack the graph with other datapoints showing connected users per protocol or something... Thanks! David Klein
  6. Sorry @GraphTheWorld, not ignoring you! My priorities in the company have been shifted elsewhere right now and D42 isn't one of them. I'll come back and elaborate more later.. (I've also asked the rest of my team to give their input on what they'd like to see) At most, our top goal was, whatever is in Device42 labeled as production should be in LogicMonitor (unless monitoring is set to off) .. or/and the opposite.. whatever is in LogicMonitor should be in Device42.
  7. @Sarah Terry Thank you !!! That helps out a lot, that answer doesn't seem to be very straight forward for the common user. Especially when an alert is cleared. The user has to know then if they want to go see history on an instance that when they go to the alerts tab on that instance, they also have to change cleared to all to see past alerts then click on history. -- which is why a tab right next to alerts might be nice, or a visible "history" button under the alerts tab so that the common user can easily have a link to see history. At least for now it's just a matter of training everyone
  8. hey @Sarah Terry I was just search for "history" and ran across this.. I was just looking at a resource and thinking boy it would be nice if right next to the Alerts tab was a History tab (or maybe it could just show on the same Alerts tab as old alerts... basically a quick way to see has this instance alerted before and when ? Which would be great for the normal user!
  9. @David Lee Thank you for this, I might have to play around with implementing this for a few of my DS's... Along with conditional formatting I would love to see the ability to say: if threshold is < X or > than Y if threshold is > X and < Y if threshold for DP1 is < than X AND threshold for DP2 is < than Y. (right now I use a comlex datapoint and put my thresholds in there.. if dp1 is lower than X and dp2 is lower than Y return a 0 or 1 based on true/false statements... its ugly and confusing )
  10. Server1 Server2 uy1 - ab1 - uy1 - ab1 - ar1 - mn1 - ar1 - mn1 - my1 - bg2 - my1 - bg2 - All instances return back a value for a query time (from Server1/2 to dns1/2/3/ whichever is in the name..) All instances return back a value of 0 1 or 2 based on if they were able to query both servers.. so for example, if uy1 can
  11. Hello, we would love the ability to have the cluster alert give us a list of instance names that have triggered the cluster alert. Another is filtering based off of an instance name. Example, let's say I have 3 devices that all have 3 instances named something like Device1 --- Device2 --- Device3 a1-dns1.blah d1-dns1.blah g2-dns1.blah b6-dns2.blah e2-dns2.blah h1-dns2.blah c1-dns3.blah f1-dns3.blah i2-dns3.blah While you can see all the instances are a different name, the last part of the name is still common with some of the others (dns1.blah, dns2.blah, dns3
  12. Just another random note lol.. I read YAML better so I'm always using name: test111 parentId: 111 appliesTo: startsWith("system.displayname","Prod") translates to { "name": "test111", "parentId": 111, "appliesTo": "startsWith(\"system.displayname\",\"Prod\")" } *shrug*
  13. Please include "Grouping" too We just got flooded with a bunch of pages last night because a server went down which caused instances from several datasources to go down.. OUCH! It would be great to group instances so that if one goes down.. that group pages and says hey something is wrong with this server.. then we can log in and go check.. rather than getting flooded by everything. Same idea with grouping of servers... I could call a group "HKG POP"... a server goes down that I have put in that group.. or any instance alerts a critical.. just that one group pages and says hey a critcal
  14. Definitely a step in the right direction for LM.. now we just need to be able to use this for stuff that goes down but doesn't have an SDT lol... I assume the same logic can be applied but that involves deeper changes than data sources I may have missed it but if it hasn't been requested, besides host dependencies, we should have service dependencies. There should also be multiple dependencies. * Host 03 depends on Host01 * Host 04 depends on Host01 AND/OR Host02 -- (and) don't alert Host04(and services) if Host01 and/or Host02 are down. -- ( or) don't alert on Host04 if j
  15. long post.. I'm posting this more as an informational; this is what we did to collect everything through snmp rather than open up any ports like ssh... If you have ideas on making it better I'm all ears! Nothing fancy.. I modified the code from the real world example that snmp pass_persist gives on their page... the main script loads stuff from a YAML config file then calls each python module, passing the snmp pass_persist object (pp) and config object over to them. The modules will run a quick test to see if they actually need to run... for example if the machine doesn't have DNS, then t