io.micrometer.tracing.docs.SpanDocumentation Maven / Gradle / Ivy

Go to download
Show more of this group Show more artifacts with this name
Show all versions of micrometer-tracing Show documentation
Facade over tracing concepts
There is a newer version: 1.4.0
/**
 * Copyright 2022 the original author or authors.
 *
 * Licensed under the Apache License, Version 2.0 (the "License");
 * you may not use this file except in compliance with the License.
 * You may obtain a copy of the License at
 *
 * https://www.apache.org/licenses/LICENSE-2.0
 *
 * Unless required by applicable law or agreed to in writing, software
 * distributed under the License is distributed on an "AS IS" BASIS,
 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
 * See the License for the specific language governing permissions and
 * limitations under the License.
 */
package io.micrometer.tracing.docs;

import io.micrometer.common.docs.KeyName;

/**
 * In order to describe your spans via e.g. enums instead of Strings you can use this
 * interface that returns all the characteristics of a span. In Micrometer Tracing we
 * analyze the sources and reuse this information to build a table of known spans, their
 * names, tags and events.
 * 
 * We can generate documentation for all created spans but certain requirements need to be
 * met
 *
 * 

 * Metrics are grouped within an enum - the enum implements the
 * {@link SpanDocumentation} interface
 * If the span contains {@link KeyName} then those need to be declared as nested
 * enums
 * If the span contains {@link EventValue} then those need to be declared as nested
 * enums
 * The {@link SpanDocumentation#getKeyNames()} need to call the nested enum's
 * {@code values()} method to retrieve the array of allowed keys
 * The {@link SpanDocumentation#getEvents()} need to call the nested enum's
 * {@code values()} method to retrieve the array of allowed events
 * Javadocs around enums will be used as description
 * 
 *
 * @author Marcin Grzejszczak
 * @since 1.0.0
 */
public interface SpanDocumentation {

    /**
     * Empty key names.
     */
    KeyName[] EMPTY_KEY_NAMES = new KeyName[0];

    /**
     * Empty values.
     */
    EventValue[] EMPTY_VALUES = new EventValue[0];

    /**
     * Span name.
     * @return metric name
     */
    String getName();

    /**
     * Builds a name from provided vars. Follows the
     * {@link String#format(String, Object...)} patterns.
     * @param vars variables to pass to {@link String#format(String, Object...)}
     * @return constructed name
     */
    default String getName(String... vars) {
        if (getName().contains("%s")) {
            return String.format(getName(), (Object[]) vars);
        }
        return getName();
    }

    /**
     * Allowed events.
     * @return allowed events
     */
    default EventValue[] getEvents() {
        return EMPTY_VALUES;
    }

    /**
     * Allowed key names.
     * @return allowed key names - if set will override any key names coming from
     * {@link SpanDocumentation#overridesDefaultSpanFrom()}
     */
    default KeyName[] getKeyNames() {
        return EMPTY_KEY_NAMES;
    }

    /**
     * Additional key names.
     * @return additional key names - if set will append any key names coming from
     * {@link SpanDocumentation#overridesDefaultSpanFrom()}
     */
    default KeyName[] getAdditionalKeyNames() {
        return EMPTY_KEY_NAMES;
    }

    /**
     * Override this when custom span should be documented instead of the default one.
     * @return {@link io.micrometer.observation.docs.ObservationDocumentation} for which
     * you don't want to create a default span documentation
     */
    default Enum overridesDefaultSpanFrom() {
        return null;
    }

    /**
     * Returns required prefix to be there for tags. For example, {@code foo.} would
     * require the tags to have a {@code foo.} prefix like this: {@code foo.bar=true}.
     * @return required prefix
     */
    default String getPrefix() {
        return "";
    }

}