[JBoss JIRA] (TEIID-5633) Configure to build on travis
by Van Halbert (Jira)
Van Halbert created TEIID-5633:
----------------------------------
Summary: Configure to build on travis
Key: TEIID-5633
URL: https://issues.jboss.org/browse/TEIID-5633
Project: Teiid
Issue Type: Task
Components: Build/Kits
Affects Versions: 12.x
Reporter: Van Halbert
Assignee: Steven Hawkins
Add the travis.yml file to configure to build on travis
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months
[JBoss JIRA] (TEIID-5620) Provide flattened jmx metrics
by Steven Hawkins (Jira)
[ https://issues.jboss.org/browse/TEIID-5620?page=com.atlassian.jira.plugin... ]
Steven Hawkins commented on TEIID-5620:
---------------------------------------
>From https://github.com/prometheus/jmx_exporter compositedata is fine, it just requires some additional keys in the export definition. I'll test that out as well. It likely means that we'll keep the existing admin/jmx bean structures and only add flattened values for the most important metrics.
> Provide flattened jmx metrics
> -----------------------------
>
> Key: TEIID-5620
> URL: https://issues.jboss.org/browse/TEIID-5620
> Project: Teiid
> Issue Type: Quality Risk
> Components: Server
> Reporter: Steven Hawkins
> Assignee: Steven Hawkins
> Priority: Major
> Fix For: 12.1
>
>
> Providing JMX metrics via jolokia to Prometheus does not work well with complex types. We are providing several metric sets - engine stats, worker pool stats, requests, etc. as beans which needs to be flattened. Simple parameters are ok to the metrics methods, but simple results are required.
> We need to make sure that at least statistics are available on:
> * number of plans waiting to be processed - this will be a primary metric for determining horizontal scale out
> * amount /%of buffer memory used - this will be a primary metric for determining if pods need to be allocated with more memory/disk
> Ideally alerting could be available on percent utilization - but we could also add a metric such as out of disk count to provide a hard count of exceptional conditions.
> It's assumed that cpu utilization will be monitored from the pod itself - which will be a primary metric for determining if pods should be allocated with more cpu resources.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
5 years, 10 months