com.epam.reportportal.service

Class LoggingContext

java.lang.Object

com.epam.reportportal.service.LoggingContext

public class LoggingContext
extends java.lang.Object

Logging context holds thread-local context for logging and converts SaveLogRQ to multipart HTTP request to ReportPortal Basic flow: After start some test item (suite/test/step) context should be initialized with observable of item ID and ReportPortal client. Before actual finish of test item, context should be closed/completed. Context consists of Flowable with buffering back-pressure strategy to be able to batch incoming log messages into one request

See Also:

init(Maybe, Maybe, ReportPortalClient, Scheduler)

Field Summary

Fields

Modifier and Type	Field and Description
static int	DEFAULT_BUFFER_SIZE

Method Summary

Modifier and Type	Method and Description
static io.reactivex.Completable	complete() Completes context attached to the current thread
io.reactivex.Completable	completed() Marks flow as completed
void	emit(java.util.function.Function<java.lang.String,com.epam.ta.reportportal.ws.model.log.SaveLogRQ> logSupplier) Emits log.
static LoggingContext	init(io.reactivex.Maybe<java.lang.String> launchUuid, io.reactivex.Maybe<java.lang.String> itemUuid, ReportPortalClient client, io.reactivex.Scheduler scheduler) Initializes new logging context and attaches it to current thread
static LoggingContext	init(io.reactivex.Maybe<java.lang.String> launchUuid, io.reactivex.Maybe<java.lang.String> itemUuid, ReportPortalClient client, io.reactivex.Scheduler scheduler, int bufferSize, boolean convertImages) Initializes new logging context and attaches it to current thread

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Detail

DEFAULT_BUFFER_SIZE

public static final int DEFAULT_BUFFER_SIZE

See Also:

Constant Field Values

Method Detail

init

public static LoggingContext init(io.reactivex.Maybe<java.lang.String> launchUuid,
                                  io.reactivex.Maybe<java.lang.String> itemUuid,
                                  ReportPortalClient client,
                                  io.reactivex.Scheduler scheduler)

Initializes new logging context and attaches it to current thread

Parameters:

launchUuid - a UUID of a Launch

itemUuid - a Test Item UUID

client - Client of ReportPortal

scheduler - a Scheduler to use with this LoggingContext

Returns:

New Logging Context

init

public static LoggingContext init(io.reactivex.Maybe<java.lang.String> launchUuid,
                                  io.reactivex.Maybe<java.lang.String> itemUuid,
                                  ReportPortalClient client,
                                  io.reactivex.Scheduler scheduler,
                                  int bufferSize,
                                  boolean convertImages)

Initializes new logging context and attaches it to current thread

Parameters:

launchUuid - a UUID of a Launch

itemUuid - a Test Item UUID

client - Client of ReportPortal

scheduler - a Scheduler to use with this LoggingContext

bufferSize - Size of back-pressure buffer

convertImages - Whether Image should be converted to BlackAndWhite

Returns:

New Logging Context

complete

public static io.reactivex.Completable complete()

Completes context attached to the current thread

Returns:

Waiting queue to be able to track request sending completion

emit

public void emit(java.util.function.Function<java.lang.String,com.epam.ta.reportportal.ws.model.log.SaveLogRQ> logSupplier)

Emits log. Basically, put it into processing pipeline

Parameters:

logSupplier - Log Message Factory. Key if the function is actual test item ID

completed

public io.reactivex.Completable completed()

Marks flow as completed

Returns:

Completable