Salesforce: Alerting on logs coming from API Queries

magnayn — Tue, 13 Jan 2026 13:20:10 GMT

We're using the salesforce integration, here specifically the "API Queries" piece to bridge a SOQL query and have the results arrive in DT logs.

This is working perfectly. 'fetch logs | filter query.name == 'SF Wrapper Logs'. Happy days.

What I now wish to achieve is alerting, something like "if the rate of logs with LM_Type__c == "ERROR" breaches a certain level, trigger an alert.

And I'm failing miserably. I'm led to believe by chatbots that, because the logs are landing direct from an extension (I.E: dt.openpipeline.source == 'extension:com.dynatrace.salesforce-extension'), nothing done in OpenPipeline or anywhere else is going to work. It talks about query based metrics, which we do not seem to have (or I can't find them), and log re-ingestion, which we also seem not to have.

Is there not some easy way we can use to "do alert based on logging" ?

Re: Salesforce: Alerting on logs coming from API Queries

t_pawlak — Tue, 06 Oct 2026 09:23:07 GMT

I don't think the fact that the logs are coming from the Salesforce extension prevents you from alerting on them.

Since the API Query results are ingested as regular logs into Grail, you should be able to create a DQL-based Custom Alert in the Anomaly Detection app.

For example, something along these lines:

fetch logs | filter query.name == "SF Wrapper Logs" | filter LM_Type__c == "ERROR" | makeTimeseries error_count = count(), interval: 1m

ou can then configure the alert condition against error_count, for example when the number of matching records exceeds a threshold within the evaluation window.

Another option is to create a log metric for those matching records in OpenPipeline and alert on that metric. That would generally be preferable if you want to reuse the same count in dashboards or multiple alerts.

So you shouldn't need to re-ingest the Salesforce logs. dt.openpipeline.source == "extension:com.dynatrace.salesforce-extension" only tells you where the records originated; once they are stored in Grail, they can still be queried with DQL.

For your use case I'd probably start with the DQL Custom Alert, as it avoids creating an additional metric just to test the scenario.

topic Re: Salesforce: Alerting on logs coming from API Queries in Extensions

Salesforce: Alerting on logs coming from API Queries

Re: Salesforce: Alerting on logs coming from API Queries