2018-10-25 15:24:34 +02:00
# New Relic
imgproxy can send its metrics to New Relic. To use this feature, do the following:
2022-02-01 11:43:36 +02:00
1. Register at New Relic and get a license key.
2. Set the `IMGPROXY_NEW_RELIC_KEY` environment variable to the license key.
3. _(optional)_ Set the `IMGPROXY_NEW_RELIC_APP_NAME` environment variable to be the desired application name.
2022-06-24 13:02:58 +02:00
4. _(optional)_ Set the `IMGPROXY_NEW_RELIC_LABELS` environment variable to be the desired list of labels. Example: `label1=value1;label2=value2` .
2018-10-25 15:24:34 +02:00
imgproxy will send the following info to New Relic:
2022-02-01 11:43:36 +02:00
* CPU and memory usage
* Response time
2022-07-12 14:20:03 +02:00
* Queue time
2022-02-01 11:43:36 +02:00
* Image downloading time
* Image processing time
* Errors that occurred while downloading and processing an image
2022-07-07 15:13:30 +02:00
Additionally, imgproxy sends the following metrics over [Metrics API ](https://docs.newrelic.com/docs/data-apis/ingest-apis/metric-api/introduction-metric-api/ ):
2022-07-26 10:11:13 +02:00
* `imgproxy.requests_in_progress` : the number of requests currently in progress
* `imgproxy.images_in_progress` : the number of images currently in progress
2022-12-05 16:43:25 +02:00
* `imgproxy.buffer.size` : a summary of the download buffers sizes (in bytes)
2022-07-07 15:13:30 +02:00
* `imgproxy.buffer.default_size` : calibrated default buffer size (in bytes)
* `imgproxy.buffer.max_size` : calibrated maximum buffer size (in bytes)
* `imgproxy.vips.memory` : libvips memory usage (in bytes)
* `imgproxy.vips.max_memory` : libvips maximum memory usage (in bytes)
* `imgproxy.vips.allocs` : the number of active vips allocations