Open topic with navigation

TIBCO ActiveMatrix® Service Grid - Container Edition 1.0.0

# Sample Kubernetes YAML File for Deploying Application Monitor

Sample Kubernetes YAML files for deploying Application Monitor are at `amsgce-runtime-<version>/samples/kubernetes/Application_Monitor.`

Update the following Kubernetes object specification (.`yaml`) files for Application Monitor:

- `amxce_authorization.yaml` - A `ClusterRoleBinding` for binding roles to the user.
- `tea-agent.yaml -` Kubernetes deployment YAML file to deploy Application Monitor agent`.`

- tea-server.yaml - Kubernetes deployment YAML file to deploy TEA Server`.`

In the sample YAML files, specify the image tag of TEA Server Docker image (<tea-server-docker-image>) and Application Monitor agent (<amxceteaagent-image-name>).

Environment Variables

You can use the following environment variables to configure Application Monitor:

Environment Variable | Description
--- | ---
tea_server_url (Required) | URL of a TIBCO Enterprise Administrator Server running in the cluster. This is required to connect and autoregister Application Monitor agent with TEA Server. Example:`http://tea-service:8777/tea`
amxce_tea_agent_port (Optional) | Application Monitor agent port. Default: 7073
amxce_tea_agent_name | Application Monitor agent display name. The name is displayed in the Application Monitor UI.
amxce_swaggerui (Optional) | The externally hosted Swagger UI URL. If specified, then in the Application Monitor, you can open REST service in the Swagger UI by clicking the link provided in the Endpoints tab.
`amxce_tea_agent_shutdown_port` (Optional) | This is used to set shutdown port of TIBCO Enterprise Administrator server.
`tibco.amxce.reload.interval.ms` | Time interval in which Application Monitor synchronizes with Kubernetes API server and checks ActiveMatrix Service Grid - Container Edition nodes for active connection. It runs in scheduled thread and thread name starts with "amxce-reload-" Default: 300000 ms (5 min) Note: For small scale setup, set this parameter to lower value.
`tibco.amxce.agent.node.connect.max.thread` | This property specifies the number of running threads when Application Monitor connects to AMXCE Nodes. The thread name starts with "amxce-hpa-". Default: 5
`tibco.amxce.agent.node.connect.timeout.ms` | This is the maximum time interval for which Application Monitor waits for creating connection to AMXCE Node. After connection timeout, the Node is displayed as unreachable. Application Monitor retries to connect to unreachable Node after time interval value specified in the`tibco.amxce.reload.interval.ms.` Default: 5000 ms (5 seconds)

Note: Communication between Application Monitor agent and ActiveMatrix Service Grid - Container Edition application container is done by using JMX. Communication between Application Monitor agent and application pods with SSL enabled is not supported in ActiveMatrix Service Grid - Container Edition 1.0.0.

If you are using ClusterRole resource, you must provide "replicasets" access to the ClusterRole. This is required to get the deployment name and desired state of the pod. For more information about using ClusterRole for authorization, see Kubernetes documentation.

Example:

    kind: ClusterRole
    apiVersion: rbac.authorization.k8s.io/v1
    metadata:
      name: amxcecluster-role
    rules:
    - apiGroups: ["", "extensions", "apps"]
      resources: ["pods"*,"replicasets"*]
      verbs: ["get", "list", "watch"]

Copyright © 2020-2021. TIBCO Software Inc. All Rights Reserved.