Graylog2 / Graylog2/graylog2-server

Link in pager duty notification doesn't specify a timerange, won't show log messages that triggered alert

Open
#14,111 0 comments 0 reactions 0 assignees View on GitHub
bug triaged
Dominant language
Java
Stars
8.1k
Forks
1.1k
Avg merge
1d 20h
Merged PRs (30d)
217

Description

## What?

When viewing an alert in pagerduty that was sent by graylog, a link is provided that opens graylog to a search page using the event definition search query:

![image](https://user-images.githubusercontent.com/107503402/205146407-c390de4c-fa85-4d15-b5f1-4d7fdaa0fbe1.png)

However, this opens a search page with no time range specified, and defaults to the graylog cluster default (which i believe is last 5 minutes).

![image](https://user-images.githubusercontent.com/107503402/205146987-e089f770-b722-4345-9c1b-229c0a7226ce.png)

This means the log data that triggered the alert is very likely to not be contained in the search result. In order to find the log data applicable to the event, you must find the time the event fired and double check the event definition to understand how far back the search needs to go.

## Why?

The current experience can be improved and made less confusing by adding an absolute search range to the link so the search page opens with exactly the right time range in addition to the search query.

## Your Environment

* Graylog Version: Graylog Cloud 5.0.1 (demo.graylog.cloud)

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.