Skip to content
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

Interactive Message Response Size Handling #1051

Open
huseyinbabal opened this issue May 5, 2023 · 2 comments
Open

Interactive Message Response Size Handling #1051

huseyinbabal opened this issue May 5, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@huseyinbabal
Copy link
Contributor

huseyinbabal commented May 5, 2023

Overview

You can see the original context here

Botkube has interactive message system where you can select resource interactively and take actions e.g. select one of the pods and see logs. If the response size of pod list is too big, we return it as Slack attachment (which is expected, since Slack has plain text size limit).

You can see an example below.
pod_size_big

Acceptance Criteria

  • Provide configuration for reducing the size of resource list to work with interactive messages.
  • (Maybe) If resource list size is more then 4K, trim first 4K and show only that part with a message visible to end user.

Reason

For big k8s clusters, there might be lots of resources and we will see attachments while working with interactive messages.

@huseyinbabal huseyinbabal added the enhancement New feature or request label May 5, 2023
@sadath-12
Copy link
Contributor

I can help with this issue @huseyinbabal

@huseyinbabal
Copy link
Contributor Author

As we discussed 1-to-1, we can limit resources limit by line as 100, and it can be configurable via kubectl config section.

Pagination is out of context now.

This was referenced Sep 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants