feat: add elasticsearch cloud connector - #24
Merged
Conversation
Add a connector that reads logs from Elasticsearch via the elasticsearchlogs receiver and forwards them to Axorouter. - connectors/elasticsearch/config.yaml: ELASTICSEARCH_*-driven receiver (API key or basic auth, search_after pagination, per-index cursor persisted to file_storage) wired through the standard axoflow processors to the otlp_grpc/axorouter exporter - entrypoint.sh: auto-detect the provider from ELASTICSEARCH_* env vars - README + connector README: document the provider and its variables Note: requires the elasticsearchlogs receiver to be present in the axoflow-otel-collector image. Signed-off-by: Szilard Parrag <szilard.parrag@axoflow.com>
This image includes the elasticsearchlogs receiver required by the elasticsearch connector. Signed-off-by: Szilard Parrag <szilard.parrag@axoflow.com>
csatib02
approved these changes
Jun 24, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds a new Elasticsearch cloud connector that reads logs from an Elasticsearch cluster via the
elasticsearchlogsreceiver and forwards them to Axorouter, following the same pattern as the existing AWS/Kafka/CrowdStrike connectors.Changes
connectors/elasticsearch/config.yaml—elasticsearchlogsreceiver driven byELASTICSEARCH_*env vars (API key or basic auth,search_afterpagination over a stable sort, per-index cursor persisted tofile_storage), wired through the standardresource/axoflow*+resourcedetection/systemprocessors to theotlp_grpc/axorouterexporter.entrypoint.sh— auto-detect the provider fromELASTICSEARCH_*env vars.README.md+connectors/elasticsearch/README.md— document the provider, its environment variables, and the TLS settings.Behaviour notes
start_at=end,initial_lookback=1h,page_size=1000,poll_interval=30s.[{"@timestamp": asc}, {"_seq_no": asc}]; the last field must be unique per document._seq_nois used because it is sortable without fielddata (unlike_id).Prerequisite
This connector only ships configuration. It requires the
elasticsearchlogsreceiver to be present in theaxoflow-otel-collectorimage referenced by theDockerfile(the receiver is proposed upstream in axoflow/opentelemetry-collector-contrib#36), the same way the customcrowdstrikereceiver is already baked in.Validation
config.yamlparses as valid YAML;yamllintclean (same cosmetic comment warnings as the existing connectors).entrypoint.shpassessh -n; provider auto-detection verified.