-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In self-managed elastic, the agent's logs are not visible in kibana #3415
Comments
@michel-laterman I upgraded to 8.14.1 but the problem persists. Can you help me? |
The data streams have data in them, what logs are you expecting to see that are missing, and where you are looking? This is probably better suited to being a post in https://discuss.elastic.co/c/elastic-stack/elastic-agent |
I want to see the fleet-server and agent logs in [Monitor Elastic Agents | Fleet and Elastic Agent Guide [8.14] | Elastic 3](url) But now it's empty |
I took a quick look at the diagnostics you provided, nothing in the configs stuck out to me. The logs also didn't have anything in the way of errors (nothing to indicate that it failed to connect to ES), the only thing i wound was a warning and inputs loading messages from filestream-monitoring, but i'm not sure if this is expected behaviour.
Do any logs show up in the discover view? Do the indcies/datastreams show up ion the management views? |
|
Hello, everyone.
I set up a cluster with three Linux servers using elastic version 8.11.1. The information for each server is as follows: Server 1 ip-10.150.3.12 elasticsearch+kibana, server 2 ip-10.150.3.15 elasticsearch+elastic agent, and server 3 ip 10.150.3.17 elasticsearch+fleetserver. They are self-managed clusters and are configured with TSL, using self-generated certificates. When installing fleetserver and agent, I didn't do any configuration for Elasti-agent.yml, just tar and install. fleetserver and agent are up and running, but in kibana, don't see logs. May I ask where I need to troubleshoot the problem next?
I uploaded my diagnostics log at the end, hoping to help with this problem. Thank you so much!
elastic-agent-diagnostics-2024-04-01T08-21-38Z-00.zip
The text was updated successfully, but these errors were encountered: