1 reply
2 replies
Hi All!,
Can anyone help me on how to create a trace analytics using amazon opensearch and zipkin
I use this code
import { ZipkinExporter } from '@opentelemetry/exporter-zipkin';
import { registerInstrumentations } from '@opentelemetry/instrumentation';
import { ExpressInstrumentation } from '@opentelemetry/instrumentation-express';
import { GraphQLInstrumentation } from '@opentelemetry/instrumentation-graphql';
import { HttpInstrumentation } from '@opentelemetry/instrumentation-http';
import { NodeTracerProvider } from '@opentelemetry/node';
import { Resource } from '@opentelemetry/resources';
import { BatchSpanProcessor } from '@opentelemetry/tracing';
const register = () => {
registerInstrumentations({
instrumentations: [
new HttpInstrumentation(),
new ExpressInstrumentation(),
new GraphQLInstrumentation({
depth: 10,
allowValues: true,
mergeItems: true,
}),
],
});
const provider = new NodeTracerProvider({
resource: Resource.default().merge(
new Resource({
'service.name': 'survey-service',
}),
),
});
const zipkinExporter = new ZipkinExporter();
provider.addSpanProcessor(new BatchSpanProcessor(zipkinExporter));
provider.register();
};
register();Using packages:
"@opentelemetry/exporter-zipkin": "^1.2.0",
"@opentelemetry/instrumentation": "^0.22.0",
"@opentelemetry/instrumentation-express": "^0.22.0",
"@opentelemetry/instrumentation-graphql": "^0.22.0",
"@opentelemetry/instrumentation-http": "^0.22.0",
"@opentelemetry/node": "^0.24.0",
"@opentelemetry/resources": "^1.2.0",
"@opentelemetry/tracing": "^0.24.0",After open http://localhost:9411/zipkin/ and run application with GraphQL operations, there wasn't any data in the dashboard.
It seems the telemetry didn't send to Zipkin. Where is the problem?
Hi Guys,
I am deploying Zipkin docker compose on AWS ECS, I am getting error as
A load balancer cannot be attached to multiple subnets in the same Availability Zone (Service: AmazonElasticLoadBalancing; Status Code: 400; Error Code: InvalidConfigurationRequest; Request ID: a18c170a-a44e-46e1-9c65-81e13adcd054; Proxy: null)
Anyone faced the same issue ?
at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:610) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:311) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:250) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.processImports(ConfigurationClassParser.java:600) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.doProcessConfigurationClass(ConfigurationClassParser.java:311) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.processConfigurationClass(ConfigurationClassParser.java:250) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:207) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassParser.parse(ConfigurationClassParser.java:175) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:319) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.annotation.ConfigurationClassPostProcessor.postProcessBeanDefinitionRegistry(ConfigurationClassPostProcessor.java:236) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanDefinitionRegistryPostProcessors(PostProcessorRegistrationDelegate.java:280) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.support.PostProcessorRegistrationDelegate.invokeBeanFactoryPostProcessors(PostProcessorRegistrationDelegate.java:96) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.invokeBeanFactoryPostProcessors(AbstractApplicationContext.java:707) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:533) ~[spring-context-5.2.11.RELEASE.jar:5.2.11.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:143) ~[spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:758) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:750) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:405) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:315) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1237) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1226) [spring-boot-2.3.6.RELEASE.jar:2.3.6.RELEASE]
at com.example.demo.SpringBootMsZipkinserverApplication.main(SpringBootMsZipkinserverApplication.java:16) [classes/:na]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.
Recently I've had an issue with my Zipkin. It uses Elastic Search as storage and its usage is growing. Yesterday the zipking pods started breaking due to low heap memory. I decided to increase it and since then I just can't do any search, it raises an "internal server error" message in the UI. In the logs, you can see
java.lang.RuntimeException: Text fields are not optimised for operations that require per-document field data like aggregations and sorting, so these operations are disabled by default. Please use a keyword field instead. Alternatively, set fielddata=true on [localEndpoint.serviceName] in order to load field data by uninverting the inverted index
2 replies
3 replies
Hi!
I'm trying to zipkin-gcp to export traces to cloud trace.
I run the zipkin-gcp server and the node server instrumented zipkin-js both using cloud run.
When deploying zipking-gcp to cloud run, I set the followings as env variables and used a service account with appropriate permissions(cloudtrace.admin).
STACKDRIVER_PROJECT_ID=my-project-id
STORAGE_TYPE=stackdriverBut I coludn't see any tracing on cloud trace, only I got 202 status from zipkin-gcp server.
I also added -Dlogging.level.zipkin2=DEBUG as env variables, but nothing was displayed on the log of cloud run.
ps zipking-gcp server status seems fine when accessing /health endpoint.
{
"status" : "UP",
"zipkin" : {
"status" : "UP",
"details" : {
"StackdriverStorage{my-project-id}" : {
"status" : "UP"
}
}
}
}What should I do?
Could some tell me how to debug and export traces to cloud trace?
Thanks!
Hello. I'm trying to build a wrapper for the node-rdkafka library using zipkin. I cloned the project and started developing the wrapper but seem to be running into an issue. I created a copy of the existing zipkin-instrumentation-kafkajs project since its very similar to this. I tried to implement it following the tests that are already there and was able to get the first Producer test 'should record a producer span on produce' to pass with the producer implementation using node-rdkafka. Now for the second test 'should add B3 headers to the message on produce' it uses the rawConsumer (without the proxy) and I'm running into an issue. When I run the test and I use the raw consumer setup as I usually set it up the test gets stuck when it calls consume and no output is shown. The last thing that gets printing in the console is 'lerna info Executing command in 1 package: "yarn run test"'. It just stays stuck and I can't debug it unless I take out the consumer.consume() step in the code. Any ideas on what can be going on? consumer.consume() btw is asynchronous and has an event to handle the messages that come in. After running the producer with the container still running I run a consumer in another terminal and I'm able to consume the message. Its only the consumer running in the test that is getting stuck and can't consume the message. The consumer does connect. Any advice would be great. Also not sure if you guys want to take on the development for this? I can help out with whatever you need.
So I finished implementing the node-rdkakfa version and have the tests passing. I was wondering how the team wanted me to merge this in? I have it on my company's private repo but I can do a pull request if that is the proper way. I don't see any development documentation on the github page so not sure if we are allowed to develop our own wrappers or if the zipkin team is responsible for doing that?
