---
name: containers-ts-dupe-logs
title: Why am I seeing duplicate metrics or logs being sent from my clusters?
description: You are seeing duplicate log entries for your clusters.
last-updated: 2025-06-13
---

> ## Documentation Index
> The table of contents for this documentation set is at https://cloud.ibm.com/docs/containers?format=markdown
> The index for all IBM Cloud docs is at: https://cloud.ibm.com/docs/llms.txt
> Use these files to discover more information as needed.

# Why am I seeing duplicate metrics or logs being sent from my clusters?
{: #ts-dupe-logs}
{: troubleshoot}
{: support}


You are seeing duplicate log entries for your clusters.
{: tsSymptoms}


The most common cause for this issue is that you have multiple logging agents installed in your cluster.
{: tsCauses}


Remove the unsupported observability plug-in resources from your cluster.
{: tsResolve}


1. Check for the unsupported agents.
    ```sh
    kubectl get daemonsets -n ibm-observe
    ```
    {: pre}

1. If there is a `logdna-agent` or a `sysdig-agent`, remove them.

    Example output that shows the resources which need to be removed.
    ```sh
    NAME           DESIRED   CURRENT   READY   UP-TO-DATE   AVAILABLE   NODE SELECTOR   AGE
    logdna-agent   9         9         9       9            9           <none>          4d
    sysdig-agent   9         9         9       9            9           <none>          4d
    ```
    {: screen}


1. Delete the resources.
    ```sh
    kubectl delete daemonset logdna-agent -n ibm-observe
    kubectl kubectl delete daemonset sysdig-agent -n ibm-observe
    ```
    {: pre}



1. Verify the daemonset and its pods were deleted.
    ```sh
    kubectl get daemonset logdna-agent -n ibm-observe
    kubectl get pods -l app=logdna-agent -n ibm-observe
    kubectl get daemonset sysdig-agent -n ibm-observe
    kubectl get pods -l app=sysdig-agent -n ibm-observe
    ```
    {: pre}