1(self.webpackChunk_N_E=self.webpackChunk_N_E||[]).push([[64287],{24009:function(e,t,n){(window.__NEXT_P=window.__NEXT_P||[]).push(["/application-performance-monitoring/ingestion-pipeline/opentelemetry-inputs",function(){return n(50377)}])},82692:function(e,t){"use strict";t.Z={src:"/docs/_next/static/media/jaeger-collector-inputs.19fcc1b5.png",height:650,width:1600,blurDataURL:"data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAgAAAADCAMAAACZFr56AAAAFVBMVEX19fXv7+37+vnn6OfZ2dnW1tbLzMz4n5+GAAAACXBIWXMAAAsTAAALEwEAmpwYAAAAH0lEQVR4nBXIwREAAAQEsV2H/ks28gybBChaFWSsDw8CfQAme1CglAAAAABJRU5ErkJggg==",blurWidth:8,blurHeight:3}},50377:function(e,t,n){"use strict";n.r(t),n.d(t,{__toc:function(){return s}});var i=n(85893),o=n(31379),r=n(9575),p=n(82692);let s=[{depth:2,value:"What is OpenTelemetry?",id:"what-is-opentelemetry"},{depth:2,value:"Working with OpenTelemetry Inputs in APM",id:"working-with-opentelemetry-inputs-in-apm"},{depth:2,value:"APM: OpenTelemetry Inputs",id:"apm-opentelemetry-inputs"},{depth:2,value:"Stack OpenTelemetry Endpoint",id:"stack-opentelemetry-endpoint"},{depth:2,value:"Copy Endpoint Button",id:"copy-endpoint-button"},{depth:2,value:"Protocol",id:"protocol"},{depth:2,value:"Port",id:"port"},{depth:2,value:"Https User and Https Password",id:"https-user-and-https-password"}];function a(e){let t=Object.assign({h1:"h1",h2:"h2",p:"p",img:"img"},(0,r.a)(),e.components);return(0,i.jsxs)(i.Fragment,{children:[(0,i.jsx)(t.h1,{children:"APM: OpenTelemetry Inputs"}),"\n",(0,i.jsx)(t.h2,{id:"what-is-opentelemetry",children:"What is OpenTelemetry?"}),"\n",(0,i.jsx)(t.p,{children:"OpenTelemetry is an open-source project and set of APIs, libraries, agents,\nand instrumentation to provide observability for applications. It enables\nthe collection of telemetry data from software systems to monitor, trace,\nand analyze their behavior and performance. OpenTelemetry is designed to\nhelp developers and operations teams gain insights into the health and\nbehavior of distributed and microservices-based applications."}),"\n",(0,i.jsx)(t.h2,{id:"working-with-opentelemetry-inputs-in-apm",children:"Working with OpenTelemetry Inputs in APM"}),"\n",(0,i.jsx)(t.p,{children:"'OpenTelemetry Inputs' can be located from the menu on the left, under\nthe heading 'Application Performance Monitoring'."}),"\n",(0,i.jsx)(t.p,{children:(0,i.jsx)(t.img,{alt:"Jaeger Collector Inputs",placeholder:"blur",src:p.Z})}),"\n",(0,i.jsx)(t.h2,{id:"apm-opentelemetry-inputs",children:"APM: OpenTelemetry Inputs"}),"\n",(0,i.jsx)(t.p,{children:"This page provides access to the OpenTelemetry endpoint details, allowing\nyou to retrieve and copy the information required for sending data to your\nstack. It will include information such as: plugin, protocol, port,\nhttps username and https password."}),"\n",(0,i.jsx)(t.h2,{id:"stack-opentelemetry-endpoint",children:"Stack OpenTelemetry Endpoint"}),"\n",(0,i.jsx)(t.p,{children:'This is the endpoint where you can send OpenTelemetry data to your Logit.io\nstack for analysis and monitoring. It\'s represented as a\nunique identifier: "12345-9871-4ff0-6789-696ef2841b55-apm.logit.io."'}),"\n",(0,i.jsx)(t.h2,{id:"copy-endpoint-button",children:"Copy Endpoint Button"}),"\n",(0,i.jsx)(t.p,{children:"This button allows you to copy the stack OpenTelemetry endpoint to your\nclipboard for easy use when configuring data sources."}),"\n",(0,i.jsx)(t.h2,{id:"protocol",children:"Protocol"}),"\n",(0,i.jsx)(t.p,{children:'It indicates the protocol you can use to send data to the provided endpoint.\nIn this case, "https" and "grpc" are the available options.'}),"\n",(0,i.jsx)(t.h2,{id:"port",children:"Port"}),"\n",(0,i.jsx)(t.p,{children:'The port number you need to use when configuring the data source to send\ndata to the specified endpoint. It lists "1234" as the port number for both "https" and "grpc."'}),"\n",(0,i.jsx)(t.h2,{id:"https-user-and-https-password",children:"Https User and Https Password"}),"\n",(0,i.jsx)(t.p,{children:"These fields might be used for authentication when sending data over HTTPS.\nHowever, they are currently hidden or not visible, so you may
1need to\nreveal them to enter the appropriate credentials if required"})]})}t.default=(0,o.j)({MDXContent:function(e={}){let{wrapper:t}=Object.assign({},(0,r.a)(),e.components);return t?(0,i.jsx)(t,{...e,children:(0,i.jsx)(a,{...e})}):a(e)},pageOpts:{filePath:"src/pages/application-performance-monitoring/ingestion-pipeline/opentelemetry-inputs.mdx",route:"/application-performance-monitoring/ingestion-pipeline/opentelemetry-inputs",frontMatter:{title:"OpenTelemetry Inputs",metaTitle:"Learn How to View and Edit APM OpenTelemetry Inputs",description:"Follow our in-depth help article to learn how to view and edit your APM OpenTelemetry inputs in Logit.io",stackTypes:"apm"},title:"OpenTelemetry Inputs",headings:s},pageNextRoute:"/application-performance-monitoring/ingestion-pipeline/opentelemetry-inputs"})}},function(e){e.O(0,[31379,92888,49774,40179],function(){return e(e.s=24009)}),_N_E=e.O()}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.