v1/v2 API Sunset

Question

Did anyone else get a little sick at how many things are probably going to break in October?

Lewis_Beard · Accepted Answer

My biggest worry with this is that I inherited being our portal admin in a trial by fire, when the previous individual left. And internally to our company, things were set up before I came on to where different lines of business use the system for different things, and they have their own abilities to make collectors, write scripts that use the API, etc. And they have been using the portal for ages.So in a nutshell, I have no way that I know of to even be sure of what v1 or v2 scripts exist that...

David Bond · Answer

For those using .NET / C#, the LogicMonitor.Api nuget package (maintained by us at Panoramic Data Limited) has now been completely converted to use the V3 API. This is COMPLETELY FREE and licensed under MIT, so free (as in beer AND speech) for commercial use.

If you have any system integration requirements that you would like to make supportable, we also provide software development services at a reasonable price ;-)

Michael Raymond · Answer

@Stuart Weenig All great questions! Nothing that I’m aware of, but I can certainly relay this feedback.

LM User · Answer

@Michael Raymond is there a way we can run a report to show usage of v1, v2, and v3? One of the portal datasources? Something from Looker? Can that be built before the rug is yanked out from under us? That would give me something to work on because I can use the endpoint to search the audit log to find the id to figure out what the id is used for (assuming you’ve added descriptive descriptions to your tokens when they were generated).

Michael Raymond · Answer

I can see all the tokens in use but I dont think the logs show me who is actually using them.

Audit Logs will show the API access ID making the calls, but only if there is a change in the portal (adding/deleting/updating) or if the API call fails. If you know the ID, you can then find the associated user from Settings > Users & Roles > API Tokens.

Joe Williams · Answer

True, the ship will only start sinking in October. How long can I wait to refactor all my scripts to make sure they’re not using v2.

Luckily I wrote a crappy python function that works decently well. So I am able to just alter that portion of the script and control the returned data the way the rest of the script is expecting.

LM User · Answer

True, the ship will only start sinking in October. How long can I wait to refactor all my scripts to make sure they’re not using v2.

Shack · Answer

I’m reading it as support ends Oct 23, not that things are going to begin to suddenly stop working. https://www.logicmonitor.com/support/logicmonitorrest-api-v1-and-v2sunset

LM User · Answer

Not about features. About my automations that I’ll have to update to use v3. I wasn’t using v1, so I sort of wish they were sunsetting them one at a time. They left v1 around for years (a decade?). I understand getting rid of v1, there were security issues. And i understand wanting to get rid of v2, but i wish they weren’t both at the same time.

Joe Williams · Answer

So many automations I need to visit before then. I have a lot on my plate to prepare.

I also dislike very much the change in documentation. Don’t get me wrong, I love having a swagger again. But with the change from v1/v2 to v3, we are losing a lot of decent examples of how to do filtering and what not.

Even tho I think either v3 or some things just ignore filters now.

Michael Raymond · Answer

Which features from v1/v2 are you most concerned about?

1	SUYASH GAIKWAD
2	NA Nazmeen Ali
3	DK Deepak Kumar
4	PG Phillip Green
5	SS Sean Staats
6	AH Arno haverlach

1	SUYASH GAIKWAD
2	NA Nazmeen Ali
3	DK Deepak Kumar
4	PG Phillip Green
5	SS Sean Staats
6	AH Arno haverlach