Skip to main content

New pipeline describe command

· 2 min read
Raúl Barroso
Raúl Barroso
Engineering
warning

This is a legacy platform changelog. The information reflected here may not represent current functionality and some links may be broken.

With Meroxa CLI version v1.5.0, we're introducing a new command pipeline describe to inspect more information about your pipeline.

For example, for a pipeline named my-meroxa-pipeline you would run:

$ meroxa pipelines describe my-meroxa-pipeline
UUID:   58776dd1-76e4-48aa-a2cc-4978b1ba486f
ID:     1915
Name:   my-meroxa-pipeline
State:  Healthy

Over time, we'll include new details to this command that will let you gather more information of your pipeline.

As an example of how a describe command could be useful, in v1.4.0, we included the ability to see a connector trace for those failed connectors via connectors describe:

$ meroxa connectors describe my-connector
       ID:   2470
     Name:   my-connector
     Type:   cosmosdb-source
  Streams:   (output) resource-2957-203946-demo
    State:   failed
 Pipeline:   my-pipeline
    Trace:   java.lang.RuntimeException: Client initialization failed. Check if the endpoint is reachable and if your auth token is valid
             at com.azure.cosmos.implementation.RxDocumentClientImpl.initializeGatewayConfigurationReader(RxDocumentClientImpl.java:392)
             at com.azure.cosmos.implementation.RxDocumentClientImpl.init(RxDocumentClientImpl.java:419)
             at com.azure.cosmos.implementation.AsyncDocumentClient$Builder.build(AsyncDocumentClient.java:241)
             at com.azure.cosmos.CosmosAsyncClient.<init>(CosmosAsyncClient.java:123)
             at com.azure.cosmos.CosmosClientBuilder.buildAsyncClient(CosmosClientBuilder.java:741)
             at com.azure.cosmos.kafka.connect.source.CosmosDBSourceTask.getCosmosClient(CosmosDBSourceTask.java:241)
             at com.azure.cosmos.kafka.connect.source.CosmosDBSourceTask.start(CosmosDBSourceTask.java:58)
             at org.apache.kafka.connect.runtime.WorkerSourceTask.execute(WorkerSourceTask.java:213)
             at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:184)
             at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:234)
             at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
             at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
             at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
             at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
             at java.base/java.lang.Thread.run(Thread.java:834)

To get the latest on the CLI, check out the Installation Guide.

For any questions or comments, please feel free to email us at [email protected] or reach out to us on Twitter.