question

Enrico F. avatar image
Enrico F. asked ·

Kafka / Confluent component dependencies auto-detection not working

We have been running some tests regarding support for monitoring our Kafka/Confluent cluster on OpenShift (so far only using the k8s application-only agent as we're on a managed OpenShift PaaS) but have come to realize the Smartscape is not showing any dependencies between components (i.e. producer, broker, consumer) even though messages are clearly being sent.

I realize Kafka uses a proprietary TCP protocol to exchange messages between components and therefore Dynatrace might be unable to detect this traffic.

Can somebody confirm this is a known limitation? If so, would it change anything if we deployed the full-stack OneAgent on the OpenShift nodes?

We are running on Managed (currently 1.160.123) and also have the Kafka Plugin activated.

Any input would be appreciated.

extensionsapachekubernetesopenshiftpaas
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

Enrico F. avatar image
Enrico F. answered ·
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.

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 session replay diagnostic tools 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 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