Span (brave-core 3.9.1 API)

java.lang.Object
- com.twitter.zipkin.gen.Span

All Implemented Interfaces:

Serializable
```
public class Span
extends Object
implements Serializable
```
A trace is a series of spans (often RPC calls) which form a latency tree. The root span is where trace_id = id and parent_id = Nil. The root span is usually the longest interval in the trace, starting with a SERVER_RECV annotation and ending with a SERVER_SEND.

See Also:

Serialized Form

Field Summary

Fields
Modifier and Type Field and Description

Long startTick
Internal field, used for deriving duration with System.nanoTime().

Fields
Modifier and Type	Field and Description
`Long`	`startTick` Internal field, used for deriving duration with `System.nanoTime()`.

Constructor Summary

Constructors
Constructor and Description

Span()

Constructors
Constructor and Description
`Span()`

Method Summary

All Methods Instance Methods Concrete Methods
Modifier and Type	Method and Description
`Span`	`addToAnnotations(Annotation elem)`
`Span`	`addToBinary_annotations(BinaryAnnotation elem)`
`boolean`	`equals(Object o)`
`List<Annotation>`	`getAnnotations()`
`List<BinaryAnnotation>`	`getBinary_annotations()`
`Long`	`getDuration()` Measurement of duration in microseconds, used to support queries.
`long`	`getId()`
`String`	`getName()` Span name in lowercase, rpc method for example Conventionally, when the span name isn't known, name = "unknown".
`Long`	`getParent_id()`
`Long`	`getTimestamp()` Microseconds from epoch of the creation of this span.
`long`	`getTrace_id()`
`int`	`hashCode()`
`Boolean`	`isDebug()`
`Span`	`setAnnotations(List<Annotation> annotations)`
`Span`	`setBinaryAnnotations(List<BinaryAnnotation> binary_annotations)`
`Span`	`setDebug(Boolean debug)`
`Span`	`setDuration(Long duration)` Measurement of duration in microseconds, used to support queries.
`Span`	`setId(long id)`
`Span`	`setName(String name)` Span name in lowercase, rpc method for example Conventionally, when the span name isn't known, name = "unknown".
`Span`	`setParent_id(Long parent_id)`
`Span`	`setTimestamp(Long timestamp)` Microseconds from epoch of the creation of this span.
`Span`	`setTrace_id(long trace_id)`
`String`	`toString()`
`zipkin.Span`	`toZipkin()` Changes this to a zipkin-native span object.

Methods inherited from class java.lang.Object
clone, finalize, getClass, notify, notifyAll, wait, wait, wait

- Field Detail
  - startTick
```
public volatile Long startTick
```
    Internal field, used for deriving duration with System.nanoTime().
- Constructor Detail
  - Span
```
public Span()
```
- Method Detail
  - getTrace_id
```
public long getTrace_id()
```
  - setTrace_id
```
public Span setTrace_id(long trace_id)
```
  - getName
```
public String getName()
```
    Span name in lowercase, rpc method for example Conventionally, when the span name isn't known, name = "unknown".
  - setName
```
public Span setName(String name)
```
    Span name in lowercase, rpc method for example Conventionally, when the span name isn't known, name = "unknown".
  - getId
```
public long getId()
```
  - setId
```
public Span setId(long id)
```
  - getParent_id
```
public Long getParent_id()
```
  - setParent_id
```
public Span setParent_id(Long parent_id)
```
  - addToAnnotations
```
public Span addToAnnotations(Annotation elem)
```
  - getAnnotations
```
public List<Annotation> getAnnotations()
```
  - setAnnotations
```
public Span setAnnotations(List<Annotation> annotations)
```
  - addToBinary_annotations
```
public Span addToBinary_annotations(BinaryAnnotation elem)
```
  - getBinary_annotations
```
public List<BinaryAnnotation> getBinary_annotations()
```
  - setBinaryAnnotations
```
public Span setBinaryAnnotations(List<BinaryAnnotation> binary_annotations)
```
  - isDebug
```
public Boolean isDebug()
```
  - setDebug
```
public Span setDebug(Boolean debug)
```
  - getTimestamp
```
public Long getTimestamp()
```
    Microseconds from epoch of the creation of this span. This value should be set directly by instrumentation, using the most precise value possible. For example, gettimeofday or syncing nanoTime against a tick of currentTimeMillis. For compatibilty with instrumentation that precede this field, collectors or span stores can derive this via Annotation.timestamp. For example, SERVER_RECV.timestamp or CLIENT_SEND.timestamp. This field is optional for compatibility with old data: first-party span stores are expected to support this at time of introduction.
  - setTimestamp
```
public Span setTimestamp(Long timestamp)
```
    Microseconds from epoch of the creation of this span. This value should be set directly by instrumentation, using the most precise value possible. For example, gettimeofday or syncing nanoTime against a tick of currentTimeMillis. For compatibilty with instrumentation that precede this field, collectors or span stores can derive this via Annotation.timestamp. For example, SERVER_RECV.timestamp or CLIENT_SEND.timestamp. This field is optional for compatibility with old data: first-party span stores are expected to support this at time of introduction.
  - getDuration
```
public Long getDuration()
```
    Measurement of duration in microseconds, used to support queries. This value should be set directly, where possible. Doing so encourages precise measurement decoupled from problems of clocks, such as skew or NTP updates causing time to move backwards. For compatibilty with instrumentation that precede this field, collectors or span stores can derive this by subtracting Annotation.timestamp. For example, SERVER_SEND.timestamp - SERVER_RECV.timestamp. If this field is persisted as unset, zipkin will continue to work, except duration query support will be implementation-specific. Similarly, setting this field non-atomically is implementation-specific. This field is i64 vs i32 to support spans longer than 35 minutes.
  - setDuration
```
public Span setDuration(Long duration)
```
    Measurement of duration in microseconds, used to support queries. This value should be set directly, where possible. Doing so encourages precise measurement decoupled from problems of clocks, such as skew or NTP updates causing time to move backwards. For compatibilty with instrumentation that precede this field, collectors or span stores can derive this by subtracting Annotation.timestamp. For example, SERVER_SEND.timestamp - SERVER_RECV.timestamp. If this field is persisted as unset, zipkin will continue to work, except duration query support will be implementation-specific. Similarly, setting this field non-atomically is implementation-specific. This field is i64 vs i32 to support spans longer than 35 minutes.
  - equals
```
public boolean equals(Object o)
```
    Overrides:
    
    equals in class Object
  - hashCode
```
public int hashCode()
```
    Overrides:
    
    hashCode in class Object
  - toString
```
public String toString()
```
    Overrides:
    
    toString in class Object
  - toZipkin
```
public zipkin.Span toZipkin()
```
    Changes this to a zipkin-native span object.

Class Span

Field Summary

Constructor Summary

Method Summary

Methods inherited from class java.lang.Object

Field Detail

startTick

Constructor Detail

Span

Method Detail

getTrace_id

setTrace_id

getName

setName

getId

setId

getParent_id

setParent_id

addToAnnotations

getAnnotations

setAnnotations

addToBinary_annotations

getBinary_annotations

setBinaryAnnotations

isDebug

setDebug

getTimestamp

setTimestamp

getDuration

setDuration

equals

hashCode

toString

toZipkin