-
Notifications
You must be signed in to change notification settings - Fork 48
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
Java errors after enabling log collection in Jenkins #295
Comments
Hi @ricardojdsilva87 |
Hi @ricardojdsilva87 |
Hello @jose-manuel-almaza , |
Hi @ricardojdsilva87 |
Hello @jose-manuel-almaza , I did thought the test that you mentioned and assigned a port that is not configured on datadog (port 8126 configured on datadog and port 8127 configured on Jenkins), with that I get the following errors as it would be expected:
Thanks |
Hi @ricardojdsilva87 to help debug further, can you temporarily add a log recorder for the Datadog plugin? You can set the logger name to Additionally, can you try setting |
Hello @sarah-witt ,
Thanks |
@ricardojdsilva87 Thanks for the information. Is this log line from when |
Hello @sarah-witt , the |
@ricardojdsilva87 Can you confirm that you have a custom log source enabled for jenkins? And if so, what port is configured? https://github.com/jenkinsci/datadog-plugin#log-collection-for-agents |
Hello @sarah-witt , sorry for the late reply.
Also trying the connection to the outbound site where the logs are sent to datadog seems to be successfull By default the datadog agent collects all the logs from the running containers on the node. We needed to add only a custom configuration for the jenkins logs to parse the java stack traces so it won't appear as separate lines on the datadog portal.
Thanks |
Hi @ricardojdsilva87, sorry for the delay in response. In your agent status output you should have a log source for jenkins, if not then you will have to explicitly create the file according to these docs so the agent can listen for the TCP traffic from the plugin: https://github.com/jenkinsci/datadog-plugin#log-collection-for-agents. If the problem continues, do you mind creating a support ticket so that we can get more information to troubleshoot? Thanks! |
Thanks for the reply @sarah-witt , I'll post here the result of the new changes |
Hello we are having the following errors on Jenkins after enabling the log collection in Datadog plugin:
Tried to do a telnet on localhost 8126 and it works.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The agent should ship the logs to the central console
Configuration:
The casc configuration is the following:
The plugin is working correctly sending the information about the jobs into datadog (we are using the already existent Datadog dashboard to check) example:
On the Jenkins pipeline we are setting the following:
Also testing the connections on the UI seem to work correctly:
We are not seeing any kind of pipeline logs information being shipped to datadog.
Is there any kind of debugging we can do? Are some of the settings incorrect?
Also a question regarding the configuration:
If we set the collectLogs variable:true in the pipeline do we need to specify the option to collect logs globally? In this case if we disable the collect logs option globally and set via the pipeline we still aren't receiving the logs, but the error logs on Jenkins mentioned above stops
Environment and Versions:
Thanks for your help
The text was updated successfully, but these errors were encountered: