-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NR Dropwizard reporter should start from the project .yml file #112
Labels
3w
Estimate - three weeks or less
Comments
workato-integration
bot
changed the title
NR Dropwizard reporter should start from the project .yml file
NR Dropwizard reporter should start from the project .yml file
Nov 17, 2023
kford-newrelic
added
jan-mar qtr
Represents proposed work item for the Jan-Mar quarter
estimate
Issue needing estimation
labels
Dec 3, 2023
kford-newrelic
added
3w
Estimate - three weeks or less
and removed
estimate
Issue needing estimation
labels
Dec 20, 2023
kford-newrelic
removed
the
jan-mar qtr
Represents proposed work item for the Jan-Mar quarter
label
Jan 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
A user noticed that they were unable to start the
NewRelicReporter
from the project.yml
config file after upgrading to Dropwizard v4.0.1. They are using the Dropwizard REST framework and running the.yml
file on server startup (see below for reproduction steps.) They saw the error with versions0.8.0
and1.0.0
of thedropwizard-metrics-newrelic
project.Reproduced error message:
Steps to reproduce
.yml
config file (such asexample.yml
in thedropwizard-example
project above):java -jar path/to/dropwizard-app.jar server example.yml
for the project mentioned above.Acceptance Criteria
The New Relic reporter should be able to start from the Dropwizard config file without error.
Temporary Workaround
Until this issue is resolved, users can start and configure the
NewRelicReporter
in-code as described in the documentation of this project: starting the New Relic reporterThe text was updated successfully, but these errors were encountered: