nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

IPam custom fields lacks yes/no field type?

adeimel

Is it possible to add yes/no custom fields to IPAM? This would be useful for marking IPs as covered by XYZ other system. ex. yes/no for ip is covered in npm or apm.

You could then easily run reports as to what ips are covered and which are not. A text field could be used but it seems like the custom fields should follow suit with the other Orion products and offer yes/no status for such things.

Find more posts tagged with

Accepted answers

mavturner

Haha, ok thanks for the full examples. I've logged a feature request for this in IPAM.

All comments

mavturner

Unfortunately there is not a Yes / No field. As you mentioned, this can be accomplished using a text field. What is your concern about using the test field?

adeimel

1. making it easy for end users to mark a checkbox rather than fill in a text field.

2. consistent customization through out the product family. In NPM and NPM land thwack is filled with user examples of using yes/no fields for various purposes.

Under IPAM reporting would be the most common example I can think of. ex. Is this ip being managed by say APM yes/no. Generate report for all active ips NOT currently monitored.

Value add there is being able to find new systems that come online without the proper setup. IPAM is always scanning so it acts as a good source of truth for audits such as that.

#2 can of course work with a text field... So i will go back to #1 and lazy end users.

mavturner

Haha, ok thanks for the full examples. I've logged a feature request for this in IPAM.