The TRX Parser action includes vendor-only telemetry that automatically collects usage and performance metrics for the action maintainer. This telemetry is completely transparent to action users and requires no configuration.
trx_parser_action_runs_total
- Total number of action runs (labeled by outcome: success/failure)trx_parser_files_processed_total
- Total number of TRX files processedtrx_parser_tests_total
- Total number of tests found in TRX filestrx_parser_tests_passed
- Total number of passed teststrx_parser_tests_failed
- Total number of failed teststrx_parser_action_run
- Overall action execution spanfind_trx_files
- File discovery operationtransform_trx_files
- TRX file parsing operationstransform_single_trx_to_json
- Individual TRX file parsingcreate_check_runs
- GitHub check run creation operationscreate_single_check_run
- Individual GitHub check run creationgithub_check_create
- GitHub API calls for check creationget_trx_files
- File system operations for finding TRX filesFor the action maintainer, telemetry requires these repository secrets:
Variable | Description |
---|---|
VENDOR_HONEYCOMB_API_KEY |
Honeycomb API key for exporting telemetry data |
VENDOR_HONEYCOMB_DATASET |
Optional: Honeycomb dataset name (defaults to ‘trx-parser’) |
You don’t need to do anything! This telemetry is completely transparent and automatic. Your usage of the action is exactly the same whether telemetry is enabled or not.
- name: Parse TRX files
uses: NasAmin/trx-parser@v1
with:
TRX_PATH: './test-results'
REPO_TOKEN: $
The action will work identically with or without telemetry, and you’ll never see any telemetry-related configuration, logs, or errors.