Skip to content

Initial Draft of Confluent Cloud Document #5495

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Conversation

akhil-sumologic
Copy link
Collaborator

Purpose of this pull request

This is a new app and the initial draft version. We’ll refine it further based on customer feedback.

Note: Dashboard's images will be cropped and updated appropriately once the dashboards are finalized.

Select the type of change

  • Minor Changes - Typos, formatting, slight revisions
  • Update Content - Revisions, updating sections
  • New Content - New features, sections, pages, tutorials
  • Site and Tools - .clabot, version updates, maintenance, dependencies, new packages for the site (Docusaurus, Gatsby, React, etc.)

Ticket (if applicable)

https://sumologic.atlassian.net/browse/SUMO-264003

@akhil-sumologic akhil-sumologic added the do-not-merge Pull requests that should not be merged label Jun 19, 2025
@cla-bot cla-bot bot added the cla-signed Contributor approved, listed in .clabot file label Jun 19, 2025
* Analyze trends in CPU minutes consumed over time to optimize cost and capacity planning for your Confluent Cloud deployment.
* Compare current CPU usage across different compute pools to balance workloads and improve overall system efficiency.

<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/ConfluentCloud/Confluent-Cloud-Compute-Pool.png')} alt="Confluent Cloud - Compute Pool" style={{border: '1px solid gray'}} width="800" />
Copy link
Collaborator

@jpipkin1 jpipkin1 Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you trim the blank space from the bottom of the Compute Pool dashboard screenshot?

* Track active connections, request bytes, and response bytes to identify potential bottlenecks or unusual traffic patterns.
* Analyze request count trends over time to understand usage patterns and plan for capacity needs.

<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/ConfluentCloud/Confluent-Cloud-Kafka-Cluster.png')} alt="Confluent Cloud - Kafka Cluster" style={{border: '1px solid gray'}} width="800" />
Copy link
Collaborator

@jpipkin1 jpipkin1 Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also trim the blank space from the bottom of the Kafka Cluster dashboard screenshot?

* Track schema count trends over time to manage growth and capacity planning for your Schema Registry.
* Correlate request counts with operation types to identify unusual spikes or drops in schema-related activities.

<img src={useBaseUrl('https://sumologic-app-data-v2.s3.amazonaws.com/dashboards/ConfluentCloud/Confluent-Cloud-Schema-Registry.png')} alt="Confluent Cloud - Schema Registry" style={{border: '1px solid gray'}} width="800" />
Copy link
Collaborator

@jpipkin1 jpipkin1 Jun 20, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you also trim the blank space from the bottom of the Schema Registry dashboard screenshot?

Copy link
Collaborator

@jpipkin1 jpipkin1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR looks great, @akhil-sumologic. I made minor changes (see commit "Updates from review").

Some of the screenshots could be trimmed. But if you can't trim them, that's okay.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla-signed Contributor approved, listed in .clabot file do-not-merge Pull requests that should not be merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants