Before you post: Your responses to these questions will help the community help you. Please complete this template if you’re asking a support question. Don’t forget to select tags to help index your topic!
Am able to ship wildfly server.log to ELK stack using above jar (jboss-logmanager-ext) and able to see in kibana.
I do have my Graylog (v5) stack running but i dont know how to send the wildfly log that is currently being shipped to ELK to our Graylog stack.
2. Describe your environment:
Linux (RHEL 8)
graylog v5.2 followed steps as per graylog site.
Service logs, configurations, and environment variables:
using wildfly server.log to be shipped by using steps given in URL for wildfly (in URL shared above)
3. What steps have you already taken to try and solve the problem?
Graylog stack v5.2 is up running with opensearch and mongodb. But now i want to ship wildfly log to graylog. Currently wildflyl logs are being shipped to ELK stack.
4. How can the community help?
Please advise and share the guidelines/pointer/steps that i can use to ship wildfly logs to graylog stack.
Actually am doing the same - placed the required jar(s) in the modules path. added that module jars to standalone.xml subsystem using jboss-cli commands - outcome was success. But am still not able to understand the cause of error when i tried to add root-logger via command:
In the URL you have given - person also doing the same but didnt got this exception - instead he was missing to add jar under the module path.
the only difference i found, am using wildfly v14.0 and he is using wildfly v19.0. For some reason product team has not upgraded to higher version of wildfly yet. so trying to check if we can ingest the log of wildfly v14 to graylog.