Cortex
influxdb-apply
Our great sponsors
| Cortex | influxdb-apply | |
|---|---|---|
| 4 | 1 | |
| 1,249 | 0 | |
| 2.9% | - | |
| 4.9 | 0.0 | |
| 3 months ago | about 4 years ago | |
| Scala | Python | |
| GNU Affero General Public License v3.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Cortex
-
Internal Threat Intel Database
TheHive Cortex might come in handy here:https://github.com/TheHive-Project/Cortex
-
Top 20 Open-source tools for every Blue Teamer
TheHive is a scalable 4-in-1 open source and free security incident response platform designed to make life easier for SOCs, CSIRTs, CERTs, and any information security practitioner dealing with security incidents that need to be investigated and acted upon swiftly. Thanks to Cortex, our powerful free and open-source analysis engine, you can analyze (and triage) observables at scale using more than 100 analyzers.
-
Looking for a web script dashboard solution
Basically, I am looking for something a bit like Cortex (screenshot), but for a generic and standalone use.
-
Launch HN: Opstrace (YC S19) – open-source Datadog
Thanks for the correction! You linked to the right Cortex, not to be confused with https://github.com/TheHive-Project/Cortex, haha. https://github.com/cortexproject/cortex is what we talk about. Naming is hard.
influxdb-apply
-
Launch HN: Opstrace (YC S19) – open-source Datadog
Yes, `apply` is hard. It's just as hard as deploying, maintaining, and turning down a service. When adding an `apply` command to a devops tool, the tool authors must think through the entire lifecycle of their service in the user's workflow and make it work well.
The tool creators are the ones with the knowledge to figure these things out. If they don't provide `apply`, then users must research and experiment and learn by making mistakes. This is a colossal waste of effort. Users end up with brittle poorly-documented scripts to do all the things that `apply` would do. These scripts cause ongoing waste of engineering effort, customer frustration from downtime, and lost business growth and revenue.
I spent several weeks making `apply` commands for InfluxDB [0] and Grafana. This proved extremely difficult for Grafana because of deficiencies in its API. Both InfluxDB and Grafana need some work to make them fit into a modern infrastructure-as-code ops environment. Grafana's cofounder and product lead were not interested in my feedback [1] [2].
[0] https://github.com/cozydate/influxdb-apply
[1] https://news.ycombinator.com/item?id=23136582
[2] https://news.ycombinator.com/item?id=23233468
What are some alternatives?
IntelOwl - IntelOwl: manage your Threat Intelligence at scale
loki - Like Prometheus, but for logs.
Kuiper - Digital Forensics Investigation Platform
veneur - A distributed, fault-tolerant pipeline for observability data
catalyst - Catalyst is an open source SOAR and ticket system that helps to automate alert handling and incident response processes
cortex - A horizontally scalable, highly available, multi-tenant, long term Prometheus.
dfir-orc - Forensics artefact collection tool for systems running Microsoft Windows
opstrace - The Open Source Observability Distribution
ThePhish - ThePhish: an automated phishing email analysis tool
opencti - Open Cyber Threat Intelligence Platform