Forum Discussion
Azure Service Map
Rsrikant In my view, it should not be a problem as long as you know what is you backend DB server for your application. If you consider your application server as the focus machines you will only get the traffic between your application server and the DB server.
Are you expecting any other external services apart from this application in question are communicating directly with the DB? Ideally this should not be the case, even if the DB server is shared, I do not expect the DB is shared as well. However, you cannot ignore the possibility, if you are not sure about the architecture of the application as there might be direct integration with you DB for push/pull data. In that case, I suggest to select the DB server as the focus machine as well and see with whom this guy is talking to and try to identify if any traffic going to other service is related to you application.
Please keep in mind that the agent captures information about all TCP processes running on the focus machine and the inbound and outbound connections for each process. So, you will get a lot of connections that may not be directly related to your application.
Give it a try and see how it goes :). Hope this helps!
Thanks,
Rohan
- RsrikantJun 23, 2020Copper Contributor
Thanks. Got your point.
As you have mentioned we will be focussing on the application & seek what connections/communications does it makes to the DB.
But from the DB side, since multiple DBs are hosted in a single server & since it is shared with multiple Applications, will be finding it difficult to identify which DB instance the request is coming & what will be the dependencies on the DB server.
If there is dependency on any other applications on this DB instance, it will be difficult to identity & segregate it.