# diagnose

Published articles for diagnose.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Why Kafka retention.ms can delay message deletion

DevFeed: [Why Kafka retention.ms can delay message deletion](<https://devfeed.tech/articles/why-your-kafka-topic-ignores-retention-ms-and-how-to-fix-it-31403.md>)

Original publisher: [Read original article](<https://developers.redhat.com/articles/2026/09/16/why-your-kafka-topic-ignores-retentionms-and-how-fix-it>)

Author: Rogerio Santos

Published: 2026-09-16T13:05:06Z

Content type: tutorial

Language: en

Sources: [Red Hat](<https://devfeed.tech/sources/red-hat.md>), [Red Hat Developer](<https://devfeed.tech/sources/red-hat-developer.md>)

Topics: [Kafka](<https://devfeed.tech/topics/kafka.md>), [Apache-Kafka](<https://devfeed.tech/topics/apache-kafka.md>), [configuration](<https://devfeed.tech/topics/configuration.md>), [file](<https://devfeed.tech/topics/file.md>), [Event-Streaming](<https://devfeed.tech/topics/event-streaming.md>)

Tags: [broker](<https://devfeed.tech/tags/broker.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [event-driven](<https://devfeed.tech/tags/event-driven.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [kafka](<https://devfeed.tech/tags/kafka.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [retention](<https://devfeed.tech/tags/retention.md>), [storage](<https://devfeed.tech/tags/storage.md>), [stream-processing](<https://devfeed.tech/tags/stream-processing.md>)

### AI overview

This guide explains why Kafka messages can remain readable beyond a topic's retention.ms setting. Kafka deletes closed log segments rather than individual messages, and the active segment and continuous writes can delay removal of older records.

### Source excerpt

A customer opened a support case with a deceptively simple complaint: a Kafka topic was configured with a 12-hour retention (retention.ms), yet messages produced on July 24 were still readable 4 days later, on July 28. Nothing was broken. The broker logged no errors. The retention policy was working as designed, but the segment layout and continuous write pattern delayed when the old records could actually be removed. The post Why your Kafka topic ignores retention.ms (and how to fix it) appeared first on Red Hat Developer.

## From Crash to Resolution: A Practical Guide for Xbox & Windows Developers

DevFeed: [From Crash to Resolution: A Practical Guide for Xbox & Windows Developers](<https://devfeed.tech/articles/from-crash-to-resolution-a-practical-guide-for-xbox-windows-developers-37540.md>)

Original publisher: [Read original article](<https://deanhume.com/from-crash-to-resolution-a-practical-guide-for-xbox-windows-developers/>)

Author: Dean Hume

Published: 2025-11-24T10:08:19Z

Content type: opinion

Language: en

Sources: [Dean Hume](<https://devfeed.tech/sources/dean-hume.md>)

Topics: [Windows](<https://devfeed.tech/topics/windows.md>), [Xbox](<https://devfeed.tech/topics/xbox.md>), [App](<https://devfeed.tech/topics/app.md>), [Tool](<https://devfeed.tech/topics/tool.md>)

Tags: [crash](<https://devfeed.tech/tags/crash.md>), [developers](<https://devfeed.tech/tags/developers.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [game-development](<https://devfeed.tech/tags/game-development.md>), [guide](<https://devfeed.tech/tags/guide.md>), [practical](<https://devfeed.tech/tags/practical.md>), [tools](<https://devfeed.tech/tags/tools.md>), [windows](<https://devfeed.tech/tags/windows.md>), [workflows](<https://devfeed.tech/tags/workflows.md>), [xbox](<https://devfeed.tech/tags/xbox.md>)

### AI overview

The author describes an article about diagnosing and resolving app crashes on Xbox and Windows, sharing practical tips, tools, and workflows for developers building games or apps.

### Source excerpt

If you've ever had an app crash at the worst possible moment, you'll know how frustrating it can be - both for developers and players. Recently, I wrote an article for the Microsoft Developer blog that dives deep into this exact challenge: how to diagnose and resolve

## Treat Testing Pain with a Healthy Dose of Test Strategy

DevFeed: [Treat Testing Pain with a Healthy Dose of Test Strategy](<https://devfeed.tech/articles/treat-testing-pain-with-a-healthy-dose-of-test-strategy-20366.md>)

Original publisher: [Read original article](<https://engineering.ziffmedia.com/treat-testing-pain-with-a-healthy-dose-of-test-strategy-43285deaad95?source=rss----d6bb34696ef5---4>)

Author: Jeff Benton

Published: 2019-10-22T16:12:57Z

Content type: tutorial

Language: en

Sources: [RetailMeNot](<https://devfeed.tech/sources/retailmenot.md>)

Topics: [Testing](<https://devfeed.tech/topics/testing.md>), [Unit testing](<https://devfeed.tech/topics/unit-testing.md>), [test-coverage](<https://devfeed.tech/topics/test-coverage.md>)

Tags: [coverage](<https://devfeed.tech/tags/coverage.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [flaky](<https://devfeed.tech/tags/flaky.md>), [integration](<https://devfeed.tech/tags/integration.md>), [test-coverage](<https://devfeed.tech/tags/test-coverage.md>), [testing](<https://devfeed.tech/tags/testing.md>), [unit-testing](<https://devfeed.tech/tags/unit-testing.md>)

### AI overview

The article presents test strategy as a low-cost way for engineering teams to diagnose testing problems and create a treatment plan. It discusses missing unit or integration tests, flaky or slow tests, maintainability issues, and test coverage pursued without clear value.

### Source excerpt

We live in a day and age where consumers cannot access medication for their ailment because of cost. We are aware of the anecdotes related to delaying treatment. In the same way, some engineering teams are stuck with projects which are in an unhealthy testing state. The team goes on sprint after sprint with the situation getting worse, not better. In this article, I will introduce a low-cost tool to enable you to diagnose your situation and put together a treatment plan. Testing pain It's a sad situation, but I think we've all been in the place where testing on our project is a pain. "belchonock" © 123RF.com It's a project where no one took the time to set up unit testing. Or the unit test framework exists and no one bothered to add unit tests. There are unit tests, but no integration tests. Or there is no support for the types of integration tests you want to write. The tests are flaky. They take too long. The tests are difficult to maintain or understand. The tests don't provide value and were added to hit a random test coverage number. After all the automated tests pass, you still have this nagging doubt about releasing the latest version to the public. The pain points I have called out above are not exhaustive. We can relate to these pain points, but why don't we fix them? We know ignoring a medical problem is not a good idea. It's not a good idea to ignore your testing pain. But choosing to tackle your testing problems can seem like a daunting task. A tool that I have found helpful to start dealing with my testing pain is to develop a test strategy. "Dejan Bozic" © 123RF.com Develop your Test Strategy A strategy is "A plan of action or policy designed to achieve a long-term or overall aim." (Definition of strategy in English. https://www.lexico.com/en/definition/strategy) A test strategy is a plan of action or policy designed to achieve a long-term testing aim. To develop a test strategy, start answering the following questions. What are the testing pain points

## Zen and the Art of Craft CMS Log File Reading

DevFeed: [Zen and the Art of Craft CMS Log File Reading](<https://devfeed.tech/articles/zen-and-the-art-of-craft-cms-log-file-reading-31323.md>)

Original publisher: [Read original article](<https://nystudio107.com/blog/zen-and-the-art-of-craft-cms-log-file-reading>)

Author: andrew@nystudio107.com (Andrew Welch)

Published: 2019-07-22T05:00:00Z

Content type: tutorial

Language: en

Sources: [nystudio107 | Articles on modern web development.](<https://devfeed.tech/sources/nystudio107-articles-on-modern-web-development.md>)

Topics: [Logging](<https://devfeed.tech/topics/logging.md>), [debugging](<https://devfeed.tech/topics/debugging.md>), [Command-line interface](<https://devfeed.tech/topics/cli.md>), [Development](<https://devfeed.tech/topics/development.md>)

Tags: [black](<https://devfeed.tech/tags/black.md>), [cli](<https://devfeed.tech/tags/cli.md>), [contain](<https://devfeed.tech/tags/contain.md>), [debugging](<https://devfeed.tech/tags/debugging.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [file](<https://devfeed.tech/tags/file.md>), [files](<https://devfeed.tech/tags/files.md>), [forensic](<https://devfeed.tech/tags/forensic.md>), [information](<https://devfeed.tech/tags/information.md>), [insights](<https://devfeed.tech/tags/insights.md>), [learn](<https://devfeed.tech/tags/learn.md>), [let-s](<https://devfeed.tech/tags/let-s.md>), [like](<https://devfeed.tech/tags/like.md>), [logging](<https://devfeed.tech/tags/logging.md>), [php](<https://devfeed.tech/tags/php.md>), [precious](<https://devfeed.tech/tags/precious.md>), [problems](<https://devfeed.tech/tags/problems.md>), [reading](<https://devfeed.tech/tags/reading.md>), [recording](<https://devfeed.tech/tags/recording.md>)

### AI overview

A tutorial on reading Craft CMS log files to diagnose problems, including how Craft separates web, 404, console, queue, and PHP error logs in the storage/logs/ directory. It also discusses using the Debug Toolbar to search, sort, and filter logs during local debugging.

### Source excerpt

Like a black box recording, log files contain precious forensic information for when you have to diagnose problems. Let's learn the art of reading them

## Sniffowanie w FortiOS

DevFeed: [Sniffowanie w FortiOS](<https://devfeed.tech/articles/sniffowanie-w-fortios-27514.md>)

Original publisher: [Read original article](<https://gagor.pro/2012/01/sniffowanie-w-fortios/>)

Author: Tom

Published: 2012-01-23T00:00:00Z

Content type: tutorial

Language: pl

Sources: [Tomasz Gągor](<https://devfeed.tech/sources/tomasz-gagor.md>)

Topics: [FortiOS](<https://devfeed.tech/topics/fortios.md>), [Fortigate](<https://devfeed.tech/topics/fortigate.md>), [debug](<https://devfeed.tech/topics/debug.md>), [Protocol (disambiguation)](<https://devfeed.tech/topics/protocol.md>)

Tags: [debug](<https://devfeed.tech/tags/debug.md>), [diagnose](<https://devfeed.tech/tags/diagnose.md>), [fortigate](<https://devfeed.tech/tags/fortigate.md>), [fortios](<https://devfeed.tech/tags/fortios.md>), [protocol](<https://devfeed.tech/tags/protocol.md>), [trace](<https://devfeed.tech/tags/trace.md>)

### AI overview

A Polish technical note documenting FortiOS commands for live traffic sniffing and IPsec tunnel diagnostics on Fortigate devices. It explains flow filters, console output, packet-count limits, and IKE debug commands, noting that IPsec diagnostics cannot be filtered according to the author.

### Source excerpt

Zawsze gdy potrzebuję zesniffować coś na żywo na Fortigate'ach muszę przeszukać Knowledge Base external link by przypomnieć sobie wszystkie polecenia do tego potrzebne. Tym razem robię notatki 😃 Sniffowanie diagnose debug enable diagnose debug flow filter addr ip address clear clear filter daddr dest ip address dport destination port negate inverse filter port port proto protocol number saddr source ip address sport source port vd index of virtual domain # np. diagnose debug flow filter saddr 10.10.80.3 diagnose debug flow filter daddr 8.8.8.8 diagnose debug flow filter dport 53 # wyświetl wyniki na konsoli diagnose debug flow show console enable # opcjonalne: wyświetla nazwy funkcji np. odwołania do routingu, itp diagnose debug flow show function-name enable # uruchomienie sniffowania - warto podać na końcu jakaś wartość # by sniffowanie zakończyło się po takiej liczbie pakietów # w przeciwnym wypadku wyniki będą się wypisywać na konsoli # aż uda nam się na oślep wyłączyć sniffowanie diagnose debug flow trace start 100 # zresetowanie filtrowania flow diagnose debug reset # wyłączenie sniffowania diagnose debug disable Diagnostyka tuneli IP-Sec # tutaj jest dużo prościej, najpierw włączamy debuga diagnose debug enable # a potem diagnose debug application ike 2 # lub dla bardzo, bardzo szczegółowych logów diagnose debug application ike -1 Niestety nie ma tutaj możliwości filtrowania (albo jeszcze o tym nie wiem), więc jeśli mamy dużo aktywnych tuneli to najlepiej zbierać wypisywane komunikaty do pliku i dopiero przeglądać.