All ACaaD components are configurable to expose telemetry data via the opentelemetry protocol and can be consumed from Grafana utilizing the full LGTM stack. As an example, the C# service publishes metrics and logs, the consumers populate spans. Sample Grafana dashboards are included in the respective repositories.
Note: The spans serve two purposes in the consumer project. For one they are very useful to identify performance bottlenecks, especially in the highly concurrent processing of server metadata. However, their main purpose as of now is to enable integration test hooks to wait for specific events happening inside the consumer, for example a signalr client connecting to the server. This means that not all processes are completely covered via tracing, but only the ones that are of interest during integration test execution.
Here the integration test (mock ACaaD server API) returns a purposefully wrong openapi response, which is why the request-parse step fails.
In a production scenario this provides valuable insights in case something would go wrong.
