Alerting based on content of logs

After checking with them it looks like this is more like having two correlated metrics evaluated at the same time.
We are currently working to add this for infrastructure metrics of the same entity types. On this path, we're first planning to expand this to different infra entity types and possibly expand to any entity or metric type.
While this is on our plans, the delivery of this is most likely over 12-18 months, I will mark the idea as "not considered" for the time being, but internally connect to the relevant roadmap item.
This should update the idea status as the work gets into development.

Thanks Giovanni,

Team Logging is working on adding the appropriate application context or metadata to logs from calls, so this should be possible to be filtered out from a Log Smart Alert.

Let me bring this to their PM and discuss in a bit more detail on how this could now be achieved with the latest state.

Hi Máté,

This RFE was created when only Application Smart Alerts existed, and when we alerted based on erroneous call we would include calls where the is not really an error and the application works find (i.e. an 404 or a 500 with a specific log that the client knows means it is OK)

I would say this applies when related to a trace log, as it is a mix of both context, "Erroneous Calls" AND "Log Message". Which I cannot do in neither the Logs and the Application Smart Alert.

Thank you

Hey,

To clarify, in Application Smart Alerts, where you can alert on erroneous calls trace logs you would like to add a filter option, that a matching log message should also be present (or specifically not be present) in order to count as a violating call?
Would this log be a trace log or something that you can since alert on in the Logs Smart Alert feature already?

Thanks,

Mate