influxdb-outlet create

ockam influxdb-outlet create [OPTIONS] --to <SOCKET_ADDRESS> --leased-token-permissions <JSON> --leased-token-expires-in <DURATION> [NAME]

Create InfluxDB Outlets

Arguments

  • [NAME] (optional)
    Address of your InfluxDB Outlet, which is part of a route used in other commands. This unique address identifies the InfluxDB Outlet worker on the Node on your local machine. Examples are /service/my-outlet or my-outlet. If not provided, outlet will be used, or a random address will be generated if outlet is taken. You will need this address when creating a InfluxDB Inlet using ockam influxdb-inlet create

Options

  • --to <SOCKET_ADDRESS>
    Address where your InfluxDB server is running, in the format <scheme>://<hostname>:<port>. At least the port must be provided. The default scheme is tcp and the default hostname is 127.0.0.1

  • --tls (optional)
    [DEPRECATED] Use the tls scheme in the --from argument

  • --from [OUTLET_ADDRESS] (optional)
    Alternative to the positional argument. Address of your InfluxDB Outlet, which is part of a route used in other commands

  • --at [NODE_NAME] (optional)
    Your InfluxDB Outlet will be created on this node. If you don't provide it, the default node will be used

  • --allow [POLICY_EXPRESSION] (optional)
    Policy expression that will be used for access control to the InfluxDB Outlet. If you don't provide it, the policy set for the "tcp-outlet" resource type will be used

  • --privileged (optional)
    Use eBPF and RawSocket to access TCP packets instead of TCP data stream. If OCKAM_PRIVILEGED env variable is set to 1, this argument will be true

  • --fixed-token [FIXED_TOKEN] (optional)

  • --org-id [ORG_ID] (optional)
    The organization ID of the InfluxDB server

  • --all-access-token [TOKEN] (optional)
    The token to use to connect to the InfluxDB server

  • --leased-token-permissions <JSON>
    The permissions to grant to new leases

  • --leased-token-expires-in <DURATION>
    The duration for which a lease is valid