Md_haseeb1mo ago

✨ What's new:

🔗 GitHub Integration – Connect your GitHub account so Vigil can correlate incidents with repository activity and deployment context.
🧠 Smarter AI Investigations – Vigil now relies more heavily on monitoring evidence, historical trends, and GitHub signals to produce more structured, evidence-based incident analysis instead of generic AI explanations.

This is another step toward making Vigil an AI reliability engineer that helps explain why something happened, not just that it happened.

As always, I'd love your feedback and suggestions. Thanks for supporting PulseBoard's journey! 🚀

💬8△2

Aivlo - Auto Image Renamer

Bulk rename images & optimize SEO metadata instantly with AI.

Freemium

★★★★★5.05.0 (1)

PromotedPromoted as part of the Growth package

Comments (8)

Olga Kargopolova1mo ago

Nice update, Haseeb! Keep shipping!

Md_haseeb1mo agoReply

Thanks Olga i will keep doing it definitely ....

Sergey Kargopolov1mo ago

Haseed, how does it work with the GitHub? 🤔 I assume AI will be able to correlate only if the monitored website throws exception/logs... but these are very rare cases.

Md_haseeb1mo agoReply

Great question Sergey!

You are right that exceptions / logs would provide the strongest signal but Vigil does not depend only on those now.

The idea is to correlate different signals around the incident timeline. lets say for example

A website goes down at 10:05 am

Vigil can look at:

1)A deployment/commit happened at 10:02 AM
2)Which files were changed
3)What part of the application those changes may affect
4)Whether monitoring behaviour changed after that deployment
5)Historical incident patterns

So even without a direct exception log, it can identify that a recent code change is a possible contributor and explain the reasoning behind it.

I’m also currently working on a deeper code analysis architecture — an algorithmic approach where Vigil can go beyond commit metadata and understand code changes, affected components, and potential risk areas in the repository.

Additionally, we recently added AWS integration. Vigil can now pull infrastructure context during incident analysis by connecting relevant AWS resources like:

1)EC2 instances
2)RDS databases
3)Application Load Balancers
4)Lambda functions
5)CloudWatch alarms

The goal is to combine application changes, infrastructure state, and monitoring signals together instead of looking at only one source of information.

Logs and exceptions will definitely make investigations stronger, but the vision is for Vigil to help investigate incidents even when the available signals are incomplete.

Sergey Kargopolov1mo ago

oh, I see... Yes, I understand now. It is a pretty serious service you have already 👍🏻

Md_haseeb1mo agoReply

Thank you, Sergey! I really appreciate that.

There's still a lot I want to improve, but my goal is to build something that helps founders investigate incidents much faster instead of just telling them a website is down.

Your questions have been really helpful—they've made me think more about how to explain Vigil's approach clearly. Thanks again for taking the time to ask and share your thoughts!

Sergey Kargopolov1mo agoReply

↳ Replying to Md_haseeb

You are very welcome, Haseeb 🙏🏼

Stacy Wycoff25d ago

The AWS integration seems like the bigger unlock here. Once Vigil can see EC2, RDS and Lambda state alongside the deployment timeline, a lot of incidents that used to look mysterious probably start pointing to one obvious source instead of five possible ones. Curious whether infrastructure signals or code signals end up carrying more weight in your confidence scoring once you have both feeding into the same investigation.