What are the steps for installing OTel Collector as a sidecar in ECS Fargate to monitor applications?  This article provides step-by-step instructions and sample configuration files you can use to install an OTel collector as a sidecar in ECS Fargate, so you can monitor applications.   It includes two alternatives for configuring your application to use OpenTelemetry: (a) by modifying your existing application image, or (b) by injecting the OTel Java agent into your container.  In this article... Installation instructions  | Resources   Installation instructions Go to AppDynamics Cloud Tenant UI > Configure > Kubernetes & APM and generate the agent credentials. Download the file or copy the snippet that includes clientId, clientSecret, endpoint, and tokenUrl.    Create a collector-values.yaml file. Replace content as follows:  REPLACE: WITH:  <<client-id>>  <<client-secret>>  <<token-url>>  Replace with the values from step 1.  <<tenant-url>>  Replace with the actual tenant URL  processors: batch: timeout: 10s send_batch_size: 8192 receivers: otlp: protocols: grpc: http: exporters: logging: #loglevel: debug verbosity: detailed otlphttp: logs_endpoint: https://<<tenant-url>>/data/v1/logs metrics_endpoint: https://<<tenant-url>>/data/v1/metrics traces_endpoint: https://<<tenant-url>>/data/v1/trace auth: authenticator: oauth2client extensions: oauth2client: client_id: <<client-id>> client_secret: <<client-secret>> token_url: <<token-url>> service: pipelines: traces: receivers: [otlp] processors: [batch] exporters: [otlphttp, logging] metrics: receivers: [otlp] processors: [batch] exporters: [otlphttp] logs: receivers: [otlp] processors: [batch] exporters: [otlphttp] extensions: [oauth2client] telemetry: logs: level: "debug" In the same directory as the collector-values.yaml file, create an otelcollector-dockerfile file with the following content:  # Sample Dockerfile for the OpenTelemetry Contrib Collector SideCar Container. # This is provided for illustration purposes only, for full details # please consult the product documentation: https://docs.appdynamics.com/ FROM debian # Install Required Packages RUN apt-get update && apt-get -y install curl && apt-get -y install openssl && apt-get -y install bash && apt-get clean # Create a work directory to copy the Otel Collector artifacts ENV APP_HOME /opt/otel RUN mkdir -p ${APP_HOME} WORKDIR ${APP_HOME} # Download and extract Contrib version of Otel Collector artifacts to the work directory RUN curl -L0 https://github.com/open-telemetry/opentelemetry-collector-releases/releases/download/v0.75.0/otelcol-contrib_0.75.0_linux_386.tar.gz --output otelcol-contrib_0.75.0_linux_386.tar.gz RUN tar -xvf otelcol-contrib_0.75.0_linux_386.tar.gz RUN rm -rf otelcol-contrib_0.75.0_linux_386.tar.gz # Copy the config file for Otel Collector to work directory COPY collector-values.yaml ${APP_HOME} # Expose the /opt/otel directory as a shared volume #VOLUME ["/opt/otel"] # Expose ports EXPOSE 4317 4318 8888 8889 13133 55679 CMD ${APP_HOME}/otelcol-contrib --config ${APP_HOME}/collector-values.yaml Build, tag, and push the docker image. Then, replace <repository-url> as shown below.  docker build -t otel-collector-contrib:latest --no-cache -f otelcollector-dockerfile . docker tag otel-collector-contrib:latest <repository-url>/otel-collector-contrib:latest docker push <repository-url>/otel-collector-contrib:latest Configure your application to use OpenTelemetry using one of two ways: • Modify your existing application image • Inject OpenTelemetry Java Agent into your application as an init container  Option 1 | Configure your app to use OTel by modifying the existing application image  Modify your existing application image and add javaagent:path/to/opentelemetry-javaagent.jar to your JVM’s startup arguments.  Download opentelemetry-javaagent.jar from Releases of the opentelemetry-java-instrumentation repo. The JAR file contains the agent and all automatic instrumentation packages. Add the JAR file to your application build file. See the build file below for reference.   FROM openjdk:17-jdk-slim-buster RUN apt-get -y update && apt-get -y install curl LABEL version="1.0.1" RUN mkdir -p /opt/app/otelincsaas WORKDIR /opt/app/otelincsaas # Copy Jar file. COPY otelincsaas/ /opt/app/otelincsaas/ COPY otelincsaas/opentelemetry-javaagent.jar /opt/app/otelincsaas/ RUN chmod -R 755 /opt/app/otelincsaas ENTRYPOINT ["java", "-javaagent:/opt/app/otelincsaas/opentelemetry-javaagent.jar", "-jar","otel-in-csaas-1.0.0.jar"] Add -javaagent:<path-to-opentelmetry-jar>/opentelemetry-javaagent.jar to your startup command. Next step Option 2 | Configure your app to use OTel by injecting the (OTel) Java Agent into your application as an init container Create a Docker file. otelagent-dockerfile # Sample Dockerfile for the OpenTelemetry Agent SideCar Container. # This is provided for illustration purposes only, for full details # please consult the product documentation: https://docs.appdynamics.com/ FROM debian # Install Required Packages RUN apt-get update && apt-get -y install curl && apt-get -y install openssl && apt-get -y install bash && apt-get clean # Create a work directory to copy the Otel Agent artifacts ENV APP_HOME /opt/otel RUN mkdir -p ${APP_HOME} WORKDIR ${APP_HOME} # Download and extract Otel Agent artifacts to the work directory RUN curl -L0 https://github.com/aws-observability/aws-otel-java-instrumentation/releases/download/v1.24.0/aws-opentelemetry-agent.jar --output aws-opentelemetry-agent.jar # Expose the /opt/otel directory as a shared volume VOLUME ["/opt/otel"] CMD tail -f /dev/null Build, tag, and push the Docker image. Replace <repository-url> accordingly. Build, Tag, and Push docker build -t otel-java-agent:latest --no-cache -f otelagent-dockerfile . docker tag otel-java-agent:latest <repository-url>/otel-java-agent:latest docker push <repository-url>/otel-java-agent:latest  At this stage, we have images for the: application otel-collector otel-agent Create a task definition in your ECS Fargate cluster and deploy the images. A ADD A CONTAINER FOR:   otel-java-agent Name: otel-java-agent  Image URL: <repository-url>/otel-java-agent:latest  Essential Container: No  otel-collector-contrib   Name: otel-collector-contrib  Image URL: <repository-url>/otel-collector-contrib:latest  Essential Container: Yes  <your application> Name: <application container name here>  Image URL: Application Image  Essential Container: Yes  Set the other details according to your Application.  Set the environment variables in the following table, along with others, if any.  Environment Variables Template: KEY VALUE TYPE VALUE OTEL_SERVICE_NAME  value Name of the Service  OTEL_RESOURCE_ATTRIBUTES  value service.namespace=name of the application  JAVA_TOOL_OPTIONS  value -javaagent:/opt/otel/aws-opentelemetry-agent.jar  OTEL_LOGS_EXPORTER  value otlp  OTEL_TRACES_EXPORTER  value otlp OTEL_EXPORTER_OTLP_INSECURE  value true  OTEL_PROPAGATORS  value tracecontext,baggage,b3  Edit the task definition in JSON format. For your application container, add the following properties and create a new task definition. "volumesFrom": [ { "sourceContainer": "otel-java-agent" } ], "dependsOn": [ { "containerName": "otel-java-agent", "condition": "START" } ] Deploy the service. Resources The  opentelemetry-javaagent.jar  is available in "Releases",  opentelemetry-java-instrumentation ... View more

Table of Contents Overview Prerequisite How do I delete a Collector?   Overview The Database Collector is the process that runs within a Database Agent to collect performance metrics about your database instances and database servers. To enable the Database Agent to collect data, you must add and configure a Database Collector for each database instance that you want to monitor. See Add Database Collectors. Though many Collector configuration details can be edited, its database platform type can't be changed. So, if you've chosen the wrong database type, you'll have to add a new Collector with the right type. You'll want to delete the incorrect one. You may also want to delete the Collector for an unused or outdated database in order to free its license for other use. Once a Collector is deleted, it can't be restored. Its data will also be deleted.   Prerequisite To delete the database collector, you must have a role with the Can Delete All Collectors permission. How do I delete a Collector? Click Databases in the top navigation. Then click Configuration in the left navigation and click Collectors.   From the list of Collectors, select the Database Collector you want to delete.  Confirm your selection, since you won't be able to restore the database or its data after you delete.  Click the Delete button. In the modal confirmation message, click OK. The collector you selected will be deleted.           ... View more

How do I resolve problems signing in to my v4.5x Controller via SAML? After upgrading the Controller to v4.5.x, you may encounter an issue where the SAML authentication request fails for accounts that use Active Directory Federation Services (ADFS) SAML. As a result, you may experience problems logging in via SAML to your Controller. HAVEN'T UPGRADED YET? The Solution section below can help ensure that your users avoid this problem after upgrading. In this article... Symptoms Reason Solution Symptoms If you recently upgraded a SaaS Controller and use ADFS SAML, you will see a generic 400 error in your Controller UI when trying to log in. If you have an on-prem Controller, you will see the following error in the Controller server.log: [#|2018-11-29T15:42:57.360-0800|SEVERE|glassfish 4.1|com.singularity.ee.controller.servlet.SAM LAuthenticationServlet|_ThreadID=75;_ThreadName=http-listener-1(13);_TimeMillis=1543534977360; _LevelValue=1000;|Error while processing SAML Authentication Response com.onelogin.saml2.exception.ValidationError: No name id found in Document. at com.onelogin.saml2.authn.SamlResponse.getNameIdData(SamlResponse.java:466) at com.onelogin.saml2.authn.SamlResponse.getNameId(SamlResponse.java:480) at com.onelogin.saml2.Auth.processResponse(Auth.java:527) at com.onelogin.saml2.Auth.processResponse(Auth.java:557) at com.appdynamics.platform.services.auth.impl.resource.SamlAuthenticationResourceImpl.consumeSAMLAuthenticationResponseInternal(SamlAuthenticationResourceImpl.java:206) at com.appdynamics.platform.services.auth.impl.resource.SamlAuthenticationResourceImpl.consumeSAMLAuthenticationResponse(SamlAuthenticationResourceImpl.java:162) at com.appdynamics.controller.mds.auth.MdsSamlAuthResourceImpl.consumeSAMLAuthenticationResponse(MdsSamlAuthResourceImpl.java:59) at com.singularity.ee.controller.servlet.SAMLAuthenticationServlet.doPost(SAMLAuthenticationServlet.java:262) at javax.servlet.http.HttpServlet.service(HttpServlet.java:707) at javax.servlet.http.HttpServlet.service(HttpServlet.java:790) at org.apache.catalina.core.StandardWrapper.service(StandardWrapper.java:1682) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:344) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:214) at com.singularity.ee.controller.servlet.RequestOriginMarkingFilter.lambda$doFilter$0(RequestOriginMarkingFilter.java:37) at com.appdynamics.platform.RequestOrigin.runAs(RequestOrigin.java:65) Reason As part of our improvements around SAML 2.0 authentication in the v4.5 release, our SAML implementation now requires a NameID assertion for Microsoft ADFS. If your configuration has not been updated to include this prior to upgrading to v4.5, you may encounter the error above. Solution To resolve this, add the NameID as the Outgoing Claim Type in your claim rule. You can map NameID with any unique ID (SAM-Account-Name, email, or UPN etc.). Follow the steps below prior to upgrading your Controller. 1. From your ADFS Console, select the “Relying Party Trusts” folder. 2. Select your trust for AppDynamics and right-click on it.   3. Choose “Edit Claim Issuance Policy…” 4. On the Issuance Transform Rules screen, select your AppDynamics rule and click the “Edit Rule…” button. 5. In the Edit Rule dialog, either add a new unique identifier (e.g., SAM-Account-Name) or edit the existing unique identifier (e.g., SAM-Account-Name) and map it to the Outgoing Claim Type “Name ID.” Add a new unique attribute Edit an existing attribute 6. Save your work. 7. Test to ensure that the authentication succeeds. Instructions last updated: 2/27/19 ... View more