Giter Club home page Giter Club logo

Comments (8)

0xdabbad00 avatar 0xdabbad00 commented on August 20, 2024 2

I ticketed #5 to provide some customization about what is displayed, but we'll focus on the filtering in this ticket.

It sounds like you need support for the --collapse-by-tag to be added to more resources @rafarost, such as RDS instances. I'll look into what I can do there.

Also, for any others reading this. Another option, which is not great, but could help for unique use cases, would be to edit your .json files yourself. For example, for the demo files you could run:

cat describe-instances.json | jq '.Reservations[].Instances[] | select(.Tags[].Value=="Web2")'

You would need to add back in the parents, but that would show only instances with a tag value of Web2 (Somehow you could probably maintain the parents with jq but I'm not sure how).

from cloudmapper.

Ph4rell avatar Ph4rell commented on August 20, 2024 1

Hello @0xdabbad00, got the same problem, how do we have to use the --collapse-by-tag ?

I tried to used it like this: --collapse-by-tag ValueTag but not working

Could you give us an example in the doc ?
Thank you,
Pierre

from cloudmapper.

rafarost avatar rafarost commented on August 20, 2024

That would be helpful. I was facing the same issue here. I started looking into the code, and realized that AWS CLI does not return the tags. You have to make an extra call to gather tags (describe-tags). So, I did a quick workaround to group nodes by "prefix". If you follow a certain naming convention on your AWS resources, that will help solving your issue too. But, I'm still having issues with some resources that are generated automatically and does not follow naming conventions. Tags will be really nice.

from cloudmapper.

0xdabbad00 avatar 0xdabbad00 commented on August 20, 2024

There is a --collapse-by-tag filter currently in the prepare step. This was added for cases where people are handling auto-scaling on their own, without using AWS's proper autoscaling groups, so they have dozens or more EC2s that are all exactly the same. That could help you here.

It sounds like you might have say an account with different applications or environments in it that have some tag, let's say it's tagged prod and staging, so you want to see just the prod resources. I worry that if we limit your view to only the prod resources, it will hide communication paths that may exist to the staging resources that you would want to be aware of. Maybe you don't care? Can you explain your use case a bit more and desired output so I can make sure I get this right?

I'm also thinking about filtering down to a single VPC or Subnet, which could help as well.

from cloudmapper.

rafarost avatar rafarost commented on August 20, 2024

In my case I'm actually using the --collapse-by-tag feature. It helped me a lot on ec2 instances. But, I do have a similar scenario on RDS instances, which makes really hard to read the graph. Since I know that all the instances have the same network setup, and all of them follow a naming convention, I did an implementation to group them by a prefix. That worked nice for me. But, group by tag would be much more elegant. Gather tags will also be nice for ELB's. For instance, when you have all ELB's being auto-generated, with random names. Their tags will actually have more information regarding the services behind them. So, If you have an option to name them according an specific tag, would be really nice to make the graph more readable.

from cloudmapper.

ngerstle avatar ngerstle commented on August 20, 2024

The ability to toggle a view (or collapse-by-tag, which I just saw) for some nodes would be fantastic.
Many of the accounts/services I've tried mapping have underlying non-amazon infrastructure services (consul/prometheus/logging) that clutter and obscure all the other network connections because they connect to all nodes.
Being able to toggle (especially in browser) visibility for all resources with a given tag would be good, and dynamically selecting displayed tags would be fantastic.

from cloudmapper.

GauravThukral avatar GauravThukral commented on August 20, 2024

I am trying to use --collapse-by-tag when using python cloudmapper.py prepare. In AWS tag there is key Environment which has enviornment name . How can i use same in command.

python cloudmapper.py prepare --account-name tmonpe --collapse-by-tag Environment:Environment name

How to use key Value pair in -collapse-by-tag ?

Any updates?

from cloudmapper.

0xdabbad00 avatar 0xdabbad00 commented on August 20, 2024

Filtering by tags resolved in #343

from cloudmapper.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.