Skip to main content
Solved

Failed to send anonymized telemetry metadata. Data flow has been stopped

  • March 11, 2025
  • 1 reply
  • 61 views
M

We're seeing the following message and events are no longer flowing through the Worker Group.

Message: Failed to send anonymized telemetry metadata. Data flow has been stopped.
Failed to send anonymized telemetry metadata. License is blocking inputs. Please contact sales@cribl.io or check that firewall rules are not blocking Cribl telemetry metadata collection.

249_72b3c9362c004c1aaf45ae3217d709e5.png

Best answer by Kyle McCririe

Hi there, it looks like your worker is not able to send telemetry metadata.

Licensing | Cribl Docs

Cribl licensing structures

You can manually test connectivity to the telemetry endpoint by using the following command:

$ curl https://cdn.cribl.io/telemetry/

You should see a response of:

cribl /// living the stream!

If you dont see this response. There is likely something like a firewall blocking that worker from sending telematry data.

    1 reply

    K
    • Kyle McCririe
    • Employee
    • Answer
    • March 11, 2025

    Hi there, it looks like your worker is not able to send telemetry metadata.

    Licensing | Cribl Docs

    Cribl licensing structures

    You can manually test connectivity to the telemetry endpoint by using the following command:

    $ curl https://cdn.cribl.io/telemetry/

    You should see a response of:

    cribl /// living the stream!

    If you dont see this response. There is likely something like a firewall blocking that worker from sending telematry data.

    Terms & ConditionsAccessibility statement