Sign in
agent:
Auto Exec

Monitor and analyze error logs from microservices using Elasticsearch queries with aggregation and filtering.

Search and retrieve recent logs from Elasticsearch for specific services containing target keywords.

Trace-based log analysis across microservices or services in Elasticsearch for distributed request tracking using problematic trace_ids from jaeger

List my elasticsearch indices to give me an index pattern name I can search the logs for

Send comprehensive troubleshooting report with root cause and relevant details to Slack channel 'demo'

Perform preliminary infrastructure check by deriving EC2 instance ID from demo app URL, checking instance state, and verifying security group access for port 81

Summarize all recent exceptions and errors for a given set of service or services in jaeger.

Show traces in the last n minutes where service.name in a list of target service/s and (http.target or http.route or url.path contains /path_filter for eg: /api/checkout).

Identify slow or high latency traces for a given service or list of services in jaeger

List all my services in jaeger excludes system related services

Perform preliminary infrastructure check by deriving EC2 instance ID from demo app URL, checking instance state, and verifying security group access for port 81

Fetch the most recent 5 logs from the elasticsearch index <index_name> in last n minutes <lookback_minutes>

Queries Elasticsearch to fetch the latest logs from a list of specified services with required fields

Fetches the latest 10 logs from Elasticsearch for a specific service, sorted by timestamp in descending order

List my elasticsearch indices to give me an index pattern name I can search the logs for

Add a key-value pair

Add credentials for various integrations

What is an "Expert"? How do we create our own expert?

Process Grafana Alerts

Managing workspaces and access control

DagKnows Architecture Overview

Managing Proxies

Setting up SSO via Azure AD for Dagknows

All the experts

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?

Docusign Integration Tasks

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

Sample selenium script

update the EKS versions in different clusters

AI agent session 2024-09-12T09:36:14-07:00 by Sarang Dharmapurikar

Install kubernetes on an ec2 instance ubuntu 20.04 using kubeadm and turn this instance into a master node.

Turn an ec2 instance, ubuntu 20.04 into a kubeadm worker node. Install necessary packages and have it join the cluster.

Install Docker

Parse EDN content and give a JSON out

GitHub related tasks

Managing Proxies

There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
  1. 1

    What's a proxy role? Why is it different from workspace role?

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.

    In DagKnows, a workspace role defines what a user can do within the DagKnows web application—such as viewing, creating, editing, deleting, or executing tasks.

    However, when a task is executed, it runs on a proxy, and this is where proxy roles come into play.

    A proxy role is used to control which credentials a user can access when tasks are executed on the proxy. While the task logic may be the same for all users, the credentials used can vary by user. For example, a task like “List my EC2 instances” may be common, but:

    • User A may run it using their own AWS credentials.
    • User B may run it with a different set of AWS credentials.

    These credentials are securely stored in the HashiCorp Vault on the proxy, organized under named roles. Only users with the appropriate proxy role are allowed to access the credentials associated with that role.

    This separation ensures that:

    • Multiple users can run the same task with different credentials.
    • Access to credentials is tightly controlled and isolated via proxy roles.

    When a user executes a task, they reference a specific credential label in their script. DagKnows will:

    1. Authenticate the user with the Vault.
    2. Check if the user’s proxy role allows access to the requested credential.
    3. If permitted, retrieve and use the credentials securely during task execution.


    1
  2. 2

    How to create a proxy role

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    • Go to Settings
    • Go to Proxies tab
    • Find the table to add a new proxy role


    • Specify the name of the proxy role to add. All lowercase. No special characters.
    • Click Add
    • Ensure the proxy role appears in the table below. If it doesn't, refresh the page and check again.


    2
  3. 3

    How to assign a proxy role to a user

    There was a problem that the LLM was not able to address. Please rephrase your prompt and try again.
    • Go to Users (left nav bar)
    • Find the user to assign a proxy role to. Click on it.
    • Click Modify settings. The user's settings will appear on the right side form.
    • Locate the table for Proxy Roles
    • Locate the proxy to assign the role on for this user
    • Select the role from the dropdown.
    • Click Modify button to save the settings
    3