coolify
coolify copied to clipboard
[Bug]: Log Drain to Axiom not working
Description
Log drain to Axiom not working. No logs are being sent, Axiom dataset is still empty
Minimal Reproduction (if possible, example repository)
- in server config added Axiom key and dataset name
- axiom is configured such that the key allows both ingest and query permission to the dataset
- Since logs were not flowing, I also restarted the server but no success
- In coolify services logs view i can see the logs being displayed and refreshed
Exception or Error
No response
Version
v4.0.0-beta.190
I had missed turning on the config at Services level in Advanced tab. Inspite of turning it on the logs are not draining
Wheni tail the logs of the coolify-log-drain container, I see the following:
[2024/01/18 16:01:51] [debug] [upstream] KA connection #50 to api.axiom.co:443 is now available
[2024/01/18 16:01:51] [debug] [out flush] cb_destroy coro_id=93
[2024/01/18 16:01:51] [debug] [retry] new retry created for task_id=0 attempts=1
[2024/01/18 16:01:51] [ warn] [engine] failed to flush chunk '1-1705593710.181330124.flb', retry in 10 seconds: task_id=0, input=forward.0 > output=http.0 (out_id=0)
[2024/01/18 16:02:01] [debug] [output:http:http.0] task_id=0 assigned to thread #1
[2024/01/18 16:02:01] [debug] [upstream] KA connection #51 to api.axiom.co:443 is connected
[2024/01/18 16:02:01] [debug] [http_client] not using http_proxy for header
[2024/01/18 16:02:01] [error] [output:http:http.0] api.axiom.co:443, HTTP status=403
{"message":"Forbidden"}
The API token is correct. Anything else I need to check?
Hello @andrasbacsai Any pointers on how I can get this working? Or if its a bug that needs to be fixed
I could not reproduce this issue. I'm using Axios and it is working on the latest version.
Is the API key / dataset name correct? Based on the Forbidden
response, I think it is not.
@andrasbacsai -> Draining logs under a docker swarm config to Axiom seems to be broken....
It is also broken for me. no logs reaching axiom.