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

adding a new plugin to monitor AWS ASGs #2092

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

Conversation

jbrahy
Copy link

@jbrahy jbrahy commented Feb 23, 2025

Added an AWS ASG monitoring plugin for xbar.

This plugin tracks Auto Scaling Group health, displays real-time statuses, and provides direct links to the AWS Console.

Let me know if any changes are needed to contribute this to the repository!

@sprak3000 sprak3000 added shell image update Either needs an image or a file extension labels Feb 23, 2025
Copy link
Collaborator

@sprak3000 sprak3000 left a comment

Choose a reason for hiding this comment

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

Also could use an image (<xbar.image>) to show what the plugin looks like running, ideally with the menu expanded.

)

# Fetch Auto Scaling Groups Data
asg_data=$(/usr/local/bin/aws autoscaling describe-auto-scaling-groups --region "$REGION" --profile "$AWS_PROFILE" --output json)
Copy link
Collaborator

Choose a reason for hiding this comment

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

Not everyone may have the aws binary at that location. I think your path is specific to people who installed it via Homebrew on Intel based hardware. Mine is at /opt/homebrew/bin/aws due to install via Homebrew on Apple's M1 based mac.

Probably could get away with just omitting the path. Someone who installed it likely has it in their path.

Copy link
Author

Choose a reason for hiding this comment

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

oh, I completely missed that. I had it installed, but it wasn't in my path for some reason when it ran. I didn't get into the debugging, but I was surprised that /usr/local/bin wasn't in my pat,h and then I thought it might be related to the path within xbar but I didn't investigate it any further. I'll check that out and commit something new

Copy link
Author

Choose a reason for hiding this comment

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

I'm working on an image. Something weird happened and it's not working now. I'm getting a fork/exec error. I'll have some beers and get back into it tonight then I'll get an image.

Cheers!

Copy link
Author

Choose a reason for hiding this comment

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

Here are two images.

menu-bar
menu-bar-drop-down

jbrahy and others added 2 commits February 23, 2025 15:09
I love this. Thank you

Co-authored-by: Luis Cruz <[email protected]>
This makes sense

Co-authored-by: Luis Cruz <[email protected]>
Copy link
Author

@jbrahy jbrahy left a comment

Choose a reason for hiding this comment

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

Everything looks great.

I removed the absolute path for the aws executable. If the aws executable is called then it should be in your $PATH
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
image update Either needs an image or a file extension shell
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants