network core

Server Dependency Analysis with Self-Referencing Nodes

Scénario de test & Cas d'usage

Business Context

IT Operations is mapping server dependencies. Some legacy servers ping themselves (localhost loopback) for heartbeat checks. The team needs to identify critical dependency clusters (cores) while explicitly handling these self-loops, which are usually ignored but are critical for this specific legacy audit.
Data Preparation

Defining a server network including self-loops (Server_A -> Server_A) and isolated islands.

Copied!
1 
2DATA mycas.server_logs;
3INFILE DATALINES delimiter=',';
4INPUT src_srv $ dest_srv $;
5DATALINES;
6SRV_A,SRV_A, SRV_A,SRV_B, SRV_B,SRV_C, SRV_C,SRV_A, SRV_D,SRV_E, SRV_Z,SRV_Z;
7 
8RUN;
9 

Étapes de réalisation

1
Execute Core Decomposition enabling 'selfLinks' to include loopbacks in the density calculation.
Copied!
1 
2PROC CAS;
3network.core / selfLinks=TRUE links={name='server_logs', from='src_srv', to='dest_srv'} outNodes={name='server_resilience', replace=true};
4 
5RUN;
6 
7QUIT;
8 
2
Review Solution Summary to confirm self-links were processed.
Copied!
1 
2PROC CAS;
3TABLE.fetch / TABLE='server_resilience';
4 
5RUN;
6 
7QUIT;
8 

Expected Result


Server_A and Server_Z (which have self-links) should be processed correctly. Server_Z, despite being isolated from the main grid, has a link to itself, which might affect its core classification compared to a completely disconnected node if selfLinks=FALSE was used. The 3-node loop (A-B-C) should form a higher core.