[teiid-issues] [JBoss JIRA] (TEIIDSB-23) Document image generation options
[
https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-23:
---------------------------------------
Teams as in the virtualization developer? or overall Integration
product?
Product - such that there is a known recommended way of creating and federating
instances.
Looking at our image, we are not exporting our metrics. The base image
https://hub.docker.com/r/fabric8/s2i-java/ has some well defined options for jolokia, but
bakes in the prometheus opts and config file:
https://github.com/fabric8io-images/s2i/blob/master/java/images/rhel/prom...
(see the exec java
javaagent:/opt/prometheus/jmx_prometheus_javaagent.jar=9779:/opt/prometheus/prometheus-config.yml)
So need to determine if we should be overriding / contributing to the prometheus config or
if we should just use jolokia for now.
Document image generation options
---------------------------------
Key: TEIIDSB-23
URL: https://issues.jboss.org/browse/TEIIDSB-23
Project: Teiid Spring Boot
Issue Type: Task
Reporter: Steven Hawkins
Priority: Major
Fix For: Q119
We need to document / validate all relevant image options:
- inclusion of agent bond or other mechanism for jmx exposure to prometheus. There may
also be related service annotations
- annotations for 3scale for rest and openapi exposure of odata
- any common config options - disk buffer memory, max active plans / engine threads /
connection pool sizes. Ideally the buffer manager heap should auto-configure and we
should probably always use off-heap for the fixed memory buffer.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)