question

anthony a. avatar image
anthony a. asked ·

CA and OneAgentOperator in kubernetes

I have a question about OneAgent Operator. In my company we have CA(in dockerfile), when we build the container, CA deploy with the container. The OneAgent Operator works totally different. Can it work both technologies? CA injected in the microservice and Operator works in the cluster and de nodes.

oneagentauto-detectionkubernetestechnologies
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

1 Answer

Sebastian K. avatar image
Sebastian K. answered ·

It is highly not recommended to use dynatrace with other monitoring solutions. Even if it will work it may produce ovehead for microservices. You can always not use an operator but application only monitoring and pick some of containers that will have attached Oneagent on runtime, some of them can be still in CA if you want to compare results. But keeping working them both itn’t good idea.

Sebastian

2 comments Share
10 |2000000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 50.0 MiB each and 250.0 MiB total.

do you have any documentation about this? What is the impact? I know Dynatrace works deep monitoring in a docker container but CA IBM building the agent inside the container(dockerfile) and the deploy is totally different, while dynatrace works as operator, CA is monitoring when container deployment. Maybe the impact be in code execution for example

0 Likes 0 · ·

You can deploy dynatrace in the same way, but deployment model doesn't change the final result. Both technologies are injected inside container and collecting transactions and metrics. There are no documentation for this because it is not supported by CA and Dynatrace as well. As I said, it may work, but you will never now what impact you can have and what can go wrong.

Sebastian

0 Likes 0 · ·

Space Topics

mobile monitoring dotnet synthetic monitoring reports iis chat kubernetes servicenow amazon web services mysql mainframe rest api errors cassandra dashboard oneagent sdk cmc application monitoring openkit smartscape request attributes monitoring developer community user tagging log monitoring services ufo syntheticadvisory activegate ip addresses auto-detection high five award oracle hyperion webserver uem usql iib test automation license web performance monitoring ios news migration management zones index ibm mq web services custom event alerts notifications sso host monitoring knowledge sharing reports browser monitors java hybris sap vmware maintenance window user action naming javascript appmon ai synthetic classic availability tipstricks automation extensions diagnostic tools session replay permissions davis assistant faq documentation problem detection http monitors server easytravel apdex aws-quickstart network docker tags and metadata cloud foundry google cloud platform synthetic monitoring process groups account usability dynatrace saas gui paas openshift key user actions administration user actions postgresql synthetic locations oneagent security Dynatrace Managed user management custom python technologies mongodb openstack user session monitoring continuous delivery citrix configuration alerting NGINX timestamp action naming linux nam installation masking error reporting database mission control jmeter recorder apache mobileapp RUM php threshold azure purepath davis scripting agent aix nodejs android