Good processes for debugging a production environment? Copy data to Dev?

I thought about that a bit. The idea is that something is wrong with PROD. The data received makes the web application behave differently than in other environments. Thus, data in other environments does not synchronize with prod (as expected). However, an error occurs, and for some reason this only happens in PROD, possibly due to differences in data.

I am wondering what is good practice to fix these issues? More tests, of course. But beyond that? It was possible to create new data in dev, but the thing is that some data points or some combination of actions lead to the wrong data point. Perhaps using any other data source to reach the “actual” data point, which is different from the “expected” data point. Apologizes that this is not a very good description, and tries to be an example and definition of a common production error.

I know this is not a very accurate question. Hopefully there are recommendations that give good recommendations.

+5
source share
1 answer

. , , - (TIP).

, , , : -)

, , . : . . , , -. , , , .

, . - , 5% . 10% 20% ..

, , . -, , , . , -, , , , .

- API/. API/, API/, / .

, . , . , , .

:

+4

All Articles