semconv
Used in:
components
- OverviewOverview
- VersionsVersions
- DependentsDependents
- DependenciesDependencies
<dependency>
<groupId>ai.corva.otel</groupId>
<artifactId>semconv</artifactId>
<version>1.1.4</version>
</dependency><?xml version="1.0" encoding="UTF-8"?>
<project xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 https://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<!-- This module was also published with a richer model, Gradle metadata, -->
<!-- which should be used instead. Do not delete the following line which -->
<!-- is to indicate to Gradle or any Gradle module metadata file consumer -->
<!-- that they should prefer consuming it instead. -->
<!-- do_not_remove: published-with-gradle-metadata -->
<modelVersion>4.0.0</modelVersion>
<groupId>ai.corva.otel</groupId>
<artifactId>semconv</artifactId>
<version>1.1.4</version>
<name>semconv</name>
<description>OpenTelemetry Semantic conventions for Corva</description>
<url>https://github.com/corva-ai/otel</url>
<licenses>
<license>
<name>MIT License</name>
<url>https://www.opensource.org/licenses/mit-license.php</url>
</license>
</licenses>
<developers>
<developer>
<id>smoke</id>
<name>Radoslav Kirilov</name>
<email>radoslav.kirilov@corva.ai</email>
<organization>Corva LLC.</organization>
</developer>
</developers>
<scm>
<connection>scm:git:git://github.com/corva-ai/otel.git</connection>
<developerConnection>scm:git:ssh://github.com:example/my-project.git</developerConnection>
<url>https://github.com/corva-ai/otel</url>
</scm>
<dependencies>
<dependency>
<groupId>io.opentelemetry</groupId>
<artifactId>opentelemetry-api</artifactId>
<version>1.47.0</version>
<scope>runtime</scope>
</dependency>
</dependencies>
</project>
Open source consumption has exploded, with estimates placing this year’s downloads at over 6.6 trillion. This reliance on open source components, now making up to 90% of the modern software application, has ushered in both unprecedented innovation and complex challenges for software supply chains.
View the Report