Repository navigation
Integration for elasticsearch #932
Description
Elasticsearch is a very popular database but doesn't have out of the box integration in sentry.
Please vote with 👍 on this post if you're interested in this.
Reacted by Yoav Alon, Andrei, Ihor Tkachenko, skalecki-imblox, Jad Chamoun, Rajiv Bakulesh Shah, Michal Janek, robindierckx, Klusting, Alireza Khorami and 21 more
Reacted by Klusting, Zakaria EL BAZI and Daniel Alejandro Hernandez Cardona
Activity
github-actions commentedon Dec 23, 2021
This issue has gone three weeks without activity. In another week, I will close it.
But! If you comment or otherwise update it, I will reset the clock, and if you label it
Status: BacklogorStatus: In Progress, I will leave it alone ... forever!"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀
antonpirker commentedon Feb 28, 2022
Hello @yoav-orca
Thanks for making this proposal. If seems there is a little demand for this.
I will put this issue on our internal backlog (but not with a lot of priority) We will do roadmap planning in the next couple of weeks and decide what we are going to tackle and what not.
In the mean time: Pull Requests are always very welcomed! So if you want to start something, please do! I am also here to couch a little and help to bring stuff into shape so we can merge it.
khoramism commentedon Aug 31, 2022
so what happened guys, are you planning to add es?
antonpirker commentedon Sep 30, 2022
Currently we have a lot of other thing on our plates, so ES will not come in the near future. But we are happy to accept PRs for this!
andrecp commentedon Oct 6, 2022
@antonpirker do you have any suggestions on from where to start?
sl0thentr0py commentedon Oct 7, 2022
hey @andrecp, you can look at the sqlalchemy integration as an example of a db span-recording instrumentation. You'll need to do something similar:
11 remaining items
juneja-varun commentedon Aug 15, 2026
Hi — I'd like to work on this. @antonpirker mentioned back in 2020 that PRs would be welcome, and I noticed there's still no
elasticsearchintegration in the currentsentry_sdk/integrations/tree, so the gap seems to still be open.Plan, modeled on the existing
sqlalchemy.py/pymongo.py/redis/integrations (per @sl0thentr0py's pointer above):elasticsearch-pyclient's core request path (search/index/get/update/delete/bulk) to create spans with the standarddb.*span attributes, following whichever of those existing integrations is the closest architectural match for a REST/HTTP-based client.send_default_pii/record_sql_params-equivalent settings for query body capture, consistent with how the other DB integrations handle payload scrubbing.tests/integrations/elasticsearch/, following the existing integration test structure.Before I start: is there a currently preferred/supported version range for
elasticsearch-pyI should target (7.x, 8.x, the newerelasticsearchvs. legacy client split) ?sentrivana commentedon Aug 25, 2026
Hey @juneja-varun, thanks for your interest. We already have a community PR open for ES, so it's just about us finding the time to review it.
juneja-varun commentedon Aug 25, 2026
Thanks for the pointer @sentrivana — good to know it's already covered. I'll leave it with #6793 then, no need to duplicate the effort.