Skip to content

Commit

Permalink
improve logging
Browse files Browse the repository at this point in the history
  • Loading branch information
dpacheconr committed Nov 20, 2023
1 parent 165ae61 commit d8df242
Showing 1 changed file with 4 additions and 3 deletions.
7 changes: 4 additions & 3 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,14 +23,12 @@ Before setting up the integration, you will need a [New Relic license/ingest API
1. Configure your New Relic license key as a secret in your repository, and call it `NEW_RELIC_LICENSE_KEY`
2. The exporter uses automatic token authentication by default, for this you need to ensure that `GITHUB_TOKEN` has at least read access to the action scope. Alternatively, you can use a Personal Access Token, in this case, configure your PAT token as secret in your repository, called it `GHA_TOKEN`


Create your workflow yaml with below configuration, under .github/workflows, called it `new-relic-exporter.yaml` for example.

Amend env: section according to the token method in use.
`GHA_TOKEN: ${{ secrets.GITHUB_TOKEN }}` for automatic token authentication
`GHA_TOKEN: ${{ secrets.GHA_TOKEN }}` for PAT token authentication


```
name: new-relic-exporter
Expand All @@ -45,6 +43,7 @@ env:
GHA_RUN_ID: ${{ github.event.workflow_run.id }}
GHA_RUN_NAME: ${{ github.event.workflow_run.name }}
jobs:
new-relic-exporter:
name: new-relic-exporter
Expand All @@ -68,8 +67,10 @@ Each workflow's run/execution steps can be viewed as spans, and logs are also ca
![SingleTrace](screenshots/single_trace.png)
![Logs](screenshots/logs.png)

## Troubleshooting


Configure `GHA_DEBUG` as secret in your repository and set it to true
Add GHA_DEBUG: ${{ secrets.GHA_DEBUG }} to your env configuration block.

## Contributing

Expand Down

0 comments on commit d8df242

Please sign in to comment.