# Cache mechanism and log when transfer fails **URL:** \ **Category:** Logstash\ **Created:** [February 10, 2023, 9:15am UTC](https://discuss.elastic.co/t/cache-mechanism-and-log-when-transfer-fails/325230 "2023-02-10T09:15:02Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![YasuhiroOkumura](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yasuhirookumura/32/116682_2.png) [@YasuhiroOkumura](https://discuss.elastic.co/u/YasuhiroOkumura)\ **Post date:** [February 10, 2023, 9:15am UTC](https://discuss.elastic.co/t/cache-mechanism-and-log-when-transfer-fails/325230/1 "2023-02-10T09:15:02Z")
1.When transferring messages from logstash(8.6) to pagerduty using pagerduty output plugin, if the transfer fails, is it possible to cache and resend? 2.When using the pagerduty output plugin to transfer messages from logstash to pagerduty, if the transfer fails, which log and what error will be output? ---
**Author:** ![Wave](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wave/32/117242_2.png) [@Wave](https://discuss.elastic.co/u/Wave)\ **Post date:** [February 12, 2023, 1:26am UTC](https://discuss.elastic.co/t/cache-mechanism-and-log-when-transfer-fails/325230/2 "2023-02-12T01:26:05Z")
Perhaps a caching server in between logstash and pagerduty will help in this situation? Some popular ones are redis or kafka. You'll probably need to do some custom work to have it go exactly the way you describe it though. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 12, 2023, 1:26am UTC](https://discuss.elastic.co/t/cache-mechanism-and-log-when-transfer-fails/325230/3 "2023-03-12T01:26:43Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.