Recent Content
Possible deprecation of legacy HPE Edge Connect authentication
Hello all! We are working on an update to the HPE Edge Connect PowerPack that converts the dynamic applications to use the snippet framework. This will improve supportability, simplify troubleshooting, improve performance, and make it easier to customize the collections to suit your needs. As part of this, we are considering dropping support for "cookie" auth and requiring users to use API keys to connect SL1 to the Edge Connect Orchestrator. If you have a use case that precludes using an API key for this integration, please reach out and help us understand your parameters. Thanks!ScienceLogic Job: Sr. Manager, Engineering (Platform)
What you’ll be doing… This Senior Manager, Engineering role occupies a pivotal role at the intersection of technology and leadership, contributing to product strategy and owning the delivery of product commitments, while nurturing the growth and productivity of the engineering teams. Core responsibilities include: Providing technical leadership for multiple engineering teams within the Core Platform product line. Collaborating with product managers, designers, and other stakeholders to align product goals and delivery with company objectives and customer needs. Defining and refining engineering processes to promote a more efficient, effective and secure SDLC, including leading code reviews to ensure best practices (eg, style guidelines, accuracy, testability) Setting clear expectations with individuals based on their level and role and aligned to the broader organization's goals, meeting regularly to discuss performance, development, provide feedback and coaching. Visit the Job Posting for more details about the role and to applyScienceLogic Job: Sr. Manager, Engineering
What you’ll be doing… This Senior Manager, Engineering role occupies a pivotal role at the intersection of technology and leadership, contributing to product strategy and owning the delivery of product commitments, while nurturing the growth and productivity of the engineering teams. Core responsibilities include: Providing technical leadership for multiple engineering teams spanning two product lines in the Network Automation/Compliance and Enterprise Data Automation/Workflow Integration spaces. Collaborating with product managers, designers, and other stakeholders to align product goals and delivery with company objectives and customer needs. Defining and refining engineering processes to promote a more efficient, effective and secure SDLC, including leading code reviews to ensure best practices (eg, style guidelines, accuracy, testability) Setting clear expectations with individuals based on their level and role and aligned to the broader organization's goals, meeting regularly to discuss performance, development, provide feedback and coaching. Visit the Job Posting for more details about the role and to apply
LUA Cisco parse interfaces + CSV output
This script is designed to retrieve and parse network interface information from a cisco device, and then optionally print this information in either a human-readable format or as a CSV file. Here's a breakdown of its objectives: Retrieve Interface Information: The script sends commands to a network device to get the interface details (sendget('show interfaces','#')). It captures the output of these commands (local output = before()). Parse the Output: Theparse_interfacesfunction processes the output to extract relevant details about each interface, such as the interface name, description, IP address, MTU, encapsulation type, and packet statistics. Format the Information: The parsed information is stored in a table (interfaces). Print the Information: Ifenable_csv_printis set to0, the script prints the interface details in a human-readable format. Ifenable_csv_printis set to1, the script converts the interface details into CSV format using theinterfaces_to_csvfunction and prints the CSV string. The enable_csv_print variable controls whether the output is printed in a human-readable format (0) or as a CSV file (1). This allows for flexible output depending on the user's needs. -- Enable CSV output? enable_csv_print = 0 sendget('', '#') sendget('show interfaces','#') waitprompt() local output = before() -- print(output) local function parse_interfaces(output) local interfaces = {} local current_interface = {} for line in output:gmatch("[^\r\n]+") do if line:match("^GigabitEthernet") or line:match("^TenGigabitEthernet") then if next(current_interface) then table.insert(interfaces, current_interface) end current_interface = { interface = line } elseif line:match("^%s+Description:") then current_interface.description = line:match("Description:%s+(.*)") elseif line:match("^%s+Internet address is") then current_interface.ip_address = line:match("Internet address is%s+(%S+)") elseif line:match("^%s+MTU") then current_interface.mtu = line:match("MTU (%d+)") elseif line:match("^%s+Encapsulation") then current_interface.encapsulation = line:match("Encapsulation (%S+)") elseif line:match("^%s+%d+ packets input") then current_interface.packets_input = line:match("(%d+) packets input") elseif line:match("^%s+%d+ packets output") then current_interface.packets_output = line:match("(%d+) packets output") end end return interfaces end local function interfaces_to_csv(interfaces) local csv = "Interface,Description,IP Address,MTU,Encapsulation,Packets Input,Packets Output\n" for _, intf in ipairs(interfaces) do csv = csv .. string.format("%s,%s,%s,%s,%s,%s,%s\n", intf.interface, intf.description or "N/A", intf.ip_address or "N/A", intf.mtu or "N/A", intf.encapsulation or "N/A", intf.packets_input or "N/A", intf.packets_output or "N/A" ) end return csv end local interfaces = parse_interfaces(output) if enable_csv_print == 0 then for _, intf in ipairs(interfaces) do print(string.format("Interface: %s, Description: %s, IP Address: %s, MTU: %s, Encapsulation: %s, Packets Input: %s, Packets Output: %s", intf.interface, intf.description or "N/A", intf.ip_address or "N/A", intf.mtu or "N/A", intf.encapsulation or "N/A", intf.packets_input or "N/A", intf.packets_output or "N/A")) end end local csv = interfaces_to_csv(interfaces) if enable_csv_print == 1 then print(csv) endInterface admin/operationally down events
OK. So I'm fairly new to modifying events in SL1, but our NOC has requested that we research suppressing the "Poller: Interface operationally down" event if "Poller: Interface Admin down" is active on a given interface. That makes perfect sense to me. If an interface is admin down, then there is absolutely no need for the operationally down event/alert. Other tools I have administered in the past had this logic baked in out of the box, but that doesn't seem to be the case with SL1. I looked at using the Autoclear option for the Admin down event to have it clear the operationally down message, but I'd much rather just not have the operationally down event trigger at all if the interface is admin down. Any thoughts on how to get this configured? Thank you.User Groups- How to Join or Request to Co-Manage One
Hello Nexus Community Members, Have you had a chance to visit our User Groups? Most of our user groups are organized around topic, event, location or audience. They are all pertinent to ScienceLogic Products, Services and Customers. There are varying levels of privacy depending on the audience and content. Log In to the Nexus Community Click on the User Group you would like to Join Click on the Send Request to Join button If you think you would like to create and co-manage a user group with us, please message me directly and we can talk about the launch process and how this might benefit the community. Cheers, SaraNexus Community Weekly Highlights #9
Hello Nexus Community Members, We want to continue to welcome new members- we look forward to working with you. Pritam Wiseman AbsoluteBore vugale IvanP Radhika John4KBRSL1 jimco KyleTanaka Jeff_Kinny Feel free to share your ideas and feedback so we can get you the most helpful resources and information. Cheers, Sara- Community Manager
Heartbeats Monitoring - suggestion
Hello, One of our customer is using a lot of Custom Scripts, where we are monitoring their output by syslog. There is starting a problem, when script stuck or block. Then customer don't know about it. Is there any possibilities how to monitor, If these scripts are working? We have suggestion, that Custom Scripts can send also message like OK or KO. 2 Events will match these both. There should be an action (run book) for script is running like: em7_snippets.generate_alert(xtype = 1, xid=EM7_VALUES['%x'], message = 'script heartbeat') and not running with count like: if EM7_VALUES['%c'] >= 2: em7_snippets.generate_alert(xtype = 1, xid=EM7_VALUES['%x'], message = 'script is not running') There will be also 2 automation. For script heartbeat will be action for heartbeat every 5min (for example as schedules) and for some Device group. Second automation for not running will have action not running. I think, there will must be next two events which will be matched by "script heartbeat or script is not running". Also if new syslog message will come, the first events (mentioned above) will must clear these events for continue with actions and automatons. Do you think that it is possible to implement it? How will look Hardware usage when we will have more automations/actions or when we will have it on lot of devices? Do you think that it is construable? Thank you for your answers.
About Discussion Forums
A place for dialogue and discovery about our products and services
