> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/dpd-connector-premium/azure-integrationen/azure-diagnose-debug-portal.md).

# Azure-Diagnose / Debug-Portal

## Azure-Diagnose / Debug-Portal

Mit der **Azure-Diagnose** sendet Business Central jeden DPD-Sendungsaufruf (Request-XML, Response-XML, Fehler/SOAP-Fault) zusätzlich an ein zentrales Debug-Portal. So lassen sich auch **einzelne fehlgeschlagene Belege** nachvollziehen.

### In Business Central einrichten

{% stepper %}
{% step %}

#### Endpunkt & Schlüssel hinterlegen

In der [DPD Konfiguration](/dpd-connector-premium/verbindung-and-konfiguration/dpd-konfiguration-feldreferenz.md) unter **Diagnose/Debug**:

* **Azure-Diagnose Endpunkt (URL)** → `https://<functionapp>.azurewebsites.net/api/diag`
* **Azure-Diagnose Schlüssel** → identisch mit `DIAG_INGEST_KEY` der Function
  {% endstep %}

{% step %}

#### Aktivieren

**„Azure-Diagnose aktivieren"** einschalten.
{% endstep %}

{% step %}

#### Testen

Aktion **„Azure-Diagnose testen"** sendet einen Testeintrag und meldet die Erreichbarkeit.
{% endstep %}
{% endstepper %}

### Debug-Portal

Unter `https://<functionapp>.azurewebsites.net/api/diag/view` (Login per `ADMIN_UI_KEY`) sehen Sie die letzten Aufrufe (Zeit, Erfolg/Fehler, Fault-Code, Referenz/Paketnr., Meldung) und je Eintrag die vollständige Request-/Response-Ansicht – mit Filter „nur Fehler" und optionalem Auto-Refresh.

### App-Settings (Diagnose)

| Setting           | Beschreibung                                         |
| ----------------- | ---------------------------------------------------- |
| `DIAG_INGEST_KEY` | Schlüssel für den Diagnose-Ingest (`POST /api/diag`) |
| `DIAG_TABLE`      | Table-Storage-Tabelle (Default `dpddiag`)            |
| `ADMIN_UI_KEY`    | Zugang zum Debug-Portal                              |

{% hint style="info" %}
Die Diagnose-Ereignisse werden im Azure **Table Storage** über die vorhandene `AzureWebJobsStorage`-Verbindung gespeichert; Request/Response werden auf ca. 30 KB gekappt.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/dpd-connector-premium/azure-integrationen/azure-diagnose-debug-portal.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.