Possibility to "scrape" or "forward" traces (not logs, not metrics) for Spring Boot 3

By -

I would like to find a way to scrape or forward the traces generated by Spring Boot 3 app.

We have a Spring Boot 3 app that does not make outbound HTTP calls. The app only takes requests and saves data in DBs. When saving to DB, it generates traces, representing the interaction with DBs.

This same app generates application logs. For those, we use promtail / splunk forwarder to tail and forward the logs to the log aggregation backend. This is transparent to the application layer.

This same app generates application metrics. For those, we use prometheus, and expose an endpoint, so prometheus comes and scrapes the metrics. The application layer is not sending things on its own.

In the above two cases, the app itself is not making any outbound calls to send the logs or the metrics.

The application does not have any HTTP clients, and on the network layer, for security reasons, the app itself will not be able to communicate out.

The issue arises when it comes to traces. It seems there is no way to scrape or forward the traces, only for the app to create some network outbound calls, which we cannot do.

Is there a way for Spring Boot apps to not send the traces directly?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more