Send CodeSign Secure logs to Grafana Loki or Splunk through OpenTelemetry for central search, monitoring and alerting.
How plugins work
A plugin that has never been set up before in CodeSign Secure shows Configure.
A plugin that has been set up shows Edit and a Connect or Disconnect button, depending on its status.
After a successful connection, the server restarts within a few seconds. The page may show a server error during the restart; refresh it after a moment.
Important:
Because connecting restarts the server, signing requests in progress at that moment fail. Connect plugins during a quiet period.
OpenTelemetry and Grafana Loki
Exports all logging data to a Grafana Loki instance.
Field
Required
Description
Example
Protocol
Yes
The protocol used to reach Loki
http
Endpoint
Yes
Hostname or IP address of the Loki server
loki.example.com
Port
Yes
The Loki port
3100
OpenTelemetry and Splunk
Exports all logging data to Splunk for search, analysis, and dashboards.
Field
Required
Description
Protocol
Yes
The protocol used to reach Splunk
Endpoint
Yes
Host name or IP address of the Splunk server
Port
Yes
The port Splunk receives events on
Token
Yes
The Splunk token that authorizes CodeSign Secure to send events, typically an HTTP Event Collector (HEC) token
Index
Yes
The Splunk index the events are written to
Recommendations
Create a Splunk token and index dedicated to CodeSign Secure, so you can rotate or restrict them without affecting other sources.
Allow the connection from the CodeSign Secure server in your firewall. See Ports and Protocols.
After connecting, check that new events arrive, for example, by signing a test file.
