Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ability to run standalone apm server 8.x without elasticsearch output nor kibana endpoint #11031

Closed
jguay opened this issue Jun 20, 2023 · 5 comments

Comments

@jguay
Copy link

jguay commented Jun 20, 2023

Running standalone APM Server 8.x without elasticsearch output nor kibana endpoint will return

{"log.level":"error","@timestamp":"2023-06-19T01:02:04.567Z","log.logger":"beater","log.origin":{"file.name":"beater/beater.go","file.line":368},"message":"error waiting for server to be ready: cannot wait for integration without either Kibana or Elasticsearch config","service.name":"apm-server","ecs.version":"1.6.0"}

This is a documented requirement

However if apm server is not intended to be allowed to connect to Kibana nor Elasticsearch, this adds a requirement to open connection to Kibana for APM Server standalone to work... Also currently with fleet, only logstash and elasticsearch output are supported hence why APM Server standalone may be used (example using Kafka or Redis output)

Requested feature would be to add the ability to disable the check for APM integration assets installation status hence something like apm-server.check-assets defaulting to true but setting to false would not attempt to check assets are installed or require kibana endpoint

@simitt
Copy link
Contributor

simitt commented Jun 21, 2023

This is indeed a valid usecase for outputs different than Elasticsearch. We have seen issues in the past when templates and ingest pipelines were missing before data ingestion started. After some previous internal discussions, we would want to add additional safety guards and only allow disabling the check if output is different than ES.

@kruskall
Copy link
Member

I think this would no longer be an issue once elastic/elasticsearch#97546 is merged

@heisGarvit
Copy link

Hi, any update / workout found to remove dependency on startup ?

@axw
Copy link
Member

axw commented May 27, 2024

This will be resolved in 8.15.0, by #12066 and elastic/elasticsearch#108860.

@axw axw closed this as completed May 27, 2024
@bafzachris
Copy link

bafzachris commented Nov 6, 2024

With 8.15.3 and redis output configured I still get:

{"log.level":"error","@timestamp":"2024-11-06T07:37:36.527Z","log.logger":"beater","log.origin":{"function":"github.com/elastic/apm-server/internal/beater.waitReady","file.name":"beater/waitready.go","file.line":64},"message":"precondition failed: dial tcp 127.0.0.1:9200: connect: connection refused","service.name":"apm-server","ecs.version":"1.6.0"}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants