incident.io is a Slack-native incident response and management tool that scales as your team grows. Hypergrowth companies use incident.io to automate incident processes, focus on fixing the issue, and learn from incident insights to improve site reliability and fix vulnerabilities. Learn more and see how it works on incident.io.
No Cortex Project videos yet. You could help us improve this page by suggesting one.
Based on our record, incident.io should be more popular than Cortex Project. It has been mentiond 31 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
There are SaaS products out there that can help with data collection like incident.io or firehydrant.io to more quickly construct a timeline. Source: about 1 year ago
My new favourite is https://incident.io. Great UI, great product, especially if you also need an incident management tool. Source: about 1 year ago
We did a pretty detailed write-up about a significant incident we had a few months back at incident.io: https://incident.io/blog/intermittent-downtime. Source: over 1 year ago
Co-founder of incident.io here, so I'll avoid throwing my thoughts around for obvious reasons. Source: over 1 year ago
I work at a company that offers a platform for this called https://incident.io/. Source: over 1 year ago
Now if its more metric data you are using and want to do APM, prometheus is your man https://prometheus.io/, want to make prometheus your full time job? Deploy cortex https://cortexmetrics.io/, honorable mention in the metrics space, Zabbix, https://www.zabbix.com/ I've seen use cases of zabbix going way beyond its intended use its a fantastic tool. Source: 12 months ago
Yes, but also no. The Prometheus ecosystem already has two FOSS time-series databases that are complementary to Prometheus itself. Thanos and Mimir. Not to mention M3db, developed at Uber, and Cortex, then ancestor of Mimir. There's a bunch of others I won't mention as it would take too long. Source: 12 months ago
You can use the Remote write feature to send to a centralized location. It would have to be scalable like Cortex https://cortexmetrics.io/. Source: over 1 year ago
For a homelab I think prometheus + grafana is easy to get started and scales well. There are lots of ways to set up the architecture. Prometheus can write to a directory on a filesystem, it can be set to write to a remote server, and there are other projects to integrate object storage (s3, minio, etc) or influxdb for long term storage and downsampling. Source: almost 2 years ago
FireHydrant.io - FireHydrant helps teams organize and remedy incidents quickly when their system experience disruptions.
Thanos.io - Open source, highly available Prometheus setup with long term storage capabilities.
PagerDuty - Cloud based monitoring service
Prometheus - An open-source systems monitoring and alerting toolkit.
Rootly - Rootly helps build a consistent incident response process by automating manual admin work like creating incident channels, Jira tickets, Zoom rooms, and generating postmortem timelines, all from within Slack.
IRONdb - Circonus delivers Machine Data Intelligence for the most demanding use cases. Collect, store, manage, and analyze IoT and monitoring data at unprecedented volume and frequency.