Team Knowledge

every engineering organization has unique tribal knowledge the unwritten rules, naming conventions, query patterns, and debugging heuristics that experienced engineers carry in their heads teaching this knowledge to resolve improves the quality of both chat responses and alert investigations the more context resolve has about your systems, the faster and more accurate its analysis becomes iteratively add knowledge to teach resolve best practices for different types of issues teams and knowledge start by creating a team , which represents a logical group within your organization (ex infra, payments) teams have a few key sections knowledge define best practices for querying observability tools and investigating incidents configuration settings to help resolve understand when this team's knowledge is relevant to pull in to an investigation alerts use the alerts page to filter alerts, enable auto investigation, and attach runbooks workplace collaboration tools connect slack or ms teams channels for alerts, change events, or general chat resources define ownership by selecting applications, services, or clusters managed by the team dashboards add dashboard guidance to help resolve interpret and analyze observability data correctly overview diagram of teams create your first team open app0 resolve ai https //app0 resolve ai/ open the left sidebar and click teams click create team enter a name, description, and click create team set up knowledge, alerts, workplace collaboration tools, and dashboards the default org lets you add guidance for company wide defaults and best practices how resolve uses knowledge knowledge is how you guide resolve’s reasoning resolve uses a two tier knowledge model — every knowledge type can exist at both the organization level and the team level knowledge type organization level team level resolve md company wide defaults for all investigations team specific overrides and context alert runbooks org wide runbook guidance runbooks scoped to this team’s alerts dashboard guidance default guidance for shared dashboards guidance for dashboards this team owns docs company wide reference documents team specific service and system docs alert investigations resolve examines all knowledge associated with the alert and its owning team(s), pulling mapped runbooks and relevant team and org knowledge chats resolve pulls in skills and relevant knowledge sections quickly to keep conversations responsive alerts owned by multiple teams resolve fetches relevant knowledge from all owning teams priority resolve searches org and team knowledge together, surfacing the most relevant information for the investigation team level guidance is prioritized when it's a closer match