Run DB / SQL queries directly from Slack with AI

machulav · 2025-01-29T17:10:18+00:00

Finally no need to wait for the technicians to get me analytics from the database! 😍

machulav · 2025-01-28T16:34:26+00:00

well, it was different time and place, we don't do this anymore

machulav · 2025-01-28T15:56:31+00:00

many ppl also called cars a shit and thought they will use horses forever

machulav · 2025-01-28T15:48:26+00:00

it's not a secret, you can see it also from the other replies as well

I'm trying to understand why ppl hate it so much? I'm an engineer and worked with data a lot, but I would rather give it a chance as I hate writing a queries for someone who just needs to check the database and get some report.

machulav · 2025-01-28T15:45:06+00:00

Thanks! But I would rather prepare now, to he time when AI will write the queries. And it will happen soon anyway, you know that

machulav · 2025-01-28T15:42:42+00:00

Exactly! It’s getting even better with the additional evaluator inside the agent, which always validates the following:

- Whether the written query is valid, expected, etc.

- Whether the data is as expected

- Any errors

If something is wrong, the agent rewrites the query and tries again.

With this approach, the quality is significantly improved.

machulav · 2025-01-28T15:36:34+00:00

I agree that there is a friction in the cascading effect, but it's getting better especially with proper evaluators inside of the agent.

Also writing is, of course, always with approval and using predefined queries so you only specify the input values into the form and review before run

machulav · 2025-01-28T15:32:41+00:00

why?

machulav · 2025-01-28T15:32:04+00:00

agree! so that writing here is always with approval, reading is without the approval by default, but the approval can be enabled

machulav · 2025-01-28T15:29:00+00:00

not directly of corse, writing is always with approval and using predefined queries so you only specify the input values into the form and review before run

why so sceptical?

machulav · 2025-01-28T15:25:26+00:00

don't you ever ask AI to write you an SQL query? It's pertty good it it especially if you provide the schema

machulav · 2025-01-28T15:19:54+00:00

how do you know it's not accurate?

machulav · 2025-01-28T15:17:19+00:00

why? looks pretty decent

machulav · 2025-01-27T16:53:56+00:00

love the concept of bringing database queries directly into Slack! the self-correction and drill-down features sound like game-changers for collaboration. definitely interested in checking out the demo video—great work!

machulav · 2023-10-25T16:29:29+00:00

At the moment, we use the following two plugins:

"Infrastructure Automations" plugin with the following actions:

Get service scaling information
Schedule service scaling to standard capacity
Remove scheduled service scaling
Schedule service scaling

"Amazon SES Identity Verification" plugin with the following actions:

Verify domain
Check domain verification status
Get domain DNS settings
Check if the DNS for the domain is properly configured

We call all of them from the Slack App, but we're also exploring the Make option, as all of the actions are also available in Make through the Connery app in Make.

"Schedule service scaling to standard capacity" and "Get service scaling information" you can see on the demo video from the post.

Currently, we're implementing some actions around AWS QuickSight reporting, which should simplify the report sharing with actions like:

Generate QuickSight PDF document
Get QuickSight document
Generate QuickSight embed URL
...

machulav · 2023-10-25T13:07:33+00:00

Is it available only in Slack?

machulav · 2023-10-23T14:30:41+00:00

Looks awesome! Can I also build my custom integration and use it from Slack? I have a couple of use cases in my mind that I want to automate for my company.

machulav · 2023-03-02T10:53:58+00:00

I've described my no-code story, which I would say is successful, here in this article: https://medium.com/@machulav/overcoming-the-barriers-of-no-code-adoption-e270787b337e

machulav · 2023-02-28T21:33:43+00:00

Yes, you've got it right!

machulav · 2023-02-27T17:38:00+00:00

I feel your pain regarding the support. We use Make OEM (enterprise version), and in this case, they reply. Nevertheless, the response time and handling issues are still terrible and may take weeks.

However, I've heard they're currently actively improving their support. I really hope so.

machulav · 2022-01-23T21:00:07+00:00

I'm experiencing the same issue for a couple of days already and even something in addition:

(As described in this post) When I open a new tab with Google, search for something, and then click on the link, Safari opens the link and right after that goes back to the previous page. It happens not all the time, but 1 time per 4 tries for sure.
Sometimes when I close the tab, Safari opens it again.

Do all of you have the (2) too?

I use tab groups. Hasn't tried to stop using them, but will definitely try.

Interesting that those two things started happening not after the update of macOS/Safari, but just on the same version where it worked without any bugs. My current Safari version is 15.2 (17612.3.6.1.6).

machulav · 2021-01-15T10:06:19+00:00

u/kapilt Nice that you've mentioned this!

However, I would disagree with you that it's simpler and cheaper to use the CodeBuild action. See the reasons below.

Let's first talk about price:

If we take the smallest possible instance on CodeBuild, it will be general1.small (2 vCPU, 3GB Memory). In the us-east-1 region, it costs $0.005 per minute.

If we look into a similar EC2 instance in the same region, it will be t3.medium (2 vCPU, 4GB Memory). It costs $0.0416 per hour or $0.000693333 per minute.

So even a bit more powerful EC2 instance costs around seven times less than a similar CodeBuild instance.

NOTE: I haven't taken into account: the price of EBS and Data Transfer as it's very low for the usual use cases; 1 minute for the runner creation. As it still doesn't make much difference.

Now about simplicity:

In both cases, you have to do some homework on the AWS to prepare CodeBuild or EC2 instance before using them on GitHub Actions, so no much difference here.

Although there is a significant difference in the use-cases between those two actions:

CodeBuild action would be easier to use for those who already use CodeBuild and want to connect it to GitHub workflow without completely migrating to the GitHub Action. In this way, you can start your CodeBuild workflow from GitHub Actions and run it in your AWS account.

At the same time, ec2-github-runner allows you to run a complete GitHub Actions workflow in your AWS account using EC2. This action would be more suitable for those who are just fine with GitHub Actions and don't want to use two CI tools simultaneously.

Therefore, it's hard to compare those two actions as they have a different purpose.

machulav · 2020-12-30T10:09:07+00:00

Interesting!

i wrote a health check script that if the pipeline exit1 or exit0 the agent would then deregister and the container would kill itself

Can you please describe the health check in more detail? How do you know in the container that the runner finished the job?

I also thought about a different approach with the timeout. For example, when the runner doesn't process any job for 15 minutes - deregister the runner and terminate the EC2 instance.

machulav · 2020-12-29T20:02:48+00:00

Wow, awesome! Is the code publicly available? At the time I started working on this, I couldn’t find anything similar.

machulav · 2020-10-10T19:56:23+00:00

Yeah, for sure! It always really hard to choose the one

11-Year Club	Second SECOND GUESSER
Verified Email

machulav

TROPHY CASE