Logging and monitoring
Logging
In Nexeed IAS all logs are logged by our application to stdout and then saved in dockers log directory on the host machine (=VM, […]).
Filebeat collects these, parses them (JSON, when Logging guidelines are implemented in all IAS Modules) and forwards them to elasticsearch.
Application Performance Monitoring (APM)
Application Performance Monitoring possibilities need to be activated during deployment to be able to make use of it.
ERP Connectivity’s HELM chart references Nexeed global configuration values for configuration of APM. These are described in the IAS operations manual.
Metrics
A metric is a single measurement at a specific point in time. It can be enriched with more information but quickly turnes then more into an event than in a metric.
Examples for metrics are:
-
CPU Load (load: 5%)
-
Memory consumption (memory.used: 500mb)
-
Disk usage (disk.usage: 90%)
-
Network usage (network.usage : 5000bytes/s)
ERP Connectivity provides following metrics: * messages recevied and processed on internal event bus * HTTP Server metrics (via System.Net.Http) * Runtime Metrics (via OpenTelemetry.Instrumentation.Runtim)
Tracing
A trace represents the path of a request through a software system. This path contains many single steps that are executed within an application.
ERP Connectivity uses Tracing to provide insights into the execution of Connector and Orchestrator Packages - in addition to classical logging. With this the execution of Packages can easily be monitored.