> For the complete documentation index, see [llms.txt](https://help.highlight.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.highlight.net/functionality.md). # Functionality ## Provisioning * [**Provisioning API**](/functionality/provisioning-api.md) explained * [**Bulkloading**](/functionality/bulkloading.md) ## Application Awareness * [**Feature set**](/functionality/application-awareness-tm.md) Our Application Awareness feature set explained ## Autodiscovery * [**Bandwidth**](/functionality/bandwidth-autodiscovery.md) How Highlight can discover bandwidth from a configured QoS policy, and from DSL circuits * [**Broadband Clarity**](/functionality/broadband-clarity.md) How Highlight's Broadband Clarity feature works * [**Classes**](/functionality/class-autodiscovery.md) How Highlight discovers classes from the configured QoS policy * [**Multilink**](/functionality/multilink-autodiscovery.md) Explains discovery of switch interfaces bonded using LACP or PAgP; and WAN interfaces bonded using PPP * [**VLANs**](/functionality/vlan-autodiscovery.md) How Highlight can discover VLANs (sub-interfaces) on monitored physical interfaces * [**Switches**](/functionality/switch-functionality.md) Information gathered by Highlight and supported manufacturers * [**Dynamic IP addresses**](/functionality/watch-dns-hostname-and-dynamic-ip-addresses.md) How Highlight handles DNS hostnames and changing IP addresses ## Highlight System * [**Architecture**](/functionality/highlight-architecture.md) An overview of how Highlight agents work with public, private and hybrid networks * [**Server specifications**](/functionality/server-specifications.md) Minimum OS, CPU, RAM and free disk space requirements for Highlight servers, plus network access required * [**Performance tests**](/functionality/performance-test-information.md) Explanation of why use performance tests, which ones to configure, and what each test does * [**SNMP objects**](/functionality/snmp-objects-used-in-highlight.md) Summarised list of SNMP Objects used in Highlight * [**Data retention**](/functionality/highlight-data-retention.md) System defaults for retaining data used to create the Details page charts * [**Polling interval**](/functionality/highlight-polling-intervals.md) System defaults for polling various elements in Highlight * [**Customising**](/functionality/customising-highlight.md) Customising Highlight * [**Features by vendor**](/functionality/features-and-supported-vendors.md) The options available in Highlight in terms of vendors and features ## Network and Security Considerations * [**Network overhead**](/functionality/traffic-load-generated-by-highlight.md) Explains and quantifies the small amount of management overhead that Highlight monitoring adds * [**Security**](/functionality/highlight-security-considerations.md) Explains Highlight mitigation of risk for SNMP Write access ## Riverbed Steelhead * [**Riverbed Steelhead**](/functionality/riverbed-steelhead-monitoring.md) Using Highlight to monitor traffic optimisation and application breakdown across Riverbed Steelhead devices --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.highlight.net/functionality.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.