[
https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIIDSB-23:
-------------------------------------
used the term datavirtualization, rather than dataintegration as
integration is already a primary term for syndesis.
I was trying to use what we maybe using in future with syndesis so that there for a single
monitoring solution.
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
I think this is fine, I see that is approach syndesis used. Only thing I want to
understand is if there are multiple pods with "datavirtualization" label, all of
them can be discovered and monitored by a single Prometheus system.
it is possible to separate this into just the prometheus example
I was not saying to dynamically change what is deployed as the previous example. I was
only thinking in terms of instructions and README with duplication of code/configuration
from previous example. I will provide updates to that.
I came across this article
https://www.callicoder.com/spring-boot-actuator-metrics-monitoring-dashbo...
where we could use micrometer with Teiid app and see if we can expose some of readymade
metrics.
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)