mirror of
https://github.com/denoland/deno.git
synced 2025-03-04 18:12:59 -05:00
55c5b07535
adds tracing and opentelemetry exporting to the LSP.
enable it in `.vscode/settings.json` (or wherever you configure the
LSP), like
```
{
"deno.tracing": true
}
```
which will by default export opentelemetry traces to `localhost:4317`
or
```
{
"deno.tracing": {
// all fields optional
"collector": "openTelemetry" (default) | "logging" (output in lsp log window)
"collectorEndpoint": "http://localhost:4318" (for opentelemetry)
"enable": true | false,
"filter": "info" // defaults to "info", but can be any span filter
}
}
```
---
a full working setup would be
1: Run jaeger (an opentelemetry collector with a nice UI):
```
docker run --rm -p 16686:16686 -p 4317:4317 jaegertracing/jaeger
```
2. Enable in .vscode/settings.json
```
{
"deno.tracing": true
}
```
3. Restart LSP (right now it only will start the opentelemetry exporter
on LSP startup)
3. open `http://localhost:16686` in your browser
---------
Co-authored-by: Nathan Whitaker <nathan@deno.com>
|
||
|---|---|---|
| .. | ||
| testing | ||
| analysis.rs | ||
| cache.rs | ||
| capabilities.rs | ||
| client.rs | ||
| code_lens.rs | ||
| completions.rs | ||
| config.rs | ||
| diagnostics.rs | ||
| documents.rs | ||
| jsr.rs | ||
| language_server.rs | ||
| logging.rs | ||
| lsp_custom.rs | ||
| mod.rs | ||
| npm.rs | ||
| parent_process_checker.rs | ||
| path_to_regex.rs | ||
| performance.rs | ||
| README.md | ||
| refactor.rs | ||
| registries.rs | ||
| repl.rs | ||
| resolver.rs | ||
| search.rs | ||
| semantic_tokens.rs | ||
| text.rs | ||
| trace.rs | ||
| tsc.rs | ||
| urls.rs | ||
Deno Language Server
The Deno Language Server provides a server implementation of the
Language Server Protocol
which is specifically tailored to provide a Deno view of code. It is
integrated into the command line and can be started via the lsp sub-command.
This documentation has been moved to the Deno manual.