migrating-to-v2.md

Guide for Migrating from v1 to v2

The v2 release of LogDNA S3 Lambda function integration contains lots of refactoral changes to improve the performance and configuration by introducing @logdna/logger, @logdna/env-config, and eslint-config-logdna. There are several changes in naming and handling environment variables as well. All environment variables are documented here

Renamed Variables

• LOGDNA_KEY was replaced with INGESTION_KEY.
• LOGDNA_HOSTNAME was replaced with HOSTNAME.
• LOGDNA_TAGS was replaced with TAGS.
• LOGDNA_URL was split into multiple new variables: INGESTION_ENDPOINT, INGESTION_HOST, INGESTION_PORT, and SSL.
• LOGDNA_BATCH_INTERVAL was replaced with FLUSH_INTERVAL.
• LOGDNA_BATCH_LIMIT was replaced with FLUSH_LIMIT.

Removed Variables

• LOGDNA_FREE_SOCKET_TIMEOUT, LOGDNA_MAX_REQUEST_RETRIES, LOGDNA_REQUEST_RETRY_INTERVAL, and LOGDNA_MAX_REQUEST_TIMEOUT were removed because the connection is handled within the logger client.
• LOGDNA_MAX_LINE_LENGTH was removed because line length is handled on the server-side.
• LOGDNA_EVENTLOG and LOGDNA_FILELOG were removed because v2 streams only the logs from the files within the specified bucket. You can use AWS CloudTrail Event Logging to stream Object-level operations from S3 buckets. For more information, refer to this article.

New Variables

• PROXY, HTTPS_PROXY, and HTTP_PROXY provide proxy support.
• USER_AGENT supports custom user-agent overrides.