[teiid-issues] [JBoss JIRA] (TEIIDSB-40) define logging options
Steven Hawkins (Jira)
issues at jboss.org
Wed Feb 20 16:21:00 EST 2019
[ https://issues.jboss.org/browse/TEIIDSB-40?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13698492#comment-13698492 ]
Steven Hawkins commented on TEIIDSB-40:
---------------------------------------
It's still a PITA to bring up the EFK stack on minishift - https://github.com/minishift/minishift/issues/2207 https://github.com/openshift/origin-aggregated-logging/issues/882 (or even openshift from other posts). --logging is not allowed as an experimental nor regular flag up to 3.11, and the ansible setup method fails for a variety of reasons.
There's mention that things will be better with v4...
> define logging options
> ----------------------
>
> Key: TEIIDSB-40
> URL: https://issues.jboss.org/browse/TEIIDSB-40
> Project: Teiid Spring Boot
> Issue Type: Sub-task
> Components: OpenShift
> Reporter: Steven Hawkins
> Assignee: Ramesh Reddy
> Priority: Major
> Fix For: 1.0.3
>
>
> It looks like the preferred mechanism with spring boot is to use:
> https://github.com/logstash/logstash-logback-encoder
> This should make it easier for the aggregate container logging to use the container logs. I'll validate this and update the example appropriately - which we could create a parallel to prometheus for the logging stack / kibana.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
More information about the teiid-issues
mailing list