Overview

knowledge bases enable aiden to understand your unique infrastructure, processes, and organizational practices think of it as onboarding aiden to your team by sharing crucial context about how things work in your environment augmenting integrations knowledge bases significantly enhance aiden's ability to work with your integrated tools by providing essential context about your setup for example we use the label 'env' in our prometheus metrics to denote environment (prod/staging/dev) our aws resources follow the naming convention {team} {env} {service}" all production databases have tags environment=prod, backup=daily this context helps aiden formulate more precise queries and actions when working with your integrated systems automated context collection (coming soon) in the near future, aiden will automatically build knowledge bases by analyzing your integrated tools and systems this automated discovery will work alongside your manually provided information to create a comprehensive understanding of your environment for instance, aiden will be able to discover common patterns in your cloud resource tags learn about your monitoring label schemas understand your deployment patterns map service dependencies writing effective knowledge bases write your knowledge bases as if you're explaining your setup to a new senior devops engineer for example we use a centralized argocd instance for all our deployments applications are segregated using argocd projects, with each team having their own project all production deployments require approval from two team leads some key areas to document deployment workflows and practices infrastructure architecture and patterns security policies and compliance requirements development environments and configurations release processes and gates incident response procedures best practices keep it natural write in plain language – no need for special formatting or structures be specific include details that make your setup unique include context add explanations for why certain choices were made document exceptions note any special cases or variations in your processes getting started start with documenting your most frequently used processes and your tool specific configurations this helps aiden immediately provide more accurate assistance, especially when working with your integrated systems