Related pages:

Your Rating:
Results:
PatheticBadOKGoodOutstanding!
0 rates

PCF

Pivotal Cloud Foundry (PCF) is an open-source cloud computing Platform as a Service (PaaS). Developers can develop, deploy, operate, and scale cloud-native applications for public and private clouds.

AppDynamics provides three tiles to support PCF 2.x (v2.0.7+) that are available on the Pivotal Network for download and install in a PCF foundation.

PKS

Pivotal Container Service or PKS is Pivotal's product for deploying and managing open-source Kubernetes. The Kubernetes monitoring that AppDynamics provides has been tested to work with PKS. Follow the instructions from Using Docker Visibility with Kubernetes for setting up container visibility within PKS. This daemonset.yaml example has been tested with kubectl in PKS. The yaml file contains a command that sets up a symbolic link. This symbolic link maps the location of the docker.sock file, expected by the AppDynamics Machine Agent, to the actual location on a PKS worker node.

AppDynamics Application Performance Monitoring for PCF

To simplify APM setup, the AppDynamics Application Performance Monitoring for PCF tile delivers a service broker to support an AppDynamics marketplace service. The Controller parameters are configured in the tile and automatically published to the marketplace when the tile is installed.

A PCF app can be bound to the marketplace service to consume the Controller credentials.

$ cf bind my-pcf-app my-appd-marketplace-service

Performing a push will utilize the integrated AppDynamics buildpack support to start the APM agent based on the parameters from the marketplace service and start sending performance metrics to the Controller.

$ cf push

The tile also installs the AppDynamics extension buildpack in the PCF environment. For more information on the buildpack support and language-specific workflows to enable APM, see the tile documentation.

AppDynamics Platform Monitoring for PCF

The AppDynamics Platform Monitoring for PCF tile provides visibility into the PCF platform where your AppDynamics-monitored applications are deployed. The tile deploys a Firehose Nozzle that collects various KPI metrics and publishes them to a Controller. The tile also deploys a Dashboard App that automatically creates KPI health rules and custom dashboards associated with the health rules. The Dashboard App allows you to monitor the health and capacity of one or more PCF foundations. For more information see the tile documentation

AppDynamics Application Analytics for PCF

The AppDynamics Application Analytics for PCF tile supports collecting Transaction Analytics in real-time from PCF apps to connect application performance, user experience, and business outcomes. The tile deploys an analytics agent in the PCF environment that forwards transaction analytics events from PCF apps to an AppDynamics Events Service. For more information see the tile documentation.

Deploy Using Pivotal Container Service (PKS)

Pivotal Container Service or PKS is Pivotal's product for deploying and managing open-source Kubernetes. The Kubernetes monitoring that AppDynamics provides has been tested to work with PKS. Follow the instructions from Monitoring Kubernetes for setting up container visibility within PKS.

Below is a daemonset.yaml example that has been tested with kubectl in PKS and contains a command to setup a symbolic link to map the location of the docker.sock file expected by the AppDynamics Machine Agent to the actual location on a PKS worker node.

Sample Daemonset

Here is an example YAML file to run Machine Agent as Daemonset across your Kubernetes nodes:

---
apiVersion: extensions/v1beta1
kind: DaemonSet
metadata:
  name: sim-k8s-agent
  namespace: default
spec:
  template:
    metadata:
      labels:
        name: appdynamics
    spec:
      containers:
      - env:
        - name: APPDYNAMICS_CONTROLLER_HOST_NAME
          value: "<controller-host-name>"
        - name: APPDYNAMICS_CONTROLLER_PORT
          value: "<controller-port>"
        - name: APPDYNAMICS_CONTROLLER_SSL_ENABLED
          value: "<true/false>"
        - name: APPDYNAMICS_AGENT_ACCOUNT_NAME
          value: "<account-name>"
        - name: APPDYNAMICS_AGENT_ACCOUNT_ACCESS_KEY
          value: "<access-key>"
        - name: APPDYNAMICS_SIM_ENABLED
          value: "true"
        - name: APPDYNAMICS_DOCKER_ENABLED
          value: "true"
        image: <machine-agent-image>
        name: sim-k8s-agent
        volumeMounts:
        - mountPath: /hostroot
          name: hostroot
          readOnly: true
        - mountPath: /var/run/docker.sock
          name: docker-sock
      volumes:
      - name: hostroot
        hostPath:
          path: /
          type: Directory
      - name: docker-sock
        hostPath:
          path: /var/run/docker.sock
          type: Socket
      restartPolicy: Always
---
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: cluster-read-all
rules:
  -
    apiGroups:
      - ""
      - apps
      - autoscaling
      - batch
      - extensions
      - policy
      - rbac.authorization.k8s.io
    resources:
    # everything except secrets
      - componentstatuses
      - configmaps
      - daemonsets
      - deployments
      - events
      - endpoints
      - horizontalpodautoscalers
      - ingress
      - jobs
      - limitranges
      - namespaces
      - nodes
      - pods
      - persistentvolumes
      - persistentvolumeclaims
      - resourcequotas
      - replicasets
      - replicationcontrollers
      - serviceaccounts
      - services
    verbs:
      - get
      - watch
      - list
  - nonResourceURLs: ["*"]
    verbs:
      - get
      - watch
      - list 
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: k8s-agent-readall-role-binding
subjects:
  - kind: ServiceAccount
    name: default
    namespace: default
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-read-all
---
  • No labels