/** * Agilicus API * Agilicus is API-first. Modern software is controlled by other software, is open, is available for you to use the way you want, securely, simply. The OpenAPI Specification in YAML format is available on [www](https://www.agilicus.com/www/api/agilicus-openapi.yaml) for importing to other tools. A rendered, online viewable and usable version of this specification is available at [api](https://www.agilicus.com/api). You may try the API inline directly in the web page. To do so, first obtain an Authentication Token (the simplest way is to install the Python SDK, and then run `agilicus-cli --issuer https://MYISSUER get-token`). You will need an org-id for most calls (and can obtain from `agilicus-cli --issuer https://MYISSUER list-orgs`). The `MYISSUER` will typically be `auth.MYDOMAIN`, and you will see it as you sign-in to the administrative UI. This API releases on Bearer-Token authentication. To obtain a valid bearer token you will need to Authenticate to an Issuer with OpenID Connect (a superset of OAUTH2). Your \"issuer\" will look like https://auth.MYDOMAIN. For example, when you signed-up, if you said \"use my own domain name\" and assigned a CNAME of cloud.example.com, then your issuer would be https://auth.cloud.example.com. If you selected \"use an Agilicus supplied domain name\", your issuer would look like https://auth.myorg.agilicus.cloud. For test purposes you can use our [Python SDK](https://pypi.org/project/agilicus/) and run `agilicus-cli --issuer https://auth.MYDOMAIN get-token`. This API may be used in any language runtime that supports OpenAPI 3.0, or, you may use our [Python SDK](https://pypi.org/project/agilicus/), our [Typescript SDK](https://www.npmjs.com/package/@agilicus/angular), or our [Golang SDK](https://git.agilicus.com/pub/sdk-go). 100% of the activities in our system our API-driven, from our web-admin, through our progressive web applications, to all internals: there is nothing that is not accessible. For more information, see [developer resources](https://www.agilicus.com/developer). * * The version of the OpenAPI document: 2025.12.16 * Contact: dev@agilicus.com * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). * https://openapi-generator.tech * Do not edit the class manually. */ export interface _NetworkDetailedStats { /** * The total number of connections currently established or establishing. This value is a guage, meaning it is not monotonic. */ connections_current: number; /** * The number of times a connection attempt failed because it took too long to establish */ connections_timedout: number; /** * The number of times a connection attempt failed because a host lookup failed */ connections_host_not_found: number; /** * The number of times a connection attempt failed because the target host reset the connection */ connections_reset: number; /** * The number of times a connection attempt failed because TLS validation did not succeed. This is typically because either the server certificate did not match the expected one, or because we did not trust it. Try to fix this problem by ensuring that the certitifate is valid, matches the hostname the client connects to, and that it is issued by a certificate authority trusted by the client. Alternatively, if this is not possible, disable certificate validation. */ connections_tls_validation_failed: number; /** * The number of times a connection attempt failed for reasons other than the explicitly enumerated ones. */ connections_other_failure: number; /** * The number of times a connection attempt failed because the upstream returned an invalid TLS response. Typically this happens because the upstream is not configured to use TLS, but it could be due to a bug in the upstream server, or some other incompatibility (e.g. an unsupported version whose versioning mechanism is unknown). Check that the server is configured to serve TLS, or connect to it using plaintext. */ connections_tls_protocol_failure?: number; /** * The number of times a connection attempt failed because the upstream server replied that it did not support one of the versions supported by the client. Typically this is because the server is running a fairly old version of software. See if there is a new version of the software available, or ensure that it provides a maximum TLS version of at least 1.2. */ connections_tls_unsupported_version?: number; /** * The number of times a connection attempt failed because the upstream server replied that it was unable to accept the connection request. This can be for various reasons such as an incompatible set of cipher suites. Check that the server supports a modern set of cipher suites, or look at its logs to see if it indicates the reason for the failure. */ connections_tls_remote_error?: number; /** * The number of times a connection attempt failed because the TLS negotiation failed for reasons other than the explicitly enumerated ones. */ connections_tls_other_error?: number; /** * The number of times we failed to send a datagram to a network because it was too large (e.g. above MTU) */ datagrams_too_large_sent?: number; /** * The number of times we failed to receive a datagram to a network because it was too large (e.g. above MTU) */ datagrams_too_large_received?: number; } export interface NetworkDetailedStats extends _NetworkDetailedStats { _builtin_original?: _NetworkDetailedStats; _remove_builtin_extensions?: () => void; } export declare class NetworkDetailedStatsImpl implements _NetworkDetailedStats { _builtin_original?: _NetworkDetailedStats; connections_current: number; connections_timedout: number; connections_host_not_found: number; connections_reset: number; connections_tls_validation_failed: number; connections_other_failure: number; connections_tls_protocol_failure: number | undefined; connections_tls_unsupported_version: number | undefined; connections_tls_remote_error: number | undefined; connections_tls_other_error: number | undefined; datagrams_too_large_sent: number | undefined; datagrams_too_large_received: number | undefined; constructor(base: _NetworkDetailedStats); _remove_builtin_extensions(): void; } export declare function newNetworkDetailedStatsImpl(base: _NetworkDetailedStats): NetworkDetailedStatsImpl;