Skip to content

elastic-package stack Kibana telemetry #1091

Open

Description

Summary

The Kibana started by elastic-package stack up sends telemetry out of the box. Building dashboard on top of these metrics, there is no way to differentiate legitimate data from test data as most of the metrics only contain a cluster_uuid to identify the cluster.

Should we disable telemetry (telemetry.optIn setting) in elastic-package's Kibana to prevent mixing data ? Alternatively, could we store that data to a different index so production dashboard would not report irrelevant data (ie error rate of package installation in dev environment), maybe by routing it to a different telemetry cluster if that is possible ?

We can also ignore this and consider it a minor annoyance as testing data would not be noisy enough.
Thoughts ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

    Labels

    Team:EcosystemLabel for the Packages Ecosystem team

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions