[BUG]Even though I am not extracting loggers, diagnostics still I am getting validation error

[sandhya-techie]

Release version

v6.0.1.1

Describe the bug

extractor config.yaml file:

I am getting below error even though in my artifacts diagnostics and loggers ar not present.

dbug: HttpPipeline[0]
Received response
Method: PUT
Uri: https://management.azure.com/subscriptions//resourceGroups//providers/Microsoft.ApiManagement/service/apim-instance-name/apis/v1/diagnostics/applicationinsights?api-version=2023-09-01-preview
Status code: 400
Duration (hh:mm:ss): 00:00:00.1308076
crit: publisher[0]
Application failed.
System.Net.Http.HttpRequestException: HTTP request to URI https://management.azure.com/subscriptions//resourceGroups/rg/providers/Microsoft.ApiManagement/service//apis/v1/diagnostics/applicationinsights?api-version=2023-09-01-preview failed with status code 400. Content is '{"error":{"code":"ValidationError","message":"One or more fields contain incorrect values:","details":[{"code":"ValidationError","target":"loggerId","message":"Logger Id 'logger-name' does not exist"}]}}'.
at common.HttpPipelineExtensions.<>c__DisplayClass11_0.b__0(Response response) in /home/runner/work/apiops/apiops/tools/code/common/Http.cs:line 173
at LanguageExt.Either.Left2.Match[B](Func2 Left, Func2 Right) at LanguageExt.Either2.IfLeft(Func`2 leftMap)

Expected behavior

this issue should not appear as in artifacts those information is not available.

Actual behavior

Even though in artifact those information is not present still it is giving validation error.

Reproduction Steps

.

[github-actions]

  Thank you for opening this issue! Please be patient while we will look into it and get back to you as this is an open source project. In the meantime make sure you take a look at the [closed issues](https://github.com/Azure/apiops/issues?q=is%3Aissue+is%3Aclosed) in case your question has already been answered. Don't forget to provide any additional information if needed (e.g. scrubbed logs, detailed feature requests,etc.).
  Whenever it's feasible, please don't hesitate to send a Pull Request (PR) our way. We'd greatly appreciate it, and we'll gladly assess and incorporate your changes.