WARNING: This information is part of a limited availability release. Portions of this API may be subject to changes and improvements over time. Fields marked deprecated may be removed in the future and their use is discouraged. For more information, see our product and feature lifecycle descriptions.
Fastly will upload log messages to New Relic Logs in the format specified in the New Relic configuration object.
|String||The name of the New Relic Logs logging endpoint. Required.|
|String||The alphanumeric string identifying a service.|
|Integer||The current version of a service.|
|String||Apache style log formatting. Your log must produce valid JSON that New Relic Logs can ingest. Default is: |
|Integer||The version of the custom logging format used for the configured endpoint. Can be either 2 (the default, version 2 log format) or 1 (the version 1 log format). The logging call gets placed by default in |
|String||Where in the generated VCL the logging call should be placed, overriding any format_version default. Can be |
|String||Time-stamp (GMT) when the endpoint was created.|
|String||Time-stamp (GMT) when the endpoint was updated.|
|String||Time-stamp (GMT) when the endpoint was deleted.|
|String||When to execute the New Relic Logs logging rule. If empty, always execute.|
|String||The Insert API key from the Account page of your New Relic account. Required.|
User contributed notes
We welcome comments that add use cases, ideas, tips, and caveats. All comments will be moderated before publication. To post support questions, visit our support center and we'll find you the help you need.