You are on page 1of 1

Assumption: an app is using N dependencies.

Each dependency performs API calls to their 


vendor's server in order to perform any given function.
Goal: monitor all behaviour related to the app, including sub dependencies of a 
dependency.
Limitations: dependency can't form a dependency graph (i.e. mapping of sub dependencies 
is impossible due to legal or compliance issues)

ELK 
stack

Data 
pipeline

API 
server of  API 
ELK ingests logs from direct dependency
sub dep  server of 
#1 sub sub 
dep #1
API 
server 
#1 API calls
API calls

API calls
sub sub dep 
sub dep #1
#1

dep #1

you can increase 


the list with any 
other amount of 
direct 
dependencies 
used in the App

sub dep #1
App

dep #2

you can increase  API calls you can increase 


the list with any  the list with any 
other amount of  other amount of 
direct  direct 
dependencies  dependencies 
used in the App used in the App

API 
server 
#2

You have control over this only! No control over this No control over this

You might also like