You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It shows the log lines which contain the pattern (very nice), but it also shows the incoming logs on which it creates the alarm:
But those incoming logs are not filtered with the given pattern? Also the alarm is not using the pattern.
I would expect that it creates an alarm that count's the log lines with the pattern and if there are more then 5 in a period of 5 min it goes into the alarm state. So is it a bug or do I just not understand where this addMaxIncomingLogsAlarm feature is for? because It now just creates a sample count alarm that goes in alarm state if the lambda is called more then 5 times in 5 min.
The text was updated successfully, but these errors were encountered:
Hi,
since 22 march it's possible to add an addMaxIncomingLogsAlarm to the LogMonitoring (#504). But I was wondering, if you set a pattern like:
It shows the log lines which contain the pattern (very nice), but it also shows the incoming logs on which it creates the alarm:
But those incoming logs are not filtered with the given pattern? Also the alarm is not using the pattern.
I would expect that it creates an alarm that count's the log lines with the pattern and if there are more then 5 in a period of 5 min it goes into the alarm state. So is it a bug or do I just not understand where this addMaxIncomingLogsAlarm feature is for? because It now just creates a sample count alarm that goes in alarm state if the lambda is called more then 5 times in 5 min.
The text was updated successfully, but these errors were encountered: