<a id="reference-relation-endpoints"></a>

# Relation endpoints

[Relation endpoints](https://canonical.com/juju/docs/juju-cli/3.6/reference/relation/#relation)
are the integration points a charm exposes so it can be connected to other
applications.

The osquery charm is a subordinate charm. It requires a single endpoint that
attaches it to a principal application, and it doesn’t provide any endpoints of
its own.

## Requires

| Endpoint       | Interface   | Scope       | Description                                                                                                                                                                                            |
|----------------|-------------|-------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| `general-info` | `juju-info` | `container` | Attaches the osquery subordinate to a principal application so that the<br/>`osqueryd` agent runs on the same machine. The `container` scope<br/>restricts the relation to units that share a machine. |

Because osquery is endpoint security monitoring software, it’s designed to run
alongside any workload. Integrating the charm over the generic `juju-info` interface lets
it attach to any principal machine charm — for example, the `ubuntu` charm — so
you can monitor arbitrary hosts.

## Provides

The charm doesn’t currently provide any relation endpoints. It communicates with
its osquery controller directly over TLS rather than through a Juju relation.

<!-- TODO: If the charm gains provided endpoints (for example, an observability or
controller integration), document them here. -->
