Can't get new device icon to show
Hi all, I'm trying to upload a new device icon for a custom Powerpack I'm creating (Ruckus SNMP). I've taken a screenshot of the logo as a .png. First I tried to follow the documentation here, found a tool to convert the png to a svg, and SL shows me an error: Next, I just tried uploading the png in various sizes (128, 300, and 600). All of them successfully upload, and show an actual icon the Icon browser minus that grey frame (see screenshot below). However, when I apply this Icon in the Device Class view, the device itself just shows a blank window where the icon would be. Anyone had any experience doing this?10Views1like0CommentsSSL Certificate monitoring via UDP/TCP ports tab
I have worked with support on the UDP/TCP ports tab. How it works was not how I thought it would or should work. I thought it would list any open port on a server (this would be helpful) but it does not. Based on how we use the tool I would like this changed to be able to list all open ports and then have the system load all ssl certs assigned to those ports (it only does 443 today for ssl certs). We need an automated way to monitor SSL Certs. We built a custom dynamic app by port (one dynamic app per port number) to handle this but it is clunky and ssl monitoring should be something you address out of the box. Knowing what ports have an SSL cert and when it expires is as important as availability.35Views2likes0CommentsWhich Dynamic App is more efficient for Linux File System exceeds a threshold
Which Dynamic Application is more efficient for File System Utilization SL1 can trigger two different type of events for when a File System exceeds a threshold: File System exceeded events are generated via an Internal DA by SL1 and is executed every 5 minutes Host Resource Storage Utilization events are generated via a Discovered DA from the SNMP agent on the host and can be collected at 5, 10, or 15-minute interval I am trying to determine which one make more sense to use on linux servers and is not as taxing the data collectors.Solved50Views0likes1CommentIs anyone else running SL1 v12.1.2?
We were supposed to be upgraded to v12.2 but problems with Aurora (the AWS database offering) we have ben placed onto v12.1.2. We were handed the system on September the 9th, and the release notes are dated the 10th. It has zero backward compatibility with collectors (all must be on 12.1.2) and we've been plagued with critical system alerts before we even attached a collector. I kind of get the feeling that we're alpha testing this release.... ☹️ Can anyone else, give me some comfort and confirm that we are not the Guinea Pigs for this release?201Views1like6CommentsSL1 Themes after upgrading to v12.2.1.2
Upgraded to SL1 v12.2.1.2 last night and had some bumps but for most part my organization is doing okay. Seen several positive changes in the UI like a much improved Events page however I'm having problems with my themes. I have both a lab and a production systems. To keep myself from accidentally doing stuff in production when I think I'm in the lab, in the past I put a dark theme on production and a light theme on my lab. Since the upgrade I'm seeing light theme pages in certain pages, despite the fact that the dark theme is applied (and reapplied for good measure). Is this a known issue? Anyone else seeing this behavior?Solved48Views1like2CommentsOverlapping IP addresses
This might be an oldie... How should we manage devices which have multiple overlapping IP addresses. For example Layer3 switches or router HA pairs can have same IP addresses set up to two or multiple devices for routing high availability or management reasons. This then makes SL1 see same IP addresses in multiple devices. And that then generates events into System organization, events like: A Message Collector is managing multiple devices with an overlapping secondary IP address: Secondary IP address overlap on devices managed by Message Collector: 101 | Collector Groups: 44 | IP Address: 128.0.0.127 | Device IDs: 70999, 70998, 71001, 71009, 71005, 71003, 71006, 71004, 71007, 71002, 71013, 71012, 71015, 71010, 71014, 71008, 71016 Ok, that IP address can be deleted from database, but the nightly discovery again brings up the same issue next day. And because those are network devices where every now and then are some changes done in interfaces I believe we just have to have the Auto-Update enabled for those devices. So: is there a way to tell that please do not discover all IP addresses for this device is there a way to make SL1 accept that, some other way than creating pretty interesting regexes into event policies event policy is for system level so that not easily be just suppressed for some devices are there some other ideas how to manage this situationSolved69Views2likes2Comments