Log Management
Enable Logging to Azure Monitor
Since version 3.0, SCEPman, as well as the Certificate Master, will utilize Microsofts Log Ingestion API to write logs to Azure Monitor. This uses a concept of a Log Analytics Workspace to hold the data and allow analyzation as well as a Data Collection Rule that interfaces between the App Service and the log storage. This allows for a more modern approach including RBAC based permissions for SCEPman to access the LAW.
The creation of the Log Analytics Workspace as well as the configuration of the Data Collection Rule is automatically done by running Complete-SCEPmanInstallation of the SCEPman PowerShell module.
Reenabling Data Collector API
If, for any reason, you want to reinstate the previous API to be used you can do so by removing the Log Ingestion related app service variables and again add the ones to be used by the Data Collector API.
Variables to be removed:
Variables to be added:
SCEPman will automatically pick up the settings after a restart and will utilize the Data Collector API again.
KQL Query Examples
See Issues with Your SCEPman Instance
Number of Issued Certificates by Endpoint in the Selected Time Frame
This query is guaranteed to work with SCEPman 3.0 and newer when using the Log Ingestion API for logging. Changes to SCEPman that make this query unusable will be considered Breaking Changes.
If you are using the old Log Ingestion API, use this slightly adapted query:
Starting with SCEPman 2.8, there is always exactly one Info level log entry whose log message starts with "Issued a certificate with serial number " per issued certificate, followed by its serial number. However, due to the unsolvable Two Armies Problem, it can happen that the created certificate never reaches the requester or some other type of error prevents the actual enrollment. Likewise, in case of severe errors, it can happen that a log entry exists without corresponding database entry or vice versa.
Distinct Certificates with OCSP Check
If you are still using the Data Collector API, use this query instead:
Last updated
Was this helpful?