How to remove these pipelines from ES8.17.5

Elastic Search
1

I am upgrading ES to the latest version, but after installing it, I found that some of the pipelines I don't need but I cannot delete them,
logs@json-pipeline

logs-default-pipeline

logs@json-message

ent-search-generic-ingestion

search-default-ingestion

behavioral_analytics-events-final_pipeline

logs@default-pipeline

When I deleted them and restarted the ES service, the following log appeared and they were added back
[2025-03-27T15:35:24,937][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline logs@json-message
[2025-03-27T15:35:51,903][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline logs-default-pipeline
[2025-03-27T15:36:05,570][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline logs@json-pipeline
[2025-03-27T15:36:24,973][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline ent-search-generic-ingestion
[2025-03-27T15:36:46,458][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline search-default-ingestion
[2025-03-27T15:37:03,886][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline behavioral_analytics-events-final_pipeline
[2025-03-27T15:37:18,937][INFO ][o.e.x.c.t.IndexTemplateRegistry] [HKAPPDWV2003_node1] adding ingest pipeline logs@default-pipeline

May I ask how I should handle it

2

Welcome to the forum.

You asked for suggestions - I suggest, based on what information you supplied, NOT to delete them.

Maybe better explain what actual problems they are creating for you?

By the way , I thought latest is currently 8.17.4? You really using 8.17.5?

3

Sorry, I got the version number wrong. Actually, I am using 8.17.3

In ES, we have defined a portion of the pipelines ourselves, and we hope that users will only use the defined pipelines. The reality is that there are some default pipelines, which can mislead users.

So we want to delete or prevent this part of the pipeline from displaying

4

Thanks for the clarification

So maybe one of the Elastic employees will reply with an official answer / way / advice.

Personally, within any product there’s features I might not personally be interested to use currently. But I can’t really appreciate the full interdependences between this and that across the whole product. So I’d be ultra-cautious before deleting stuff. Your pipelines and the system supplied pipelines can surely coexist.