fabric8io / agent-bond Goto Github PK

Hi Roland,
the links above are broken. Are the samples still available somewhere?
Cheer Christian

to disable this variable, which is useful if this is set e.g. hardcoded in the image.

See also fabric8io/fabric8-devops#799 where this became an issue.

The URL to the docker image on docker hub is broken

We are using OpenShift 3.4, operated by AppAgile/Deutsche Telekom for a customer.

Our application is a Spring Boot application which already contains Jolokia. The base image is

        from:
          kind: ImageStreamTag
          namespace: 'openshift'
          name: 'fis-java-openshift:1.0-15'

Jolokia is bound to a management port 8442 w/ plain http and happily responds to a local request (via Terminal session to the POD/container) using curl localhost:8442/jolokia:

{"request":{"type":"version"},"value":{"agent":"1.3.6","protocol":"7.2","config":{"agentId":"10.1.11.233-1-20b54cfe-servlet","agentType":"servlet"},"info":{}},"timestamp":1502286997,"status":200}

However when we try to connect via Java Console from the Web UI we get an error message:

Error: 'tls: oversized record received with length 20527'
Trying to reach: 'https://10.1.11.233:8442/jolokia/?maxDepth=7&maxCollectionSize=500&ignoreErrors=true&canonicalNaming=false'

I have already tried several combinations of AB_JOLOKIA_... environment variables in the deployment configuration (cf. https://access.redhat.com/documentation/en-us/red_hat_jboss_middleware_for_openshift/3/html-single/red_hat_java_s2i_for_openshift/). None of them made a difference, TLS seems to be always used for access.

Regs
Gerd

The reason is that jolokia{{a,b,c}} gets shell-evaled to jolokia{a} jolokia{b} jolokia{c}. So when building up JAVA_OPTS for some startup scripts where at the end JAVA_OPTS gets evalved (like for tomcat startup scripts), this will bork everything.

Any idea for a good delimiter pair ? Should be shell safe, prefereable two different chars so its easier to parse and seldom used to avoid to implement escaping).

A simple agent which opens a port and answer requests for readiness with an "OK" or "NOK" on a plain http requests. How this check can be performed internally and how it can be configured is still open. It could be based on

• the existance of an MBean
• the outcome of an MBean
• calling an internal, static method
• ....

Same for the liveness.

This should be configurable from the outside (the same way the other agents can be configured). The functionality should be very limited (i.e. not sth replacing Jolokia) so that it can be used by everyone without authentication.

Allow Jolokia port to be specified as env variable like -javaagent:./agent-bond-agent.jar=jolokia{{port=${env:MY_JOLOKIA_PORT}}. currently specifying this way throws NumberFormatException

Agent-bond should contain some standard whitelists for common backend.

One of them should be camel for which a set of standard metrics should be collected.

All the came metrics are here: https://github.com/apache/camel/tree/master/camel-core/src/main/java/org/apache/camel/api/management/mbean

The ManagedPerformanceCounterMBean is a good starting point for this whitelist, but also ManagedRouteMBean has a load() metrics for getting the load on a route.