Investigate "Maximum number of URI tags" issue
See original GitHub issueQuarkus tests log warning messages like
[INFO] [stdout] 2022-01-27 14:15:31,983 WARN [io.mic.cor.ins.int.OnlyOnceLoggingDenyMeterFilter] (vert.x-eventloop-thread-3) Reached the maximum number (100) of URI tags for 'http.server.requests'. Are you using path parameters?
which don’t look right. But I suspect that we do not have 100 REST API different endpoints - so maybe something with Micrometer vs Quarkus vs REST-API path parameters isn’t right here.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
How do I solve "Reached the maximum number of URI tags for ...
This should reduce the number of URI tags your application is creating. The default value for the maximum number of URI tags is...
Read more >URI tag of http.server.requests meter contains templated URI
Shipping a resolved URI would explode the total number of tags at the monitoring system and can overwhelm the backend. 2
Read more >Reached the maximum number of URI tags for 'http.client ...
I receive this warning on my app. I am reading rfidtags from about 30 readers at the same time. Each time a tag...
Read more >Threat Explorer and Real-time detections - Office 365
Tags information is also shown in the URL clicks flyout. ... up to a limit of 3,000, along with the number of attempts...
Read more >URL Inspection Tool - Search Console Help
If you've fixed issues since the data was acquired, test the live URL to ... There is a daily limit of inspection requests...
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 Free
Top 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
maybe because the namespace url paths are not added in the match patterns: https://github.com/tomekl007/nessie/blob/be4e348f4b1b4e12453912cb594a4781dc73a5d6/servers/quarkus-server/src/main/resources/application.properties#L173-L183
I was able to hit the issue again (although after about 600+ requests to the server)