# Agent integration custom log creation failed

**URL:** <https://discuss.elastic.co/t/agent-integration-custom-log-creation-failed/376729>\
**Category:** Elastic Agent\
**Created:** [April 3, 2025, 8:47am UTC](https://discuss.elastic.co/t/agent-integration-custom-log-creation-failed/376729 "2025-04-03T08:47:09Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joey\_Visbeen](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joey_visbeen/32/134690_2.png) [@Joey\_Visbeen](https://discuss.elastic.co/u/Joey_Visbeen)\
**Post date:** [April 3, 2025, 8:47am UTC](https://discuss.elastic.co/t/agent-integration-custom-log-creation-failed/376729/1 "2025-04-03T08:47:09Z")

</div>

When trying to create a custom log integration for an elastic-agent this error pops up:

```auto
Datastreams matching "logs-custom.log-*" already exist and are not managed by this package, force flag is required

```

After some research, I found out that it specifically has to do with the dataset. I am trying to use custom.log as the dataset. Which is the way Elastic's naming convention says how it should be done, but the error still shows. I don't know what the error means with: "are not managed by this package". Why would this be an issue and how can I solve it. Because on our other environment this does not occur?

P.S. the force flag is not a preferred option because of automation.