We are currently running an Elastic APM POC and would like your assistance with monitoring a legacy application based on Classic ASP running on Microsoft IIS.
For the Classic ASP application, however, we understand that there is no native Elastic APM agent providing the same level of automatic backend instrumentation.
Our objective is to get the maximum possible observability for this application, including:
HTTP transactions and response times
Slow requests
HTTP errors
Application errors
Calls to external services or databases, where possible
Correlation between IIS/application logs and Elastic
End-user performance visibility
Infrastructure metrics
Alerting and anomaly detection
The application environment is:
Microsoft IIS
Classic ASP
Windows Server
Elastic Cloud
Elastic APM already used for other applications
Elasticsearch version:
8.12.2
APM Server version:
8.12.2
APM Agent language and version:
No backend APM agent currently installed for this application.
The application is written in Classic ASP running on Microsoft IIS.
We are evaluating whether Elastic RUM, OpenTelemetry, the Elastic .NET Agent, or another supported approach can provide observability for this application.
Browser version:
Microsoft Edge / Google Chrome – latest corporate version.
Original install method (e.g. download page, yum, deb, from source, etc.) and version:
Elastic Cloud deployment.
For this Classic ASP application, there is currently no backend Elastic APM agent installed.
Existing logs are already collected using Filebeat / Elastic log collection.
Fresh install or upgraded from other version?
Fresh APM POC implementation for this application.
Elastic APM is already successfully used for other applications in our environment, particularly Java applications.
Is there anything special in your setup?
Our environment is:
-
Elastic Cloud
-
Microsoft Windows Server
-
Microsoft IIS
-
Classic ASP / VBScript application
-
Existing IIS and application log collection
-
Filebeat already in use
-
Elastic APM already used successfully for Java applications
-
No Kafka output
-
No Logstash output specifically for APM
-
No custom APM index templates currently used for this POC
The main specificity is that the monitored application is a legacy Classic ASP application hosted on IIS.