https://step.dev/knowledgebase/30/plugins/analytics-integrations/ Recent content in Analytics Integrations on Step Documentation Hugo -- gohugo.io en Wed, 17 Mar 2021 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/analytics-integrations/jdbc/ Wed, 17 Mar 2021 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/analytics-integrations/jdbc/ The JDBC plugin writes Step measurements to a SQL-based database such as PostgreSQL or MySQL. This allows you to query and visualize Step execution data using any SQL-compatible tool. The JDBC plugin exports measurements only — it does not export keyword-emitted metrics (counters, gauges, histograms). For full metrics export, use the Prometheus or Metrics Logger integration. The plugin has been tested with PostgreSQL 12 and MySQL 8. Data model Since keywords in Step can carry arbitrary custom attributes, each measurement contains a set of fixed fields and an open-ended set of custom fields: https://step.dev/knowledgebase/30/plugins/analytics-integrations/prometheus/ Wed, 17 Mar 2021 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/analytics-integrations/prometheus/ Prometheus is a popular open-source monitoring and alerting system. The Step Prometheus plugin exposes measurements and metrics at a scrape endpoint that Prometheus polls at regular intervals. In addition to Step execution data, the plugin also exposes JVM and Jetty metrics for internal controller monitoring. Note that while not directly related to this plugin, other Step components such as the Grid proxy and Java agents can also expose these metrics to Prometheus via their own configuration. https://step.dev/knowledgebase/30/plugins/analytics-integrations/metrics-logger/ Wed, 17 Mar 2021 14:24:01 +0100 https://step.dev/knowledgebase/30/plugins/analytics-integrations/metrics-logger/ The Metrics Logger plugin writes Step measurements and metrics to structured log files using Logback. The log format is compatible with Splunk and other log aggregation tools. Enabling the plugin The plugin is disabled by default and must be explicitly enabled in step.properties: plugins.MetricsLoggerControllerPlugin.enabled=true Log configuration Log output is controlled by the CONTROLLER_DIR/bin/logback.xml file. The default configuration writes to a rolling file: <appender name="MEASUREMENTS" class="ch.qos.logback.core.rolling.RollingFileAppender"> <file>../log/measurement-logger.log</file> <rollingPolicy class="ch.qos.logback.core.rolling.FixedWindowRollingPolicy"> <fileNamePattern>../log/measurement-logger-%i.log</fileNamePattern> <minIndex>1</minIndex> <maxIndex>2</maxIndex> </rollingPolicy> <triggeringPolicy class="ch.