You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 10, 2018. It is now read-only.
Ideally, in #5, there will be a way to inherit connection string configuration from the local host. Regardless, it should be obvious what every property is, and how to get it. Most important are the required properties for the eventhub and storage connection strings.
Right now, there's no link to the format of the eventhub or storage connection strings. Neither is there a description of how to get these values (ex via a UI or some cli tool). This makes it hard to get started, as you have to learn something. Ideally people encountering EventHub for the first time are able to get started without even thinking.
There's probably something we can do to make it obvious what you need and how to succeed. Similar to the google or amazon experience, we don't want users to have to think too much (nor do we want other zipkin developers to have no idea how to test this for lack of experience)
The text was updated successfully, but these errors were encountered:
Ideally, in #5, there will be a way to inherit connection string configuration from the local host. Regardless, it should be obvious what every property is, and how to get it. Most important are the required properties for the eventhub and storage connection strings.
Right now, there's no link to the format of the eventhub or storage connection strings. Neither is there a description of how to get these values (ex via a UI or some cli tool). This makes it hard to get started, as you have to learn something. Ideally people encountering EventHub for the first time are able to get started without even thinking.
Here's an example block for google, which includes a section on how to enroll in an account for their zipkin collector. https://medium.com/google-cloud/distributed-tracing-spring-boot-microservices-with-stackdriver-trace-7fe42c6de3f3#.dl3mxikep
There's probably something we can do to make it obvious what you need and how to succeed. Similar to the google or amazon experience, we don't want users to have to think too much (nor do we want other zipkin developers to have no idea how to test this for lack of experience)
The text was updated successfully, but these errors were encountered: