helm-charts
elasticsearch-py
Our great sponsors
| helm-charts | elasticsearch-py | |
|---|---|---|
| 19 | 21 | |
| 1,483 | 4,134 | |
| 2.6% | 0.7% | |
| 9.8 | 8.7 | |
| 7 days ago | 7 days ago | |
| Smarty | Python | |
| Apache License 2.0 | Apache License 2.0 |
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.
helm-charts
-
Loki with grafana.
Which helm Chart do you use? You should probably use this one https://github.com/grafana/helm-charts/tree/main/charts/loki-distributed
-
Grafana for K8S - configure dashboard access permissions
We were able to keep this config in Grafana UI but if the pod (K8S) is fail the details is deleted, we are using latest prom helm .
-
Spring Boot logging with Loki, Promtail, and Grafana (Loki stack)
Grafana Labs in its Helm repository provides chart that can install Loki stack also with other complementary tools like Logstash or Prometheus.
-
How to Monitor your k8s Persistent Volume Usage
Once you have this ready for your cluster install Grafana from Grafana helm chart from here
-
Promtail tenant doesn't apply
grafana/helm-charts/blob/main/charts/loki-stack/Chart.yaml
-
Grafana Helm Chart - LDAP not working
Using the helm chart values from values.yaml here https://github.com/grafana/helm-charts/blob/main/charts/grafana/values.yaml
- Ask HN: IT Security Checklist for Startups?
-
Query frontend for loki-stack
Hey everyone! This is probably an easy question for those of you with experience. I’m using helm to install loki-stack and cannot figure out how to enable the query frontend with the Helm chart.
-
helm value override doesn't work
from: https://github.com/grafana/helm-charts/blob/ef1cd8a48ab000137df980227745d1eeefcfbefb/charts/promtail/values.yaml
-
Helm looks in a different repository then the one I specify with a --repo flag
helm3 upgrade --install grafana grafana --dry-run --repo https://grafana.github.io/helm-charts --wait Release "grafana" does not exist. Installing it now. Error: failed to download "https://github.com/grafana/helm-charts/releases/download/grafana-6.16.14/grafana-6.16.14.tgz"
elasticsearch-py
- Verify Connection to Elasticsearch (2021)
- An alternative to Elasticsearch that runs on a few MBs of RAM
- Help With Psort.py -> ELK
- Elastic Open Sources Their Endpoint Security Protection YARA Ruleset
-
OpenSearch – open-source search and analytics based on Apache 2.0 Elasticsearch
FD: I have a friend who works at Elastic, though he doesn't really colour my opinions of things.
> Firstly, dick moves like this: https://github.com/elastic/elasticsearch-py/pull/1623
I understand that this is unpopular, but you can make a very strong argument that it's to prevent weird errors in the future. I'm also guilty of littering my code with Asserts to ensure the universe is working fine.
The alternative is to allow it to work and then you end up with weird issues like when you connect mysql client to mariadb server (and vice-versa): https://stackoverflow.com/questions/50169576/mysql-8-0-11-er...
> Secondly, I don't buy the argument from Elastic any more. Yes, the ethical thing to do when you're making money from someone's work is at least contribute back. At the same time though, they're making money from packaging it up and selling it _as a service_. That "as a service" part is where they're making the bucks.
That's just an opinion, yes they have a service, and yes it competes with Amazon. Is it cool for Amazon to take a body of work and sell it without supporting it? Are amazon actually supporting it? Is it the same as Elastic using Lucene? (not really because Elastic submits a the majority of fixes to Lucene, but, you get it).
it's kinda gray, I'm sure Amazon thinks they're the good guy, but it's hard for me to look at Elastic as the bad guy in all this.
- Struggling reading code with type hints
-
I Don't Think Elasticsearch Is a Good Logging System
Oh man, https://github.com/elastic/elasticsearch-py/issues/1734 is a disappointing read. I know ES wants to save their business, but alienating users isn't exactly the path to success.
- Elasticsearch adding code to reject connections to OpenSearch clusters or to clusters running open source distributions of ES7
- Official Elasticsearch Python library no longer works with open-source forks
What are some alternatives?
kubernetes-external-secrets - Integrate external secret management systems with Kubernetes
searxng - SearXNG is a free internet metasearch engine which aggregates results from various search services and databases. Users are neither tracked nor profiled.
syslog-ng - syslog-ng is an enhanced log daemon, supporting a wide range of input and output methods: syslog, unstructured text, queueing, SQL & NoSQL.
quickwit - Cloud-native search engine for observability. An open-source alternative to Datadog, Elasticsearch, Loki, and Tempo.
zeek-clickhouse
qryn - qryn is a polyglot, high-performance observability framework for ClickHouse. Ingest, store and analyze logs, metrics and telemetry traces from any agent supporting Loki, Prometheus, OTLP, Tempo, Elastic, InfluxDB and many more formats and query transparently using Grafana or any other compatible client.
ClickHouse - ClickHouse® is a free analytics DBMS for big data
evtx2es - A library for fast parse & import of Windows Eventlogs into Elasticsearch.
logging-operator - Logging operator for Kubernetes
vector - A high-performance observability data pipeline.
orama - 🌌 Fast, dependency-free, full-text and vector search engine with typo tolerance, filters, facets, stemming, and more. Works with any JavaScript runtime, browser, server, service!