Nam Ngo

Members
  • Content Count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Nam Ngo

  • Rank
    Community Member
  1. In the current UI, I couldn’t see where we could export all of the datasources. However, we have previously had the functionality to bulk export (for purposes of backup) of all the datasources in the old UI. The documentation discusses exporting a single datasource: http://help.logicmonitor.com/using/datasource/managing-datasources/ But doesn’t indicate any way to bulk export all of the datasources (even if under a specific node). Is there a way to do this in the new UI?
  2. Currently, we\'ve been trying to get a listing of all DataSources for various automated task logic. However, there is a very limited way to get various pieces of information from the API. For example: In order to get a list of all DataSources currently, we have to export all the datasources through the LM GUI, and then we had to create a special XML parser for extracting the DataSource names (and subsequently filtering out the ones we are more concerned about), and then running that list through our desired custom automated logic. But it would be much more convenient to just do it through the API. We also can\'t easily get a list of Event Sources and Service Sources. This feature suggestion is presented in hopes that something like this can be done, and if anyone else has other API woes to suggest it here so that there is 1-stop API shop for all the API changes. The specific ones I propose are: - return a JSON list of DataSources - return a JSON list of Event Sources - return a JSON list of Service Sources - modify Event Sources - modify Service Sources - robustness in modifying some LM entities (sometimes updating particular entities when not listing all defined fields will overwrite the whole entity with an empty one except for the supplied fields you intended to change; in this case, you would lose any/everything unless you listed all populated fields; I believe this happened with hosts using the \'\'updateHost\'\' API call) - API documentation updates: https://support.logicmonitor.com/entries/28053460-API-documentation-corrections-suggestions - API for Services: https://support.logicmonitor.com/entries/22009145-Add-Services-API-documentation - Include a single \'\'master ID\'\' for ease of acking Alerts: https://support.logicmonitor.com/entries/26105929-Send-the-actual-alertID-back-via-the-alert-message-for-API-usage - Better Alert filtering through the API: https://support.logicmonitor.com/entries/27528810-filtering-out-alerts-from-api-call So... anybody have any other suggestions?
  3. Due to difficulties that caused me to propose: https://support.logicmonitor.com/entries/35788800-JDBC-DataSource-Active-Discovery-SQL-Statement-Parameters-multiple-columns We subsequently had issues with trying to format the DataPoint's Alert's customized Body Templates the way we want. As we discovered: - we can include any tokens in there (including WILDVALUE): http://help.logicmonitor.com/using/datasource/creating-datasources/defining-datapoints/tokens-available-in-alert-messages/ - there are no functions available to be used in that box (especially those of interest to us were advanced string parsing) - the values that come back from a concatenated JDBC SQL Query can be put in entirely, but not easily parsed to create a "Support-friendly" format - no possible way to pass in the result of the actual JDBC collector attributes query into the DataPoint Alert Body Template, so we couldn't work around by providing a different query - even when using ##VALUE##, it will always be the Alert's innate value and NOT any other value that comes back (example: writing a Groovy Script to return a different value in a Complex Datapoint will not replace ##VALUE## with its value, so we couldn't even work around it with this; as per discussion with LM engineering/support) - Hardcoding a message would only limit the usefulness of the alert and the result would only slow down debugging/investigation So, this is just a proposal for some easier way for custom data to be passed in to the alert body template.
  4. I\'d like to request a way to more easily select more columns in the JDBC DataSource Active Discovery SQL Statement Parameters and be able to use them. Somehow, values that come back in the ##WILDVALUE##, we want to be able to have that query come back with different columns that we can use in the actual JDBC query or DataPoint Body Template (however we would use it ##WILDVALUE.COL1## or ##WILDVALUE1## or whatever convention makes sense). Currently the way we want these WILDVALUE instances is not sufficient for our needs, and we have to set a SQL variable at the top and write really contrived string parsing in the query to get the values we want (and initially writing our Active Directory SQL Statement Parameters query in a way that returns everything in one column delimited by some character).
  5. I was reading over http://help.logicmonitor.com/developers-guide/manage-alerts/ and I only noticed two web service method calls: getAlertsconfirmAlertsI was wondering if there was a way to alter the existing values (such as \'\'ackedBy\'\') or add other fields (a custom \'\'[some internal ID]\'\')? If not, I am also wondering if there is a way to modify the ackComment value without actually acknowledging it.