-
Notifications
You must be signed in to change notification settings - Fork 8k
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
[Sample data] Observability data set #62962
Comments
@EthanStrider, at a glance, this is looking pretty good. Let's move the discussion here for the observability data set. I'll take a deeper dive later today or tomorrow and provide some feedback. In your opinion, are we going to have to anonymize anything? IP's, service names, etc. |
@alexfrancoeur I'll check on whether we need to anonymize anything. |
@alexfrancoeur @VijayDoshi To confirm - this effort is paused for now, is that correct? My understanding is that we need to get together and discuss the future of sample data in Kibana, including long-term maintainability (who's responsible to make sure it still works as we evolve the product and ECS), and how this approach compares to alternative ways to help users get started, be that training, demo playgrounds on elastic.co, etc. So not saying we shouldn't do it, but that we should not take it lightly and all be on the same page. I think Security team is in the same spot, and would like to discuss. cc @hmnichols |
I think training should be in that discussion as well. It is not that easy to load data for users nowadays.
…Sent from my iPhone
On 29 May 2020, at 18:15, Tanya Bragin ***@***.***> wrote:
@alexfrancoeur @VijayDoshi To confirm - this effort is paused for now, is that correct? My understanding is that we need to get together and discuss the future of sample data in Kibana, including long-term maintainability (who's responsible to make sure it still works as we evolve the product and ECS), and how this approach compares to alternative ways to help users get started, be that training, demo playgrounds on elastic.co, etc.
So not saying we shouldn't do it, but that we should not take it lightly and all be on the same page.
I think Security team is in the same spot, and would like to discuss. cc @hmnichols
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
@tbragin I'll get a working group together to define our approach to sample data. |
@tbragin re-surfacing this discussion since I'm hearing continued needs from teams for a common set of sample data. We previously discussed you and Mike taking an action item to work on how we can approach a "Contoso" style data-set for Elastic. Has there been any progress? Or, was this work not prioritized? |
Let's use this issue to iterate on the sample data set for Observability
cc: @EthanStrider
The text was updated successfully, but these errors were encountered: