次の導入仕様は、上記の展開オプションの実装方法の具体例です。

• トランザクション分析：サイドカーまたはポッドを使用した導入仕様
• ログ分析：サイドカーまたはポッドを使用した導入仕様

トランザクション分析：サイドカーまたはポッドを使用した導入仕様

サイドカー

次の展開仕様では、2 つのコンテナを定義します。アプリケーションコンテナの flight-services と Docker Hub からの Analytics エージェント appd-analytics-agent です。

appd-analytics-agent エージェント側のコンポーネントのインストール。

サイドカーとして、Analytics エージェントは localhost で利用できます。

apiVersion: apps/v1
kind: Deployment
metadata:
  name: flight-services
spec:
  selector:
    matchLabels:
      name: flight-services
  replicas: 1
  template:
    metadata:
      labels:
        name: flight-services
    spec:
      containers:
      - name: flight-services
        image: <flight-services-docker-image>
        imagePullPolicy: IfNotPresent
        envFrom:
          - configMapRef:
              name: controller-info
        env:
        - name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
          valueFrom:
            secretKeyRef:
              key: appd-key
              name: appd-secret
        - name: APPDYNAMICS_AGENT_TIER_NAME
          value: flight-services
		
        ports:
        - containerPort: 8080
          protocol: TCP
        restartPolicy: Always
      - name: appd-analytics-agent
        envFrom:
        - configMapRef:
            name: controller-info
        env:
        - name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
          valueFrom:
            secretKeyRef:
              key: appd-key
              name: appd-secret
        - name: APPDYNAMICS_EVENTS_API_URL
          valueFrom:
            configMapKeyRef:
              key: EVENT_ENDPOINT
              name: controller-info
 		- name: EVENT_ENDPOINT
            value: events end point
        - name: APPDYNAMICS_EVENTS_CERTIFICATE_PATH
            value: <Path of root certificate in container> e.g. /certs/root_ca.crt 
        - name: APPDYNAMICS_AGENT_GLOBAL_ACCOUNT_NAME
          valueFrom:
            configMapKeyRef:
              key: FULL_ACCOUNT_NAME
              name: controller-info
        image: docker.io/appdynamics/analytics-agent:24.10.0-595-debian
        imagePullPolicy: IfNotPresent
        ports:
        - containerPort: 9090
          protocol: TCP
        resources:
          limits:
            cpu: 200m
            memory: 900M
          requests:
            cpu: 100m
            memory: 600M
...

controller-infoappd-secretコントローラ情報 YAML ファイル。Secret を作成するコマンド。

ポッド

次のデプロイメント仕様は、同じ flight-services flight-services APPDYNAMICS_ANALYTICS_HOST APPDYNAMICS_ANALYTICS_PORT 分析プロキシ用です。

apiVersion: apps/v1
kind: Deployment
metadata:
  name: flight-services
spec:
  selector:
    matchLabels:
      name: flight-services
  replicas: 1
  template:
    metadata:
      labels:
        name: flight-services
    spec:
      containers:
      - name: flight-services
        image: <flight-services-docker-image>
        imagePullPolicy: IfNotPresent
        envFrom:
          - configMapRef:
              name: controller-info
       env:
        - name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
          valueFrom:
            secretKeyRef:
              key: appd-key
              name: appd-secret
        - name: APPDYNAMICS_AGENT_TIER_NAME
          value: flight-services
        - name: APPDYNAMICS_ANALYTICS_HOST
          value: analytics-proxy
        - name: EVENT_ENDPOINT
            value: events end point
        - name: APPDYNAMICS_EVENTS_CERTIFICATE_PATH
            value: <Path of root certificate in container> e.g. /certs/root_ca.crt
        - name: APPDYNAMICS_ANALYTICS_PORT
          value: "9090"
        ports:
        - containerPort: 8080
          protocol: TCP
        volumeMounts:
        - mountPath: /certs       # Added a new volume mount for /certs, which corresponds to the 		    location in the container where the certificate will be accessible.
           name: certs-volume
      restartPolicy: Always
      volumes:
        - name: certs-volume
            hostPath:
              path: <Path on the host where the certificate resides, formatted for the container's host OS> e.g. /mnt/c/User/NewUser/certs       
              type: Directory
...

ログ分析：サイドカーまたはポッドを使用した展開仕様

サイドカーのインストール

apiVersion: apps/v1
kind: Deployment
metadata:
  name: two-container-deployment
spec:
  selector:
    matchLabels:
      app: two-container-app
  template:
    metadata:
      labels:
        app: two-container-app
    spec:
      containers:
      - name: analyticsagent
        image: docker.io/appdynamics/analytics-agent:24.10.0-595-debian
        imagePullPolicy: Never
        ports:
        - containerPort: 9090
        env:
		- name: APPDYNAMICS_CONTROLLER_HOST_NAME
			value: controller host name
		- name: APPDYNAMICS_CONTROLLER_SSL_ENABLED
			value: "false"
		- name: APPDYNAMICS_CONTROLLER_PORT
			value: controller port
		- name: APPDYNAMICS_AGENT_ACCOUNT_NAME
			value: account name
		- name: APPDYNAMICS_AGENT_APPLICATION_NAME
			value: applicant name
		- name: APPDYNAMICS_AGENT_GLOBAL_ACCOUNT_NAME
			value: global account name
		- name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
			value: account access key
		- name: EVENT_ENDPOINT
			value: events end point 
		- name: APPDYNAMICS_EVENTS_CERTIFICATE_PATH
          value: <Path on the machine (Windows-specific with backslashes)>:<Path in the container (Windows-specific with backslashes)>
        volumeMounts:
        - mountPath: /opt/appdynamics/app-logs
          name: shared-storage
      - name: travelapp
        image: travel-debian:latest
        imagePullPolicy: Never
        env:
		- name: APPDYNAMICS_CONTROLLER_HOST_NAME
			value: controller host name
		- name: APPDYNAMICS_CONTROLLER_SSL_ENABLED
			value: "false"
		- name: APPDYNAMICS_CONTROLLER_PORT
			value: controller port
		- name: APPDYNAMICS_AGENT_ACCOUNT_NAME
			value: account name
		- name: APPDYNAMICS_AGENT_APPLICATION_NAME
			value: applicant name
		- name: APPDYNAMICS_AGENT_GLOBAL_ACCOUNT_NAME
			value: global account name
		- name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
			value: account access key
		- name: EVENT_ENDPOINT
        volumeMounts:
        - mountPath: /opt/appdynamics/analytics-demo/appAgent/ver24.10.0-595/logs/Travel_one-pod-two-cntr-Node
          name: shared-storage
      volumes:
        - name: shared-storage
          emptyDir: {}

---
apiVersion: v1
kind: Service
metadata:
  name: service-analytics-agent
spec:
  selector:
    app: two-container-app
  ports:
  - protocol: TCP
    port: 9090
    targetPort: 9090
  type: NodePort

ポッドのインストール

apiVersion: v1
kind: Pod
metadata:
  name: agent-pod
  namespace: ns1
  labels:
    app: agent-container
spec:
  containers:
    - name: aa-container
      image: docker.io/appdynamics/analytics-agent:24.10.0-595-debian
      imagePullPolicy: Never
      ports:
        - containerPort: 9090
      env:
        - name: APPDYNAMICS_CONTROLLER_HOST_NAME
            value: controller host name
        - name: APPDYNAMICS_CONTROLLER_SSL_ENABLED
            value: "false"
        - name: APPDYNAMICS_CONTROLLER_PORT
            value: controller port
        - name: APPDYNAMICS_AGENT_ACCOUNT_NAME
            value: account name
        - name: APPDYNAMICS_AGENT_APPLICATION_NAME
            value: applicant name
        - name: APPDYNAMICS_AGENT_GLOBAL_ACCOUNT_NAME
            value: global account name
        - name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
            value: account access key
        - name: EVENT_ENDPOINT
            value: events end point
          - name: APPDYNAMICS_EVENTS_CERTIFICATE_PATH
            value: <Path of root certificate in container> e.g. /certs/root_ca.crt
      volumeMounts:
        - name: shared-volume
          mountPath: /opt/appdynamics/app-logs
        - mountPath: /certs       # Added a new volume mount for /certs in the analyticsagent container, which corresponds to the location in the container where the certificate will be accessible.
           name: certs-volume
  volumes:
    - name: shared-volume
      persistentVolumeClaim:
        claimName: shared-data-pvc
    - name: certs-volume
        hostPath:
          path: <Path on the host where the certificate resides, formatted for the container's host OS> e.g. /mnt/c/User/NewUser/certs       
          type: Directory