"Did we just lose ALL our knowledge objects? Do you know how much time and energy that was?" After a destructive resync, Paychex lost two months of its knowledge object creations/modifications. We learned to be prepared if it were to ever happen again. How? It's easier than you might think, and you don't have to be an admin. You’ll learn how to proactively save your work (dashboards, reports, data models, MLTK experiments, ITSI glass tables, macros, views, etc.) and audit changes when they occur. You will leave the session knowing how to manage the ever-increasing amount of things you create. You'll also have solutions that can save you time and effort from having to recreate lost/modified objects, including how to restore service faster. You also will come away with peace of mind knowing that you can take control of safeguarding and protecting your work, thereby covering your assets when a disaster happens.
Slides PDF link - https://conf.splunk.com/files/2019/slides/FN1315.pdf?podcast=1577146257
![Splunk [AI/ML, Splunk Machine Learning Toolkit] 2019 .conf Videos w/ Slides](https://podcast-api-images.s3.amazonaws.com/corona/show/930233/logo_300x300.png){kind=logo}
View all episodes
