Scheduled - We at LogDNA wanted to notify you of some issues we've been seeing with our Live Tail service. As of recent, our engineering team has discovered a bug within Live Tail that manifests the following behavior for end-users:

- When the live tail is set to live, users might experience what seems to be a lack of logs as they are streaming into the application, e.g., 150 logs are sent to the system and live tail will only display 120 of those logs. This might cause customers confusion and reason to believe that their logs are missing. In actuality, the data is being ingested and is searchable within the application although Live Tail might make you think otherwise.

To properly resolve this bug, it's necessary to entirely re-architect how our live tail works. Over the past month, our backend team was able to successfully able to do this, not only resolving the bug but even making it more efficient and reliable going forward.

As of right now, our newly developed live tail is currently undergoing extensive testing within our staging environment to make sure we deliver a fully developed and thoroughly tested live tail to our end users. We are also ensuring our infrastructure has the necessary resources to it can handle the newly developed service.

There is not a specific ETA for the fix, but we anticipate it will be available to all customers by early January. We will announce when this fix is in place and please rest assured that your feedback has been clearly heard.
Sep 24, 21:03 UTC

Scheduled - Users may experience missing results when searching in logs ingested between 23:15 UTC on Friday, December 13 and 00:45 UTC on Tuesday, December 17. Affected are non-field searches, e.g., "field:value" will produce the expected results, but "value" may not. We refactored our parsing to provide a better user experience when displaying log lines in the UI. Unfortunately, this resulted in searches only searching a subset of some messages. We reverted the change and will ensure this is addressed when we release the improvements early next year. We apologize for any inconvenience this might have caused.
Dec 18, 00:25 UTC