Digging into this a bit more, it looks like the major st2exporter PRs are:

RFR - Add st2 exporter - Dump executions to JSON files on disk. #1597
RFR: Persist a marker in dumper #1614
WIP: Refactor executions exporter to own file #1822

fwict: st2exporter gets notified of executions on a queue and then saves each of the executions as a json file on disk. It also has a marker that gets stored in the DB to make sure no executions get lost if it goes down.

Digging further into old discussions, it looks like this service is meant to be used for analytics. Ship the json files to elasticsearch and make your own queries / dashboards kind of thing.

However, now we have documented using statsd exporter to get analytics in promtheus: https://docs.stackstorm.com/reference/metrics.html

For prometheus metrics, we have several issues:

Incorporate Metrics Collection Across ST2 #4102
Completing Initial Metrics Integration #4104
Metrics Fixup #4146
Expose metrics API for Prometheus #4341
Additional metrics instrumentation for various services and code paths #4314

The metrics feature was added in 2018, and st2exporter didn't get any updates since 2016 (other than codebase-wide changes like python3, formatting with black, or config registration changes)

So, I'm going to submit a PR to remove st2exporter and the related queue and DB Marker bits.

Uh oh!

Remove st2exporter #5295

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions