| 1 | ##### Summary |
| 2 | <!-- |
| 3 | Describe the change in summary section, including rationale and design decisions. |
| 4 | Include "Fixes #nnn" if you are fixing an existing issue. |
| 5 | --> |
| 6 | |
| 7 | ##### Test Plan |
| 8 | |
| 9 | <!-- |
| 10 | Provide enough detail so that your reviewer can understand which test cases you |
| 11 | have covered, and recreate them if necessary. If our CI covers sufficient tests, then state which tests cover the change. |
| 12 | --> |
| 13 | |
| 14 | ##### Additional Information |
| 15 | <!-- This is usually used to help others understand your |
| 16 | motivation behind this change. A step-by-step reproduction of the problem is |
| 17 | helpful if there is no related issue. --> |
| 18 | |
| 19 | <details> <summary>For users: How does this change affect me?</summary> |
| 20 | <!-- |
| 21 | Describe the PR affects users: |
| 22 | - Which area of Netdata is affected by the change? |
| 23 | - Can they see the change or is it an under the hood? If they can see it, where? |
| 24 | - How is the user impacted by the change? |
| 25 | - What are there any benefits of the change? |
| 26 | --> |
| 27 | </details> |