Are you receiving a 304 status code in your IBM Cloud Logs Routing agent?

IBM Cloud Logs Routing disables your ingestion when the configured target is not reachable.

IBM Cloud Logs Routing returns errors with a response code of 304 which is logged in your agent with the following text: "msg":"Failed to connect to ingester, retrying","error":"Connection Error websocket: bad handshake. Status Code: 304.".

Your target is set up incorrectly.

To see the reason why your ingestion is disabled, follow the instructions to get details about your tenant. The details will include a write_status field in the response. If the tenant is in the state failed, the response will contain the reason. Use this information to enable your tenant.

For example, the following write status indicates that the service to service authorization between IBM Cloud Logs and IBM® Cloud Logs Routing is not set up correctly:

{
    "write_status": {
        "status": "failed",
        "reason_for_last_failure": "Logs endpoint is not reachable. Received status code: 403",
        "last_failure": "2024-10-14T10:49:09Z"
    }
}

Follow the instructions to create a service to service authorization to enable your tenant.