Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add opentelemetry.io docs #2051

Merged
merged 7 commits into from
Apr 8, 2021
Merged

Conversation

austinlparker
Copy link
Member

Per open-telemetry/opentelemetry.io#472, we're mirroring the docs content on the website to each SIG. When a release occurs and these docs are updated, please make an issue or PR mirroring them to their appropriate location in the website repo (https://github.com/open-telemetry/opentelemetry.io/tree/main/content/en/docs/js).

@codecov
Copy link

codecov bot commented Mar 29, 2021

Codecov Report

Merging #2051 (565e78a) into main (897c35f) will not change coverage.
The diff coverage is n/a.

❗ Current head 565e78a differs from pull request most recent head d3c6ca6. Consider uploading reports for the commit d3c6ca6 to get more accurate results

@@           Coverage Diff           @@
##             main    #2051   +/-   ##
=======================================
  Coverage   93.03%   93.03%           
=======================================
  Files         154      154           
  Lines        5976     5976           
  Branches     1246     1246           
=======================================
  Hits         5560     5560           
  Misses        416      416           

@johnbley
Copy link
Member

johnbley commented Apr 1, 2021

Currently we have markdownlint failures; I'd be happy to either

  • add config to exclude website_docs from the markdownlint step, or
  • Fix up these simple issues

But am unsure which we would prefer. Would fixing up the issues to pass this repo's markdownlint cause merge conflicts in the future?

@dyladan
Copy link
Member

dyladan commented Apr 1, 2021

Currently we have markdownlint failures; I'd be happy to either

  • add config to exclude website_docs from the markdownlint step, or
  • Fix up these simple issues

But am unsure which we would prefer. Would fixing up the issues to pass this repo's markdownlint cause merge conflicts in the future?

How would it cause merge conflicts? I would prefer the issues to be fixed if possible

@austinlparker
Copy link
Member Author

I don't expect there to be a huge merge conflict issue once the initial syncing is done (because this will become the authoritative source), but I do wonder if it'd cause unexpected display issues after they're merged back to the website.

Copy link
Member

@obecny obecny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

plugins are gonna be removed very soon so I would encourage to replace all usage with
@opentelemetry/plugin-*
to equivalent of @opentelemetry/instrumentation-* and then registerInstrumentations
You might want to wait a few days with this as I will be removing plugins after the next release and will update examples and readme.md files too .


// Minimum required setup - supports only synchronous operations
const provider = new WebTracerProvider({
plugins: [
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this is outdated and will not work. The tracers doesn't support the plugins options any, please use.

import 'regenerator-runtime/runtime'
import { LogLevel } from "@opentelemetry/core";
import { WebTracerProvider } from '@opentelemetry/web';
import { DocumentLoad } from '@opentelemetry/plugin-document-load';
import { registerInstrumentations } from '@opentelemetry/instrumentation';

const provider = new WebTracerProvider();
provider.register();

registerInstrumentations({
  tracerProvider: provider,
  instrumentations: [
    new DocumentLoad()
  ],
});

import { ConsoleSpanExporter, SimpleSpanProcessor } from '@opentelemetry/tracing';

// Minimum required setup - supports only synchronous operations
const provider = new WebTracerProvider({
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

registerInstrumentations ....

const { NodeTracerProvider } = require("@opentelemetry/node");

const provider = new NodeTracerProvider({
logLevel: LogLevel.ERROR
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logLevel is removed, please use
api.diag.setLogger(new api.DiagConsoleLogger(), api.DiagLogLevel.ERROR);

const { SimpleSpanProcessor, ConsoleSpanExporter } = require("@opentelemetry/tracing");

const provider = new NodeTracerProvider({
logLevel: LogLevel.ERROR
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logLevel was removed

@dyladan
Copy link
Member

dyladan commented Apr 1, 2021

@obecny I think this is just a direct copy of what is already on the website. We should merge it, then make more substantive changes ourselves, then mirror those changes over to the website.

@obecny
Copy link
Member

obecny commented Apr 1, 2021

@obecny I think this is just a direct copy of what is already on the website. We should merge it, then make more substantive changes ourselves, then mirror those changes over to the website.

ohh now I see it make sense

@obecny obecny mentioned this pull request Apr 1, 2021
Copy link
Member

@obecny obecny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

created an issue to update docs #2070

@dyladan dyladan added the document Documentation-related label Apr 7, 2021
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
document Documentation-related
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants