René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Start an \"Operator's Guide\" or \"Administration Guide\" in GitBook docs","articleBody":"**Is your feature request related to a problem? Please describe.**\r\n\r\nAs an operator or potential one, I don't know where to find information in one place about considerations such as:\r\n\r\n- Component architecture (esp. operational perspective e.g. core needs a relational database which is used for registry only, serving instances need to talk to core instances, core and serving APIs are mostly stateless and horizontally scalable, etc.)\r\n  - Feast's options for storage and compute engines—especially as support for more is added—and what Feast configuration parameters apply to each of them\r\n- How configuration is managed in general, e.g. Spring profiles (ref #458)\r\n- How to control logging (related: #277)\r\n- What metrics are exposed and how\r\n- How Feast uses Kafka topics currently\r\n- Monitoring what Feast has last seen as the state of its managed jobs (ref #302)\r\n- Upgrading Feast\r\n  - Considerations for re-deploying ingestion with active streaming jobs\r\n\r\nProbably more, but that's a start.\r\n\r\n**Describe the solution you'd like**\r\n\r\nA section created that we can start from with an outline. By \"section\" I mean to distinguish tracks of documentation for what an end user—data engineer, data scientist, or software engineer in a client of the serving API—wants to know about using Feast's features in a deployment that's managed for them (or at least they're wearing that hat at the moment and not their DevOps one), versus operators who take care of said management.\r\n\r\nTaking Kubernetes as a (more complex) example:\r\n\r\n- [Cluster Administration as a Concepts guide](https://kubernetes.io/docs/concepts/cluster-administration/cluster-administration-overview/)\r\n- [Administer a Cluster tree of task-oriented docs](https://kubernetes.io/docs/tasks/administer-cluster/)\r\n\r\nIt's doubtful we'd get get all of the above exhaustively documented in one swoop. Starting with a pebble should lower friction for contributors to extend it, I know I'll be glad to help fill things in as we prep our production-readiness.","author":{"url":"https://github.com/ches","@type":"Person","name":"ches"},"datePublished":"2020-01-27T10:26:18.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":6},"url":"https://github.com/445/feast/issues/445"}