Tag-based network-wide troubleshooting

1 . A troubleshooting system comprising:

a storage device;

a tagging module coupled to the storage device and configured to obtain telemetry data for a network and to tag network entities in the network with a plurality of issue-indicating tags based on the telemetry data, the network entities including a first network entity of a first entity type and a second network entity of a second entity type different from the first entity type,

wherein the first network entity is tagged with a first set of issue-indicating tags, of the plurality of issue-indicating tags, specific to the first entity type, and

wherein the second network entity is tagged with a second set of issue-indicating tags, of the plurality of issue-indicating tags, specific to the second entity type; and

a tag analyzer coupled to the tagging module and configured to determine a cause of a network issue experienced on the network based on a correlation between the first set of issue-indicating tags specific to the first entity type and the second set of issue-indicating tags specific to the second entity type and to output the determined cause.

2 . The troubleshooting system defined in claim 1 , wherein the plurality of issue-indicating tags comprise tags each identifying an issue and a scope of the network affected by the issue.

3 . The troubleshooting system defined in claim 2 , wherein the tags each identify a timestamp associated with the issue.

4 . The troubleshooting system defined in claim 3 , wherein the tags each identify a severity of the issue.

5 . The troubleshooting system defined in claim 1 , wherein the first network entity is a first device in the network, wherein the second network entity is a second device in the network, wherein a first tag in the plurality first set of issue-indicating tags is associated with the first device in the network, and wherein a second tag in the second set of issue-indicating tags is associated with the second device in the network.

6 . The troubleshooting system defined in claim 5 , wherein the first device is one of a client device, a wireless access point, a network switch, an application server, or a network server and wherein the second device is another one of the client device, the wireless access point, the network switch, the application server, or the network server.

7 . The troubleshooting system defined in claim 1 , wherein the first network entity is a first device in the network, wherein the second network entity is a second device in the network, wherein a first tag in the plurality first set of issue-indicating tags is associated with a component of the first device in the network, and wherein a second tag in the second set of issue-indicating tags is associated with the second device in the network.

8 . The troubleshooting system defined in claim 7 , wherein the component of the first device is a processor of the first device, a memory of the first device, a radio of the first device, or an application executing on the first device.

9 . The troubleshooting system defined in claim 1 , wherein the first network entity is a client device of the network, wherein the network issue comprises a client application experience issue indicated by a given tag in the first set of issue-indicating tags, and wherein the tagging module is configured to tag an application executing on the client device of the network with the given tag based on the telemetry data.

10 . The troubleshooting system defined in claim 9 , wherein the second set of issue-indicating tags comprises an additional tag associated with a wireless access point, a network switch, or a server and wherein the tag analyzer is configured to correlate at least the additional tag with the given tag to determine a cause of the client application experience issue indicated by the given tag.

11 . The troubleshooting system defined in claim 10 , wherein the determined cause of the client application experience issue comprises an issue indicated by the additional tag associated with the client device, the wireless access point, the network switch, or the server.

12 . The troubleshooting system defined in claim 1 , wherein the second set of issue-indicating tags comprises a time-dependent tag indicative of a trend over time.

13 . The troubleshooting system defined in claim 12 , wherein the first network entity is a client device of the network, wherein the network issue comprises a client application experience issue indicated by a given tag in the first set of issue-indicating tags, wherein the tagging module is configured to tag an application executing on the client device of the network with the given tag based on the telemetry data, and wherein the tag analyzer is configured to correlate at least the time-dependent tag with the given tag to determine that a cause of the client application experience issue comprises a periodic issue indicated by the time-dependent tag.

14 . A method of performing troubleshooting for a network, the method comprising:

associating a given network entity with a first tag indicative of a first issue experienced by the given network entity at a given time;

associating the given network entity with a second tag indicative of a second issue experienced by the given network entity at the given time;

disassociating the given network entity from a third tag indicative of a periodic issue at the given time;

based on the given network entity being associated with the second tag at the given time and being disassociated with the second tag at one or more additional times, associating the given network entity with the third tag indicative of the periodic issue being experienced by the given network entity;

determining a cause of the first issue based on the first and third tags; and

outputting a notification identifying the cause of the first issue.

15 . The method defined in claim 14 , wherein the given network entity is a client device of the network.

16 . The method defined in claim 15 , wherein associating the given network entity with the first tag is based on telemetry data for the given network entity meeting at least a first criterion and wherein associating the given network entity with the second tag is based on the telemetry data for the given network entity meeting a second criterion.

17 . The method defined in claim 14 , wherein the first tag includes the first issue, the given time, a first scope of the network affected by the first issue, and a first level of severity of the first issue and wherein the second tag includes the second issue, the given time, a second scope of the network affected by the second issue, and a second level of severity of the second issue.

18 . The method defined in claim 14 , wherein outputting the notification comprises sending the notification as an alert to a user device or sending the notification to server equipment executing a network management application for user presentation.

19 . The method defined in claim 14 , wherein determining the cause of the first issue comprises correlating the third tag and the second tag with the first tag and wherein the second tag and at the third tag indicate the cause of the first issue.

20 . One or more non-transitory computer-readable storage media comprising computer-executable instructions that, when executed by one or more processors, cause the one or more processors to:

obtain telemetry data for at least some network entities in a network;

determine whether to associate a first issue-indicating tag with each of the network entities in the network based on whether the telemetry data for each of the network entities satisfies a first criterion, wherein the first criterion is satisfied based on a metric in the telemetry data for a given one of the network entities exceeding a corresponding threshold for the metric;

determine whether to associate a second issue-indicating tag with each of the network entities in the network based on whether the telemetry data for each of the network entities satisfying satisfies a second criterion;

determine a cause of a network issue experienced on the network based on a correlation between at least the first and second issue-indicating tags; and

take a remediation action based on the determined cause.