Express transaction names broken in v2.6.0+
See original GitHub issueTo Reproduce
require('elastic-apm-node').start();
const express = require('express');
const server = express();
// apm-agent-nodejs < 2.6.0: setting default transaction name: GET /some-path
// apm-agent-nodejs >= 2.6.0: setting default transaction name: GET unknown route
server.use('/some-path', (req, res) => {
res.send('Hi');
});
server.listen(1212);
After a quick search, elastic/apm-agent-nodejs#842 looks like a possible reason.
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
American Express down? Current status. - Downdetector
Real-time status for American Express. Is the website down, can't check your statements or log in? Here you see what is going on....
Read more >Fix issues when you pay for Google products & services
“Transaction declined. Try a different payment method or contact your card's issuer.” “Your purchase on your [telecom carrier] billing account was declined.
Read more >Troubleshoot a Full Transaction Log (SQL Server Error 9002)
Common reasons for a full transaction log · How to resolve a full transaction log · 1. Truncate the Log · 2. Resolve...
Read more >Transactions in SQL Server for beginners
This article will show basic principles of transactions in SQL Server with examples.
Read more >Merchant Services FAQ | Clover
Frequently asked questions from the merchant service and small business world, to help you run a successful business and continue to grow.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
This issue has now been fixed and released as part of v2.11.5. Thanks for your patience 😊
The second option is how it worked before so 👍