We have updated our Terms of Service, Code of Conduct, and Addendum.

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

Options
Martin Prado
Martin Prado Posts: 27 mod
edited July 2023 in Stream

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.

aab41fef0f76fabdcd4307b14ad4f370fc898f29.png

Best Answer

  • Kyle McCririe
    Kyle McCririe Posts: 29 ✭✭
    edited July 2023 Answer ✓
    Options

    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.

Answers

  • Kyle McCririe
    Kyle McCririe Posts: 29 ✭✭
    edited July 2023 Answer ✓
    Options

    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.

Categories