How to use Integrations on onenode ELK Instance

Elastic Stack Elasticsearch
1

Hi There,

we have set up a small ELK instance with one Stand Alone Agent on a JIRA Testserver.

The agent reports the logs of the hosts correctly, we would however need the JIRA Logs as well. We should use a JIRA Connection.

image
image968×140 14.6 KB

To achive this it seems to be necessary to use a Proxy / Fleet Server.
Can it be solved on an onenode system or a 2nd VM has to be installed as proxy server?

Thank you very much for a short confirmation.

Best regards

EI

2

Hi @Elasticisti

  1. You can use standalone elastic agent without fleet (that is not what the message is saying)

  2. You can use standalone elastic agent with integrations

  3. In order to use integration Kibana needs access to the Elastic Package Registry

Your Kibana can not reach the Elastic Package Repository Either directly or through a proxy

https://epr.elastic.co/

See here

3

Thank you Stephen :slight_smile:

4

I think the problem is, that JAVA cannot use the our CA Cert allowing the traffic thru our forward proxy.

I think I have to put our cacert to /etc/elasticsearch/certs ...

5

I have upload our "cacert" to the java directory and restarted Kabana und ES ...

The error can be still seen.

Anyway it is strange:

Despite the error, I see a lots if integration.
If there was a real access issue, I shouldn´t see any of them, shouldn´t I:

image
image1487×486 81.5 KB

or are these integrations where no Elastic Package Registry is needed?

Regards

EI

6

No those are "regular" integrations ...
Those may just be
place holder chiklets did you click into one? See if the actual Integrations are installed?

Either way if you want to use integrations you need to fix your access or deploy your own EPR

7

Did you get it to work / connect to the epr

8

No, I closed the ticket because I reinstalled the entire ELK.

In the new install I have uploaded our company cacert to (/usr/share/logstash/jdk/lib/security and /usr/share/elasticsearch/jdk/lib/security).

This has not helped because the “pemchain” contains self-signed Cert.

Als next Step I added the option “NODE_EXTRA_CA_CERTS="/etc/kibana/CA_Bundle_2024.pem" in the file “kibana” in directory “/usr/share/kibana/bin/”

And restarted KIBANA. No change, I have given up.

–> Kibana cannot reach epr.elastic.co even though "chainpem" is set