[
https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIIDSB-23:
---------------------------------------
For convenience moving the pr comment here:
* used the term datavirtualization, rather than dataintegration as integration is already
a primary term for syndesis.
* discovery of the pod is based upon the label (not annotation)
syndesis.io/type=datavirtualization - this can of course be changed, but needs to be done
on both the deployment config for our image and in the prometheus config
* metric_relabel_configs is a bit tricky. what syndesis has is redundant - a single keep
causes everything that does not match to be dropped. keep also makes it hard to merge
keep rules as you need to merge the regex. Note that theirs uses the context type as a
prefix - which does not of course match our type labels (currently cache and runtime).
We'll likely need to come up with better strategy here if we are going to share a
prometheus instance.
* We are following syndesis conventions. The metrics have java style names,
org.teiid.xxx, but . is automatically replaced with _ in the actual name - likely to make
for easier regex matching.
* it is possible to separate this into just the prometheus example if it's based upon
a new deployment config file that references the image built by rdbms_example and overlays
the export configuration via a configmap, rather than using fabric8 include
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)