Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Telemetry] Report array of well-known technologies #64790

Closed
afharo opened this issue Apr 29, 2020 · 4 comments · Fixed by #64935
Closed

[Telemetry] Report array of well-known technologies #64790

afharo opened this issue Apr 29, 2020 · 4 comments · Fixed by #64935
Assignees
Labels
enhancement New value added to drive a business result Feature:Telemetry

Comments

@afharo
Copy link
Member

afharo commented Apr 29, 2020

Describe the feature:

We would like to report what well-known technologies are used to ingest data in elasticsearch.

Describe a specific use case for the feature:

In order to build better experiences for our users, we want to understand the most common usages.

@afharo afharo added enhancement New value added to drive a business result Feature:Telemetry :Telemetry labels Apr 29, 2020
@afharo afharo self-assigned this Apr 29, 2020
@kobelb
Copy link
Contributor

kobelb commented Apr 29, 2020

There have been some external discussions to solving the initial implementation of "data source telemetry" which proposed using the cluster state API to determine whether or not various indices exist. It's come to my attention that Elasticsearch makes no guarantees about the response format for cluster-state, and it's not an API which we should be relying upon.

@afharo
Copy link
Member Author

afharo commented Apr 30, 2020

@kobelb I'm implementing a POC, keeping in mind the 2 main different ways of collecting telemetry: OSS/X-Pack vs. Monitoring.

The monitoring way is, initially working as expected. I'll work now on the OSS/X-Pack way and will play around with that API (and possibly the _stats one?) and will try changing permissions to see how it affects it.

Does it sound sensible?

@kobelb
Copy link
Contributor

kobelb commented Apr 30, 2020

@afharo sounds completely reasonable! Using monitoring is definitely an option; however, based on some data I was looking at the other day there's a significant number of clusters which don't have monitoring enabled that we'd be missing information from.

@afharo
Copy link
Member Author

afharo commented May 5, 2020

Yeah! I checked with @alexfrancoeur and we should prioritise the info we can get from OSS and X-Pack over Monitoring.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New value added to drive a business result Feature:Telemetry
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants