Clement Law

  • Content Count

  • Joined

  • Last visited

  • Days Won


Community Reputation

3 Neutral

About Clement Law

  • Rank
    Community Whiz Kid

Recent Profile Visitors

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

  1. Hello, The title says it all really. I cloned a custom JDBC datasource which already had credentials filled in, but the credentials weren't preserved. I wasn't told about this and had to go digging in the collector logs: [06-03 07:19:34.455 UTC] [MSG] [DEBUG] [pool-29-thread-29::collector.jdbc:Task:155185:db-server.some.where:PostgresServer-5432:jdbc:166] [JDBCTask._collect:223] Create JDBC connection, CONTEXT=timeout=10s, url=jdbc:postgresql://db-server.some.where:5432/, username=, passwordLength=0 [06-03 07:19:34.463 UTC] [MSG] [ERROR] [pool-29-thread-29::collector.jdbc:Task:155185:db-server.some.where:PostgresServer-5432:jdbc:166] [JDBCTask._collect:231] Failed to create JDBC connection, CONTEXT=timeout=10s, url=jdbc:postgresql://db-server.some.where:5432/, username=, passwordLength=0, EXCEPTION=FATAL: no PostgreSQL user name specified in startup packet org.postgresql.util.PSQLException: FATAL: no PostgreSQL user name specified in startup packet at org.postgresql.Driver$ConnectThread.getResult( at org.postgresql.Driver.connect( at java.sql.DriverManager.getConnection( at java.sql.DriverManager.getConnection( at com.santaba.agent.collector3.jdbc.JDBCTask._collect( at com.santaba.agent.collector3.DataCollectingTask.execute( at at java.util.concurrent.ThreadPoolExecutor.runWorker( at java.util.concurrent.ThreadPoolExecutor$ at I've mentioned this already, but it would be pretty useful to have the above lines in a popup window or error log right in the web UI, rather than digging into the collector logs.
  2. Hello, At the moment, when you view a graph and toggle different parts of the legend, on auto-refresh or date interval change, these selections aren't preserved. This is really annoying when you're trying to do some kind of investigation that lasts quite a long time. Is there a way of preserving which legends you've toggled between refreshes? Thanks.
  3. This is great news. From my part, I would like to see 1. Automatic network topology discovery, i.e., Logicmonitor would automatically scan the network and discover how devices are connected together and with what protocols. The information is partly there by just running nmap between every host. 2. Decent visualisation of the network topology, where you can zoom in on different parts of the network and navigate to a device's datssource easily 3. Decent management from the network topology visualisation, where you can click/search servers and say things like "everything connected to this machine by one node is now going into scheduled down time". I'm thinking regular expression matching would be really powerful in combination with this.
  4. Hello, I thought that this would be an obvious feature, but anyway... Entering an OID for an SNMP datasource gives me only three ways of interpreting output - none of which are to treat it like JSON. Can this be added as a feature? Thanks.
  5. Yes, I have. My point is, I don't think we should need to dig around in the logs for a simple error. The collector knows the error and it should just be bubbled up to the UI in a pop-up (for example).
  6. At the moment, there's a single datasource that's tied to the automatic discovery of AWS Services, and further, there are generic alerts on all these services. I just think this is too general - there should be individual datasources for each AWS Account so that you can have custom alerts on custom queues. Sometimes you don't care that a queue is empty (for example). Anyway, I want to add these subset of queues to a group. At the moment, I have to add the entire dev account and this just feels like overkill.
  7. Currently, there's no clear cut way of debugging the creation of datasources. Let me explain: 1. You create a datasource that scrapes a webpage for some JSON 2. You attach the datasource to a device 3. For some reason, the device doesn't show your datasource after refresh 4. What is going on? The answer to bullet point 4 is pretty frustrating. There's no feedback as to what is going on. For my example, it was a case of having a collector on the wrong VLAN, causing it not to be able to access the web page API, but I came to this conclusion after lots of head thumping. All there needs to be is some kind of display that shows what the error message was. Presumably, an error was thrown somewhere in the collector, but that isn't shown in the GUI. I don't think the answer to this should be to use the debug console, or to look at the logs of the collector. I think they should clear and present on the GUI. For someone who comes from a development background, I find this sort of clicking around and watching spinning gifs really annoying. I'd just like to see some more feedback for what is going on. Thanks.
  8. Hello, At the moment, when you've added an AWS Account, it will show all the services you've asked for (e.g., all SQS queues). Is it possible to have a feature where you can select a subset of these queues after they are discovered? Clearly they are stored somewhere (via a datapoint's metric path:, but there doesn't seem to be a way of changing them. Thanks.
  9. Hello, At the moment, the documentation for adding an AWS Datasource almost seems to imply that you can filter any type of service (be it EC2, S3, SQS etc) by name using the tag name/value system, but in actuality, only filters things that literally support the tag feature. I'm asking for a simple addition to the AWS Datasource so that you can filter, for example, SQS by some regex, e.g.: regex name = foo, regex value = *foo* Thereby causing the autodiscovery to only show *foo* SQS queues. This is a bit of deal breaker for people who have many SQS queues, but where some of them are just test queues which don't need to be monitored. Thanks.
  10. You have no idea how restrictive not having this feature is. How can someone hope to properly monitor their systems when the monitor has no proper hierarchical dependencies?