CAPI to Pattern migration for Cloud discovery

[Lukasz18]

Currently, we are using CAPI Cloud Discovery for Azure. It works fine, but since there is another way for Cloud Discovery to use patterns, I have some questions.

What is the reason to move Cloud Discovery from CAPI to Pattern?

This is some kind of approach from ServiceNow?

What is the advantage of it?

Regards

Lukasz K.

[Ram Devanathan1 · Accepted solution]

CAPI Discovery is legacy, our preferred discovery approach which we are taking forward is Patterns. so this migration (needed in case of AWS and Azure discovery) is intended to move over the customers to the current tech. with patterns we make regular (monthly) releases adding quality fixes and new patterns - you get all new features only with this.

However, this is not changing CPG's CAPI actions for operations - all this is only about the CAPI discovery.

[Mohit Kaushik]

Hi @Ram Devanathan ,

We are also planning to move from CAPI to pattern based discovery for Azure and I have few questions regarding that:

1. Does this require any other plugin (paid) apart from Discovery plugin which we already have.

2. How will it affect the discovery? Will there be any issues to our ongoing discovery due to this migration.

3. I can see the steps present in the article mentioned on SN support site, but before moving forward I would like to know that this transition is safe and will not affect our ongoing disocvery.

It will be great if you can provide the answers to these questions. Thanks in advance.

Regards,

Mohit Kaushik

[Ram Devanathan1]

no additional licensing needed if you have discovery entitlement activated.

it won't affect discovery. it is a like-for-like replacement, refactoring of old tech (CAPI) to new tech (patterns).

it is of course safe - but test it out on sub-prod / lower instances and on prod clones, before you go to prod.

[Mohit Kaushik]

Thanks Ram! for the quick response.