[Feedback]: Awful API documentation

[tom-x1]

Was the documentation helpful?

Yes

What documentation page is affected

Really folks, I'm just pissed. How can anyone with a sane mind think that the new api documentation is an achievement compared to the old one. I just want to add an enrichment processor and its such a hassle compared to the old one to get a working example. Did any of you ever heard of user friendlyness? The old documentation was perfect, you got a easy to read sample for Kibana console which made it intuitive to build your own query. And now with the new documentation you have to fight for every piece to get a working query, thats a joke. I have not the slightest understand for this enshitification other than its intentional. I think its better for everyone to use chatgpt in the future rather than your awful new API documentation! Rant over!

Description

Awful, a hassle, disbelief

[lcawl]

Thanks for the feedback! We're definitely working on improving the current state of the API reference. In the interim, perhaps this information can help?:

• https://www.elastic.co/docs/manage-data/ingest/transform-enrich/data-enrichment (There are some API examples in the pages nested in this section)
• https://www.elastic.co/docs/reference/enrich-processor/ (Additional reference information for each of the processors)
• https://www.elastic.co/guide/en/elasticsearch/reference/8.18/ingest-apis.html, https://www.elastic.co/guide/en/elasticsearch/reference/8.18/enrich-apis.html (If you prefer to see the old style of docs until we get closer to parity)