lbcli update logs targets

AI Tools

Updates an existing log forwarding target.

Synopsis

Updates an existing log forwarding target.

Only the flags you explicitly provide are changed; all other fields keep their current values. Use --type only when switching the target type (loki ↔ rsyslog); when changing type all type-specific flags become required.

lbcli update logs targets [flags]

Examples

# Disable a Loki target without touching any other field lbcli -J $JWT update logs targets \ --name=loki-prod \ --enabled=false # Update only the rsyslog endpoint lbcli -J $JWT update logs targets \ --name=rsyslog-siem \ --endpoint=siem.example.com:6514 # Add TLS to an existing rsyslog target lbcli -J $JWT update logs targets \ --name=rsyslog-siem \ --rsyslog-tls=rsyslog-bundle

Flag	Short	Type	Default	Description
--help	-h	bool		Help for `targets`.
--enabled		bool	true	Enable this target immediately (default: true).
--endpoint		string		rsyslog server address as host:port or ip:port; e.g., siem.example.com:514 (required for type=rsyslog).
--loki-password		string		Loki basic-auth password.
--loki-tls		string		Name of a TLS bundle for Loki mutual TLS.
--loki-username		string		Loki basic-auth username.
--name		string		Name of the log target (required).
--rsyslog-debug		bool		Enable rsyslog debug mode.
--rsyslog-timeout		string		rsyslog dial timeout; e.g., 5s.
--rsyslog-tls		string		Name of a TLS bundle for rsyslog TLS transport.
--type		string		Target type: loki or rsyslog (required).
--url		string		Loki push URL including scheme, e.g., https://loki.example.com:3100 (required for type=loki).

Last updated on

Was this page helpful?