Device DataSource Instance datapoint historical data using RestAPI v3

Make sure it works in postman first. That will tell you if the problem is your request or your script.

@Cole McDonald I personally use Insomnia.rest. It has a local electron app that I use.

While using Curl or Invoke-RestMethod is quick and easy. Sometimes it is just easier to click Go and see the structured data right there.

With the move to Bearer Token for auth, you don’t need a prescript any longer. Which makes using tools like Postman or Insomnia that much easier.

Meh, tradeoffs everywhere. Having postman sync to the cloud makes it so that i never have to start over with postman. All my work is always there, even if i change PCs.

Import collection from URL: https://www.logicmonitor.com/swagger-ui-master/api-v3/dist/swagger.json makes it so that all the documented API calls are available. Set some authentication defaults with bearer tokens on the collection and some collection variables and you should be good to go.

Being able to separate your script from the API call makes a big difference when troubleshooting. Also allows you to very quickly tune your API call to get only what you need.

I assume you’ve seen this:

Got it to cooperate using powershell… The filters I was adding pass through two functions I wrote.. at some point, it was inserting the ‘?’ dividing the URL from the queries.  Fixed that… the datapoint names are CaSe SeNsItIvE.  When accessing a single instance, there are no .item objects, so I had to catch for quantity of returns.

I’m ready to move forward with some deeper predictive metrics now :)

Confirmed absent thorugh the support team

I’m successfully reaching the timeseries data from a different dataSource on the same device then using that data to calculate predictive metrics.  I still have to add a couple of calculations, but this is the basic goal I’m shooting for.

Need to optimize the code as well, as it’s currently several API calls happening for each device and I don’t want it to eat the whole TCP ephemeral stack.

I’ve never been able to get postman to work right with LM’s API… even while taking the LMCD :)

I’ve just used my own code for it as a result.

Once I get these grabs figured out, I’m going to start building longer term predictive metrics.  Things like 3 month, randomly sampled standard deviations to determine steady or spiky used volume growth.  This will unlock growth metrics like “Days Until Full” and “Desired Capacity” to determine how best to address a volume that is filling up… fix some SQL backup that didn’t complete and delete the previous one… a single users storing a copy of GoT Red Wedding episode video file (that sounds awfully specific Cole)… or nice steady growth that can just be expanded to let it meet a quarter’s growth and allow an account manager to spend some quality time with the clients who don’t want as much interaction, so we can find ways to determine if their technology needs may be changing or suggest other optimizaitons/solutions where needed.

They are definitely stored in your account in the cloud. I switched PCs and when i logged into postman, my creds were saved there.