# Elastic SIEM & OpenCTI Integration

**URL:** <https://discuss.elastic.co/t/elastic-siem-opencti-integration/379082>\
**Category:** Elastic Security\
**Created:** [June 11, 2025, 6:32am UTC](https://discuss.elastic.co/t/elastic-siem-opencti-integration/379082 "2025-06-11T06:32:06Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Vishag\_Learning](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vishag_learning/32/143132_2.png) [@Vishag\_Learning](https://discuss.elastic.co/u/Vishag_Learning)\
**Post date:** [June 19, 2025, 5:50am UTC](https://discuss.elastic.co/t/elastic-siem-opencti-integration/379082/8 "2025-06-19T05:50:41Z")

</div>

Hi Chemamartinez,

Thank you for the support.

I'm looking on it now. I'm encountering an issue with the OpenCTI connector agent in Elastic.  
Screenshot of error(left) with error log(right),

 ![image](https://us1.discourse-cdn.com/elastic/original/3X/2/1/219633e46831e6dbeaca7976423f39f10e14ddc0.jpeg)

While troubleshooting, I noticed that the GraphQL endpoint (https://opencti-\*\*\*\*\*\*\*\*.com/public/graphql) was temporarily inaccessible but returned to normal after some time (screenshot attached). The connector agent is also experiencing instability in elastic SIEM, occasionally switching to an unhealthy state. Kindly revert back if having any insights on this matter.

---

_[View the full topic](https://discuss.elastic.co/t/elastic-siem-opencti-integration/379082)._
