search

elastic / kibana

Your window into the Elastic Stack
https://www.elastic.co/products/kibana
Other
19.68k stars 8.23k forks source link

[Sample data] Observability data set #62962

Open alexfrancoeur opened 4 years ago

alexfrancoeur commented 4 years ago

Let's use this issue to iterate on the sample data set for Observability

Screen Shot 2020-04-08 at 11 09 17 AM Screen Shot 2020-04-08 at 11 09 09 AM Screen Shot 2020-04-08 at 11 09 39 AM Screen Shot 2020-04-08 at 11 10 16 AM Screen Shot 2020-04-08 at 11 10 24 AM Screen Shot 2020-04-08 at 11 12 09 AM Screen Shot 2020-04-08 at 11 11 12 AM

cc: @EthanStrider

alexfrancoeur commented 4 years ago

@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.

EthanStrider commented 4 years ago

@alexfrancoeur I'll check on whether we need to anonymize anything.

tbragin commented 4 years ago

@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

pmusa commented 4 years ago

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 notifications@github.com 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.

VijayDoshi commented 4 years ago

@tbragin I'll get a working group together to define our approach to sample data.

VijayDoshi commented 3 years ago

@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?