LogDNA Release Notes (continuously updated)

28 days ago by LogDNA

These Notes are updated continuously, in parallel with the release of new features, changes to existing functionality, fixed and known issues, and any content that is necessary to keep our customers and community up-to-date. Note that the most recent content is at the top of this document. You can also access our older Release Notes, previously published weekly.


September 19, 2021

  • [Change in web application] Usage Quotas now include a status indicator at the top of the UI to denote when Usage Quotas are enabled.

September 02, 2021

  • [Fix in web application] Live tail no longer automatically enables when the scroll bar has not reached the bottom of the log viewer. [LOG-10427]

August 31, 2021

  • [Fix in Agent 3.3 Beta] This release of LogDNA Agent v3.3.0-beta.2 is a patch to fix an issue with running the agent on CentOS 8 and RHEL 8 on ARM64/AArch64 environments, in which there was a mismatch between the page size expected by the kernel and the build system. CentOS 8 and RHEL 8 on ARM configure the kernel with a 65536 byte page size rather than the more usual 4k page size. This fix explicitly sets the page size to 64k.

August 30, 2021

  • [Feature in web application] LogDNA is pleased to announce our new Date Picker widget, which allows for faster selection of dates in the Jump to timeframe field of the Log Viewer. Click anywhere in the field, and the date picker displays. You can immediately select a certain date or a range of dates on the calendar and the dates you pick will populate the field. Alternatively, or you can type in an exact date, a range of dates, or a natural language description of the timeframe you want to look at logs from. [LOG-8344]

August 26, 2021

  • [Change in web application] For accounts that implement webhooks for alert integration and also use our Slack integration for alerts, LogDNA will use the webhook integration for Slack alerts if a webhook body template is detected. In cases where no body template is available, then the application will use the Slack integration method. [LOG-10307]

August 23, 2021

  • [Fix in Agent 3.2] This release of LogDNA Agent v3.2.4 includes a patch to resolve an issue with the agent throughput dropping due to too many rapid writes as the latency to the API increased. This patch maintains upload latency while allowing more throughput. [LOG-10569]

August 19, 2021

  • [LogDNA Agent] We are pleased to announce the Beta release of LogDNA Agent v3.3. For details, refer to the LogDNA Agent Release Notes.

August 17, 2021

  • [Feature in web application] LogDNA is pleased to announce the release of our new PagerDuty Autoresolve feature. With auto-resolution, you can configure settings to automatically resolve PagerDuty incidents. For more information, refer to our documentation.

August 16, 2021

  • [Fix in web application] Time standards are now consistent in the Date Picker with local time versus UTC (Coordinated Universal Time) mode. [LOG-10406]
  • [Enhancement in web application] New exclusion rules are now validated upon creation in the web application UI. [LOG-10443]
  • [Fix in web application] A bug was fixed in which if an invalid entry was attempted then auto-complete was invoked and entered a valid entry but one unrelated to the invalid attempt. [LOG-10404]

August 12, 2021

  • [Fix in web application] User accounts created by the LogDNA CLI are now able to set their password and complete registration. [LOG-10412]
  • [Enhancement in web application] The LogDNA web application UI components such as buttons, text links, toggle switches, and inline tabs now use the primary color of blue, which replaces the previous colors magenta and green. For more information about this change, read our lead designer's blog!

August 10, 2021

  • [Fix in web application] We fixed a bug in which renaming a Board sometimes closed the Category that it is in. [LOG-8994]

August 9, 2021

  • [Fix in Agent 3.2] This release of LogDNA Agent v3.2.3 includes a patch for an issue in which the agent (v3.2) had a potential to stop running and/or that truncates large payloads collected by a single agent. [LOG-10537]

August 3, 2021

  • [Fix in web application] When a new user attempted to validate an email address s part of the sign-up process, the application returned a verify failed message on the first attempt. [LOG-10389]

July 30th, 2021

  • [Feature in API] LogDNA is pleased to announce the GA release of several new features and enhancements in our LogDNA API and Terraform Provider:

    • Configuration endpoints to support the programmatic management of Preset Alerts, using GET, PUT, POST, and DELETE methods, via the LogDNA API. Refer to our documentation for more details. Additionally, Preset Alerts can be managed through Terraform.
    • Enhanced integration with Terraform, including support for terraform import, which allows migration of existing LogDNA resources into Terraform State.
    • For more information, read our Blog.
  • [Enhancement in web application] Managing your API keys now includes the ability to give a customized name to each key, to help you keep them straight about each key's specific use. Also, each key now displays the date that the key was generated, and the key numbers are blurred out when you view them in the web application UI, to provide additional security.

  • [Enhancement in web application] To help you learn about new features and enhancements in LogDNA, we have implemented a new in-application notification about recent changes in the UI (with a convenient link to the Release Notes). Reloading your web application keeps your LogDNA instance up-to-date.

July 21, 2021

  • [Fix in Agent 3.2] This release of LogDNA Agent v3.2.2 includes a patch for an issue in which the agent (v3.2) had the LOGDNA_LOOKBACK environment variable set to smallfiles yet was still logging files larger than 8kb on the initial start-up. This only occurred if the large file existed before any agent was started and the state file was enabled. With this fix, the agent now correctly checks the state DB and calculates the appropriate offsets. [LOG-10318]

July 15th, 2021

  • [Enhancement in integration] Our new release of the Python library for logging to LogDNA has improved performance, with support for asynchronous operations and other best practices for handling logging metadata. Users now have the ability to create new custom fields to include in the meta object. By default, the fields args, name, pathname, and lineno from the record object are included. [PI-37, LOG-9823]

June 28th, 2021

  • [Feature in web application] LogDNA is pleased to announce the release of our new Index Rate Alerts feature. Configuring alerts based on the index rate (the retention and storage rate) of your log data provides a way to monitor anomalous behavior in your systems, such as sudden spikes in volume. Index Rate Alerts, along with Usage Quotas, brings control to your logging management tasks and budgeting. [LOG-7599]

  • [Feature in web application] LogDNA has released the new Template Library, with pre-built views, screens, and boards. These templated configurations were purpose-designed to work with specific environments and tools, such as the NGINX web server, Heroku, browser-based logging, or Microsoft Windows security events. For more information, see our documentation. [LOG-9435]

  • [Enhancement in web application] On the Manage Organization page in the web application UI the Ingestion keys and Service keys are now obscured, and display asterisks for all except the final four numbers. [LOG-9985]

June 21, 2021

  • [LogDNA Agent] We are pleased to announce the GA release of LogDNA Agent v3.2. For details, refer to the LogDNA Agent Release Notes.

June 15th, 2021

  • [Enhancement in web application] We have added a new interactive graph on the Usage Dashboard. The Last month in Days -Trends graph allows you to view the average index rates (lines per second) and the percentage of overall usage, based on application, source, or tags. You can click on a specific day in the chart to view the usage for each app, source, and tag for that day. The graph also displays the delta, or change between the previous month's data usage for that item (app, source, or tag). [LOG-9641]

  • [Enhancement in web application] On the Usage Dashboard's graph of the past month's usage, you can now click on a single date to see a pop-up displaying the amount of data ingested for the day. [LOG-9707]

June 3, 2021

  • [Enhancement in web application] You can now collapse the Timeline graph (on the right of the web application) to a small section that is always visible. The button to toggle the Timeline back to regular width appears in upper right. [LOG-8410]

June 2, 2021

  • [Enhancement in Web Application] When the Timeline graph is displayed to its normal width (toggled on), the log lines that are displayed in the main area (the Log Viewer) no longer run behind the graph, but are now separated by open space. [LOG-8411]

  • [Fix in web application] We fixed an issue with the Timeline graph, in which selecting a single point in time on the timeline, and then adjusting that time using the control in the log canvas, did not update the timeline to reflect the default 60-minute time scale. [LOG-9672]

  • [Fix in web application] Previously, on the Billings --> Settings page, the Billing Contact Email field was not displaying when logged in as a member. [LOG-9722]

May 27th, 2021

  • [Fix in web application] Now non-admin users can add a billing address for an account. [LOG-9473]

  • [Fix in web application] When you searched for logs at a specific time frame and then scrolled down in the log viewer, Live Tail turned on automatically, even if it was turned off. Now, if you have manually turned off Live Tail, it will stay off even if you scroll to bottom of the Log Viewer area. [LOG-9712]

  • [Fix in web application] Previously a second click on the exact same log line in the Timeline would reselect the log line and reload the Jump To box. With this fix, a second click will be ignored and the box will not be displayed. [LOG-9585]

  • [Enhancement in an integration] The LogDNA integration with AWS S3 is now released as v2, and contains several enhancements:

    • updated environment variables (considered a breaking change from v1)
    • 100% complete test coverage
    • restructured implementation
    • introduces @logdna/logger as a logger
    • introduces @logdna/env-config as a configuration manager
    • introduces @logdna/stdlib for utility functions
    • replaces CircleCI with Jenkins
    • docs: updated README, Contribution Guide, and added Code of Conduct
      For more information about this release and how to migrate from v1, refer to the README.md file in our public GitHub repository.