CI Visibility

Find the Pipeline or Job slowing delivery

Guance CI Visibility collects supported GitLab and Jenkins CI results so DevOps and platform teams can examine Pipeline and Job status, duration, failure reasons, flame graphs, and related logs in one investigation path.

What CI Visibility helps you solve

Give every build, test, and deployment a traceable quality record

When delivery slows or fails, teams need to identify the affected Pipeline and Job, see where time accumulated, and inspect the failure context without rebuilding the run from several CI screens.

Is the delivery path healthy? Start with status and duration trends
Use CI Explorer views to compare Pipeline and Job executions over a selected time range. Filter and group supported CI data by project, branch, status, tag, or other reported attributes to separate an isolated failure from a recurring delivery problem.
View documentation
Is the delivery path healthy? Start with status and duration trends
Which Job delayed the release? Follow the Pipeline flame graph
Which Job delayed the release? Follow the Pipeline flame graph
Open a Pipeline execution and compare the time spent in its Jobs and stages. The flame graph and Job list expose execution order, duration, status, and the part of the run that failed or consumed disproportionate time.
View documentation
Move from a failed run to its logs and reported context
Review the failure reason, reported attributes, JSON details, and related logs available for the execution. Turn recurring failures or abnormal duration into a monitored trend while keeping CI provider and collection boundaries explicit.
View documentation
Move from a failed run to its logs and reported context

Frequently asked questions

What is CI Visibility?

CI Visibility records and analyses supported CI Pipeline and Job executions so teams can review status, duration, failure reasons, flame graphs, and related logs in a consistent explorer.

Which CI systems are documented by Guance?

Current Guance documentation describes built-in CI result collection and visualisation for GitLab and Jenkins. Verify the collection method and available attributes before extending the claim to another provider.

How does CI Visibility help shorten delivery investigations?

Teams can move from aggregate success and duration trends to one Pipeline, its Jobs, the failing stage, and available logs or execution details without manually reconstructing the run.

Related reading

Read distributed traces with flame graphs

Read distributed traces with flame graphs

Use trace visualisation to compare execution time and isolate application bottlenecks.

Product features
Apply a repeatable distributed-tracing investigation

Apply a repeatable distributed-tracing investigation

Move from service latency to a representative trace and the evidence around it.

Best practices
Observe a containerised Python Flask service

Observe a containerised Python Flask service

Instrument a Flask application and validate request context in its container environment.

Best practices
Automate Java APM injection for Docker

Automate Java APM injection for Docker

Set up Java instrumentation for container deployments and verify the resulting telemetry.

Best practices

Connect delivery evidence to production reliability

Continue to APM, logs, Error Tracking, DevOps guidance, documentation, and pricing.

Get started > View documentation > View pricing >