HTTP Traces Source
An HTTP Traces Source is an endpoint for receiving trace data. The URL securely encodes the Collector and Source information. You can add as many HTTP Traces Sources as you'd like to a single Hosted Collector.
When you set up an HTTP Traces Source, a unique URL is assigned to that Source. The generated URL is a long string of letters and numbers. You can generate a new URL at any time.
Limitations
- Zipkin JSON v2 is the only supported format.
- Traces up to 1,000 spans are supported, this includes metadata. Traces above 1,000 spans per trace may be throttled and/or the critical path by service may be inaccurate.
Create an HTTP Traces Source
To configure an HTTP Traces Source:
-
In the Sumo Logic web interface, select Manage Data > Collection > Collection.
-
On the Collection page, click Add Source next to a Hosted Collector.
-
Select HTTP Traces.
-
Enter a Name for the Source. A description is optional.
-
(Optional) For Source Host and Source Category, enter any string to tag the output collected from the source. These are built-in metadata fields that allow you to organize your data.
- Fields. Click the +Add Field link to add custom log metadata Fields.
- Define the fields you want to associate, each field needs a name (key) and value.
A green circle with a check mark is shown when the field exists and is enabled in the Fields table schema.
An orange triangle with an exclamation point is shown when the field doesn't exist, or is disabled, in the Fields table schema. In this case, an option to automatically add or enable the nonexistent fields to the Fields table schema is provided. If a field is sent to Sumo that does not exist in the Fields schema or is disabled it is ignored, known as dropped.
- Define the fields you want to associate, each field needs a name (key) and value.
- When you are finished configuring the Source click Save.
View the endpoint URL
If you need to access the Source's URL again, click Show URL.
