A rule-based service path connectivity generator can utilize the SDN GUI to add a connectivity generation feature by which a user can generate topology reports in an event-based fashion or schedule jobs for batch based. For example, an event-based topology report can be generated for CNFs deployed in specific core regions. The topology reports can comprise a predefined format including A side and Z side info (e.g., nullable & non-nullable types) for each service path (e.g., cNF name, service path type, IP address, virtual local area network (VLAN), PORT) and can show up under a topology report section via the GUI. The values in the topology reports can be populated from the configuration database (within the SDN repository). The SDN GUI can comprise a feature to define rules for topology report generation. Under a rule definition feature, there can be a section in which the user can define a name for a report (e.g., based on interface types and/or following a naming convention) and set targets for the rule definition (A side and Z side NFs). Under the rule definition feature, there can also be a section in which the user can define a set of rules to be applied to the target NFs. Each rule can have two sides and an operation condition. Each side of the rule can be a value entered by the user (e.g., VLAN ID, IP address, location identifier) or a value from a dropdown list that contains objects and attributes from a Yang file of mounted NFs (e.g., cNF name, IP address, PORT). Additionally, an operation condition can be selected from a dropdown list (e.g., contains, same subnet, equal to, or the like). Once the topology reports are generated, an action can be set by the user. For example, the action can comprise sending an extensible markup language (XML) file to a consumer landing zone, or publishing a javascript object notation file in a data movement as a platform (DMaaP). The user can also select the frequency of publishing/sending the report.