[teiid-issues] [JBoss JIRA] (TEIIDSB-23) Document image generation options

[Steven Hawkins (Jira)]

    [ https://issues.jboss.org/browse/TEIIDSB-23?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13691928#comment-13691928 ] 

Steven Hawkins commented on TEIIDSB-23:
---------------------------------------

syndesis defines their Prometheus instance with https://github.com/syndesisio/syndesis/blob/master/install/generator/06-syndesis-prometheus.yml.mustache note that it has the relabel section defining what metrics to keep.  This is documented at https://github.com/syndesisio/syndesis/blob/bfd8d149c33ccc4856f8aa18e776bce36d83260e/doc/managing_environments/topics/external_prometheus.adoc  We need to be added to the keep context.

Then on our image we need to annotate that scraping should  be performed using the prometheus.io/scrape annotation:
https://github.com/syndesisio/syndesis/blob/6d680cf61441d44722a5f7d807bbf0fa4c04c9c7/install/generator/04-syndesis-db-metrics.yml.mustache#L51

> 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)