Best practice for applications in dev and staging environments

Sangiliraja Pal
Kilo Expert

‎02-20-2022 10:59 PM

Hi,

We are performing manual import of application to server mapping but servers are discovered using discovery. So the relationship between server and application is also done manually.

Currently one application CI is created that is mapped to all dev, stage and prod servers. This will give flexibility for us to drill down from application and identify all the infrastructure supporting it. But the problem with that approach is that if any issue on non production server will show as incident in application. There are very similar issues.

Is there a best practice to handle this scenario

Do we create multiple applications one for each environement and match to their respective server?

Any thoughts will be appreciated

Thanks

Labels:
0 Helpfuls
  • 1,618 Views
2 REPLIES 2

Maik Skoddow
Tera Patron
Tera Patron

‎02-20-2022 11:19 PM

Hi

it is really important to keep separated configuration items for each instance. Please take the CSDM as blueprint to model your data.

You can download my Knowledge Sources To Go. You will find in that document many links to helpful resources regarding your question.

Kind regards
Maik

0 Helpfuls

SebastianKunzke
Kilo Sage
Kilo Sage

‎02-21-2022 12:52 AM

The best practices is to handle it separate. Beside the documents a short summary why:

  • In all your process you can distinguish between the application services, because you CMDB displays the reality better
  • You can see, what business application do not have a dev, test system
  • In case you want to use Service mapping in the future, you wouldn't need to redesign your application services 
  • Not all business service offering will consumed dev, test, prod environments
  • You can define different service commitments such as SLAs, availability
0 Helpfuls