When will Problem API v1 become unavailable?

[AntonioSousa]

Problem API v1 is officially deprecated. But, I just tested it now, and it still works. Does anyone know when it will become unavailable?

The reason I ask is that at the moment, it's not possible to get information that is available through v1, in v2. Such are the cases of "rankedEvents" and "rankedImpacts", namely around disk problems,  as referenced here https://community.dynatrace.com/t5/Dynatrace-product-ideas/Idea-Link-disk-entities-to-resource-probl... and here https://community.dynatrace.com/t5/Dynatrace-product-ideas/Idea-Include-disk-entity-tags-in-resource...

[ct_27]

Yes, Dynatrace, do tell.  And please this time, go down a checklist of existing functionality in V1 to ensure, at a minimum, the same functionality exists in v2 before you decommission.   More frequent than not every time DT releases something new we, the client, lose capabilities we've come to depend on over the years.

[wolfgang_beer · Accepted solution]

Dear @AntonioSousa and @ct_27 ,

No worries, there is a good overview of deprecated APIs listed here:

https://www.dynatrace.com/support/help/whats-new/release-notes/dynatrace-api/deprecated-apis

Where we explicitly distinguish between 'deprecation' and 'end-of-life'. Two different table columns are shown for those APIs.

Deprecation means that there is a newer API endpoint available that you should use when building a new integration and you should start to plan for migrating to the newer ones early enough.

EOL means that we set a definite date on when the API will be removed. The EOL date will be shown early in advance, at least months before the actual date.

Best greetings,

Wolfgang 

[wolfgang_beer]

@AntonioSousa to follow up on the referenced disk example above and the problem v1 api deprecation. Can you please give me an example of problem API v1 metainformation on disk alerts that you got in v1 that you are missing in the v2 ranked event evidences case?

[wolfgang_beer]

@AntonioSousa sorry, forget my last question, I already found it on your linked questions. its the disk name and id ressource fields. I will create a story for adding those in v2. Thanks for reporting.

Best greetings,

Wolfgang