Kurt Huffman

LogicMonitor Staff
  • Content Count

    7
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Kurt Huffman

  • Rank
    Member

Recent Profile Visitors

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

  1. Q and A Transcript Q: Can you please describe how a sub-account works? Our use case is entirely in AWS, and we have our customers set up with their own VPC. If I need to segregate their performance monitoring data is there an option to do so with a sub account? We will also have a collector in each customer VPC to monitor app servers as well as AWS resources like ELB/ALB/NLB and RDS. A: Will be answered in followup reply to this post Q: I am working on figuring out how to move us from the older 'snmp64-If_' datasource to the new, preferred 'SNMP_Netowork_Interfaces'.
  2. Thanks everyone for attending yesterday's LogicMonitor Basics Webinar! Here's the recording in case you missed it or would like to review it.
  3. Thanks for sharing. Your pre-request script looks good. But "[object Object]" in the request variables suggests that there is no data in the body of your request. POST requests require some body data, most often in JSON format. Here is example data for a POST to /sdt/sdts taken from https://www.logicmonitor.com/support/rest-api-developers-guide/v1/sdts/add-sdts/: {"sdtType":1,"type":"ServiceSDT","serviceId":47,"startDateTime":1469134752000,"endDateTime":1469144995000} In Postman, it would look like this: Confirm that your request contains properly formatted JSON data in t
  4. If GET works but POST does not, there may be something wrong with the request variables in the script. Make sure the code in your script generating the request variables (request_vars) matches the code in the example. You can add a line to the relevant section of the script to inspect the request variables in the Postman console: // If the request includes a payload, included it in the request variables var request_vars = (http_verb == 'GET'||http_verb == 'DELETE') ? http_verb + epoch + resource_path : http_verb + epoch + request.data + resource_path; console.log(request_vars) Aft
  5. LMv1 (token-based) authentication relies on a dynamically generated signature in the Authorization header. Current time is one of the inputs for generating the signature which is why the pre-request script must be run for each request. While we recommend using LMv1 authentication due to its greater security, basic authentication (user-password) is supported for v1 of our API and is easily implemented when dynamic generation of the Authorization header is not possible. You can find more information about authenticating with our API here: Using LogicMonitor's REST API
  6. Introduction Postman is widely used for interacting with various REST APIs such as LogicMonitor's. However, there is no out-of-the-box support for the LMv1 authentication method which we recommend as a best practice. This document describes how to configure Postman to use LMv1 authentication when interacting with our REST API. Overview Postman's pre-request script functionality provides the ability to generate the necessary Authorization header for LMv1 authentication. As the name suggests, the pre-request script runs immediately before the request is made to the API endpoint. We