| agent: |
What is an "Expert"? How do we create our own expert?
Add credentials for various integrations
Managing workspaces and access control
DagKnows Architecture Overview
Setting up SSO via Azure AD for Dagknows
Enable "Auto Exec" and "Send Execution Result to LLM" in "Adjust Settings" if desired
(Optionally) Add ubuntu user to docker group and refresh group membership
Deployment of an EKS Cluster with Worker Nodes in AWS
Adding, Deleting, Listing DagKnows Proxy credentials or key-value pairs
Comprehensive AWS Security and Compliance Evaluation Workflow (SOC2 Super Runbook)
AWS EKS Version Update 1.29 to 1.30 via terraform
Instruction to allow WinRM connection
MSP Usecase: User Onboarding Azure + M365
Post a message to a Slack channel
How to debug a kafka cluster and kafka topics?
Open VPN Troubleshooting (Powershell)
Execute a simple task on the proxy
Assign the proxy role to a user
Create roles to access credentials in proxy
Install OpenVPN client on Windows laptop
Setup Kubernetes kubectl and Minikube on Ubuntu 22.04 LTS
Install Prometheus and Grafana on the minikube cluster on EC2 instance in the monitoring namespace
update the EKS versions in different clusters
AI agent session 2024-09-12T09:36:14-07:00 by Sarang Dharmapurikar
Parse EDN content and give a JSON out
Check whether a user is there on Azure AD and if the user account status is enabled
Get the input parameters of a Jenkins pipeline
Get the console output of last Jenkins job build
Get last build status for a Jenkins job
Check if the node went down
For nodes that are in a non-ready state, checks which of them went down by checking for their Node IPs
- 1t4N0rd4xF38AXoa1g7pnkubelet issue
1
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Runs checks to see node readyness issues are due to the Kubelet. Some kubelet issues include unresponsive kubelets, dead kubelets or kubelets that have exited soon.
inputsoutputs1- 1.1lWiJY2yVCuuRomG5HSN5Kubelet stopped posting node status
1.1
Kubelet stopped posting node status
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Returns nodes where kubelet had stopped posting status updates.
inputsoutputs1.1- 1.1.1R6CHVIIkBPQtZfWnDAdBKubelet Dead
1.1.1
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.1.1.1 - 1.1.2IbAsoCsZhM2ewyCX7GaVKubelet exited
1.1.2
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.1.1.2 - 1.1.3NgnZ2L0OqiMQIpG5LCfWWorker kubelet unable to update master
1.1.3
Worker kubelet unable to update master
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Gets the master instance IP addresses in the cluster and uses it to perform connectivity checks.
inputsoutputs1.1.3- 1.1.3.1xSYmJ2ECr0PZ9k9aTbFvSecurity group blocked the API request
1.1.3.1
Security group blocked the API request
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Looks at the security groups of the master instances (by their IDs) to check if there are possible port configuration mismatches preventing connectivity.
inputsoutputs1.1.3.1
- 2N4hnHypnj6NxnlLCWAS5Kube-proxy issue
2
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.2- 2.1qwIuEDWW3beQ089pLlfkkube-proxy not running
2.1
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.2.1
- 3zXuE3xBgzpA4ZB3DDVl4System resources issues
3
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.3- 3.1xMhWpsF8ZXCSDAu1oa45MemoryPressure
3.1
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Checks if any of the nodes are constrained on memory (experiencing MemoryPressure)
inputsoutputs3.1 - 3.2OOvNzV1q99d8jz2mXJWnDiskPressure
3.2
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Checks if any of the nodes are constrained on disk space (experiencing DiskPressure)
inputsoutputs3.2 - 3.3F7DA4ir5dBf9nRL9J2wxPIDPressure
3.3
There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.Checks if any of the nodes are constrained on number of processes (experiencing PIDPressure)
inputsoutputs3.3