Elastic APM Node.js Agent 1.10.0 Released
Elastic is pleased to announce that version 1.10.0 of the Node.js agent for Elastic APM has been released today, adding support for two new databases: Cassandra and Microsoft SQL Server.
Cassandra support
The agent now traces all queries made to your Cassandra cluster (PR #437). This is achieved by instrumenting the popular cassandra-driver Node module. The agent will create the following spans:
Span name | Span type | Description |
Cassandra: Connect | db.cassandra.connect | Created when cassandra-driver initiates a TCP socket to a Cassandra node |
<query-summary> | db.cassandra.query | Created when cassandra-driver performs a single query. The span name will be a short summary of the query performed so you easily can tell spans for different queries apart |
Cassandra: Batch query | db.cassandra.query | Created when cassandra-driver performs a batch query |
Microsoft SQL Server support
The agent now traces all queries made to your SQL Server database (PR #444). This is achieved by instrumenting the popular tedious Node module. The agent will create the following spans:
Span name | Span type | Description |
<sql-summary> | db.mssql.query | Created when tedious performs a query. The span name will be a short summary of the query performed so you easily can tell spans for different queries apart |
Try it out
If you are already using the Elastic APM Node.js Agent, all you need to do is upgrade to the latest version and the agent will automatically discover and trace your Cassandra and SQL Server queries — no configuration needed.
If you haven’t yet taken Elastic APM for a spin, get started by reading our Getting Started Guide.
Future
We have a lot of exciting things we are currently working on. One of those things is adding support for distributed tracing. In microservice-oriented architectures, requests are often processed by multiple services. This can make it hard to troubleshoot latency problems and to find out the root cause of an error. Distributed tracing helps to correlate the interactions of the different services by passing correlation IDs along.
Please give the agent a try and give some feedback in the discussion forum. We are also always open for contributions, so feel free to check out the source code over at GitHub and to open a pull request.