Loki
Loki connections to the CipherTrust Manager can be configured using the following:
Managing Loki Connections using GUI
To configure a Loki connection:
Host: IP address or hostname of the Loki server.
Port: port number for connecting to the Loki server.
Loki Grafana doesn't directly support authentication, but you can configure authentication values for requests between CipherTrust Manager and a reverse proxy, which forwards requests to Loki Grafana. Check the Loki Grafana deployment for the authentication required for incoming data.
HTTP User: name of the HTTP user for basic authentication.
HTTP Password: password of the HTTP user.
Transport: protocol for transport. Either TCP or TLS. TLS requires additional settings.
Settings for TLS:
You must provide CA Certificate or select Skip Certificate Verification
CA Certificate: either upload the CA certificate or paste the certificate content. This is a CA which directly or indirectly signs the Elasticsearch server certificate.
File Upload: select and click Upload Certificate to upload the trusted CA certificate from your machine. In TLS mode, the CA certificate must be in PEM format.
Text: select and paste the certificate content in the text field.
Skip Certificate Verification: select if the TLS verification of the CA certificate is not required.
Click Test Credentials to check whether the connection is configured correctly. If the test is successful, the status is OK else the status is Fail.
Click Next to move to the Add Products screen of the Add Connection wizard.
Managing Loki Connections using ksctl
The following operations can be performed:
Create/Get/Update/Delete a Loki connection
List all Loki connections
Test an existing Loki connection
Test the new Loki connection parameters before establishing the connection
The host and port are the mandatory parameters for Loki connections. The supported transport mode for sending data are tls and tcp.
The Loki connections can be authenticated or unauthenticated. Authentication can include username and password or TLS authentication or both. Check the Loki Grafana deployment for the authentication required for incoming data. Loki Grafana doesn't directly support authentication, so authentication takes place between CipherTrust Manager and a reverse proxy, which forwards requests to Loki Grafana.
The tls mode requires either a trusted CA certificate in the PEM format or --insecure-skip-verify set to true. By default, the CipherTrust Manager attempts to validate the reverse proxy's server certificate using the provided CA. The external CAs already present on the CipherTrust Manager are not used. Use --ca-cert to provide a CA which directly or indirectly signs the server certificate. Use the --insecure-skip-verify flag to indicate that CipherTrust Manager does not verify Elasticsearch's presented server certificate.
Creating a Loki Connection
To create a Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki create --name <connection-name> --products <products-name> --description <description> --host <host> --port <port> --transport <transport-protocol> --http-user <username> --http-password <password> --ca-cert <ca-cert> --meta <Key:Value> --insecure-skip-verify
The supported transport mode for sending data are tls and tcp. The tls mode requires either a trusted CA certificate in the PEM format or --insecure-skip-verify set to true.
Example Request
ksctl connectionmgmt log-forwarder loki create --name loki-conn-1 --description conn-description --host 127.0.0.1 --port 1234 --transport tcp --http-user admin --http-password password
Example Response
{
"id": "9d3af367-d4a3-4838-8663-ce07d3e88353",
"uri": "kylo:kylo:connectionmgmt:connections:loki-conn-1-9d3af367-d4a3-4838-8663-ce07d3e88353",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2022-05-04T07:53:49.838640861Z",
"updatedAt": "2022-05-04T07:53:49.837431591Z",
"service": "loki",
"category": "log-forwarders",
"last_connection_ok": null,
"last_connection_at": "0001-01-01T00:00:00Z",
"name": "loki-conn-1",
"description": "conn-description",
"host": "127.0.0.1",
"port": 1234,
"loki_params": {
"insecure_tls_skip_verify": false,
"transport": "tcp",
"http_user": "admin"
}
}
Getting Details of a Loki Connection
To get details of a Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki get --id <Connection-Name/ID>
Example Request
ksctl connectionmgmt log-forwarder loki get --id 9d3af367-d4a3-4838-8663-ce07d3e88353
Example Response
{
"id": "9d3af367-d4a3-4838-8663-ce07d3e88353",
"uri": "kylo:kylo:connectionmgmt:connections:loki-conn-1-9d3af367-d4a3-4838-8663-ce07d3e88353",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2022-05-04T07:53:49.838641Z",
"updatedAt": "2022-05-04T07:53:49.837432Z",
"service": "loki",
"category": "log-forwarders",
"last_connection_ok": null,
"last_connection_at": "0001-01-01T00:00:00Z",
"name": "loki-conn-1",
"description": "conn-description",
"host": "127.0.0.1",
"port": 1234,
"loki_params": {
"insecure_tls_skip_verify": false,
"transport": "tcp",
"http_user": "admin"
}
}
Updating a Loki Connection
To update a Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki modify --id <Connection-Name/ID> --products <products-name> --description <description> --host <host> --port <port> --transport <transport-protocol> --http-user <username> --http-password <password> --ca-cert <ca-cert> --meta <Key:Value> --insecure-skip-verify
The supported transport mode for sending data are tls and tcp. The tls mode requires either a trusted CA certificate in the PEM format or --insecure-skip-verify set to true.
Example Request
ksctl connectionmgmt log-forwarder loki modify --id 9d3af367-d4a3-4838-8663-ce07d3e88353 --host 127.0.0.1
Example Response
{
"id": "9d3af367-d4a3-4838-8663-ce07d3e88353",
"uri": "kylo:kylo:connectionmgmt:connections:loki-conn-1-9d3af367-d4a3-4838-8663-ce07d3e88353",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2022-05-04T07:53:49.838641Z",
"updatedAt": "2022-05-04T08:17:20.615258139Z",
"service": "loki",
"category": "log-forwarders",
"last_connection_ok": null,
"last_connection_at": "0001-01-01T00:00:00Z",
"name": "loki-conn-1",
"description": "conn-description",
"host": "127.0.0.1",
"port": 1234,
"loki_params": {
"insecure_tls_skip_verify": false,
"transport": "tcp",
"http_user": "admin"
}
}
Deleting a Loki Connection
To delete a Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki delete --id <Connection-Name/ID>
Example Request
ksctl connectionmgmt log-forwarder loki delete --id 9d3af367-d4a3-4838-8663-ce07d3e88353
Example Response
There will be no response if the Loki connection is deleted successfully.
Getting List of Loki Connections
To list all the Loki connections, run:
Syntax
ksctl connectionmgmt log-forwarder loki list
Example Request
ksctl connectionmgmt log-forwarder loki list
Example Response
{
"skip": 0,
"limit": 10,
"total": 1,
"resources": [
{
"id": "9d3af367-d4a3-4838-8663-ce07d3e88353",
"uri": "kylo:kylo:connectionmgmt:connections:loki-conn-1-9d3af367-d4a3-4838-8663-ce07d3e88353",
"account": "kylo:kylo:admin:accounts:kylo",
"createdAt": "2022-05-04T07:53:49.839242Z",
"updatedAt": "2022-05-04T07:53:49.839242Z",
"service": "loki",
"category": "log-forwarders",
"last_connection_ok": null,
"last_connection_at": "0001-01-01T00:00:00Z",
"name": "loki-conn-1",
"description": "conn-description",
"host": "127.0.0.1",
"port": 1234
}
]
}
Testing an Existing Loki Connection
To test an existing Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki test --id <Connection-Name/ID>
Example Request
ksctl connectionmgmt log-forwarder loki test --id 9d3af367-d4a3-4838-8663-ce07d3e88353
Example Response
{
"connection_ok": true
}
Testing a New Loki Connection
To test the parameters of a New Loki connection, run:
Syntax
ksctl connectionmgmt log-forwarder loki test --host <host> --port <port> --transport <transport-protocol> --http-user <username> --http-password <password> --ca-cert <ca-cert> --insecure-skip-verify
Example Request
ksctl connectionmgmt log-forwarder loki test --host 127.0.0.1 --port 1234 --transport tcp --http-user admin --http-password password
Example Response
{
"connection_ok": true
}
