> For the complete documentation index, see [llms.txt](https://docs.eseye.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eseye.com/api-reference/connectivity-metrics/scope-and-boundaries.md). # Scope and boundaries Connectivity Metrics is deliberately focused on connectivity telemetry rather than application data. The boundaries below are design decisions, and they are what allow the service to scale, stay compliant and behave consistently across a global footprint. ### What the service does * Provides structured, normalised connectivity metadata * Is operator-agnostic wherever that is technically possible * Avoids payload inspection entirely ### What the service does not do * Expose packet payloads * Guarantee that every operator provides every field * Provide raw network protocol parity across all networks * Perform deep application-layer inspection ### Reading these limits Two of these are worth expanding, because they shape how you model the data. **Field availability varies by operator:** Some fields, serving network context being the common example, depend on what the operator supplies. Build your pipeline to tolerate absent fields rather than treating them as errors, and expect coverage to differ between networks and countries. **Protocol parity is not guaranteed:** Networks differ in what they expose and how. Normalisation gets you consistent structure across operators, and it does not manufacture data that a given network never provided in the first place. Neither limit undermines estate-level analysis. Both are worth knowing before you write queries that assume a field is always populated. ### Related * * [Traffic Flow (NetFlow) Metrics](/api-reference/connectivity-metrics/traffic-flow-netflow-metrics.md) --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.eseye.com/api-reference/connectivity-metrics/scope-and-boundaries.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.