It is less fine when the application is one you inherited and would rather not touch, when someone else owns the deployment, or when you simply do not want observation code living inside the thing being observed. The same setup can live in a file next to the project instead, with nothing in the program saying so.
It is less fine when the application is one you inherited and would rather not touch, when someone else owns the deployment, or when you simply do not want observation code living inside the thing being...
The same setup can live in a file next to the project instead, with nothing in the program saying so.
A pattern's blast radius is one level of one named container, stated on the line above it, so match = "*" on shop:OrderService can never accidentally wrap something in another module.
The page is ready to read now. The fuller skim-friendly version will appear here automatically.
It is less fine when the application is one you inherited and would rather not touch, when someone else owns the deployment, or when you simply do not want observation code living inside the thing being observed. The same setup can live in a file next to the project instead, with nothing in the program saying so. A pattern's blast radius is one level of one named container, stated on the line above it, so match = "*" on shop:OrderService can never accidentally wrap something in another module.
For all of those the entry point edit is one edit too many. The file A wrapture.toml says what to observe and where the events go.
Open the app view to save this story, compare related coverage, and continue from the same source.