As part of this series of Oracle Enterprise Manager blogs we thought it would be useful to give a quick overview of how OEM13c users can monitor and control REDIS data store environments.
Why use OEM13c to monitor REDIS?
That’s a good question.
Other solutions exist for monitoring REDIS, however it’s the power of OEM13c combined with the AIDEV REDIS monitoring plugin that brings a lot more to the table…
First of all we can get true visibility of all REDIS environments – a single screen detailing all related targets, component health and core metric values. Have a look at this page, detailing current core metrics/health for 3 related REDIS targets…
We also can perform component control – stop/start actions can be easily configured and initiated (real time or scheduled) from OEM13c, allowing for greater automation across larger numbers of REDIS targets
For example, we can stop REDIS from the target’s dropdown menu:
By configuring custom content in stop_redis.sh & start_redis.sh (for example, a remote ssh to the REDIS host or an initiation of local control scripts) reusable mechanisms can be created – these can leverage the OEM13c credential framework to ensure security controls are enforced.
Or we can use the OEM job system to initiate the component control task – really useful when we need to schedule an en-masse stop/start across multiple targets:
OEM13c has alsways been a great monitoring tool. With REDIS, this is no different as we gain over 140 core monitoring metrics out of the box. These can be easily configured to alert against custom thresholds and hard-wired to notify the relevant people (eg. by email or through placement of an incident on a helpdesk system queue)
This is where it gets interesting. We have a wealth of metric data being collected by the OEM agents and stored/rolled up in the OEM repository. This allows the REDIS admin to compare and contrast metric data between targets and graphically view historical data – fantastic for root cause analysis investigation or trending performance/configuration changes.
Users can also create custom monitoring templates and template collections to standardise, extend and automatically enforce monitoring and alerting behaviour across the REDIS estate – useful for large estates where control is key
Sites can also leverage OEM’s reporting framework to create custom reporting solutions, mining and graphically rendering metric/configuration data collected from the REDIS estate by OEM13c – excellent for daily reports or MI summaries.
Configuration can be tracked and standardardised across the REDIS estate – again, excellent when running large estates and enforcing build/security standards
REDIS admins can also logically model application systems – related targets, for example web servers, app servers or hosts, can all be linked through associations in OEM to build logically related systems.
Dashboards can easily be created to graphically illustrate current system component status and highlight any issues…
Setting things up (a quick demo)
Ok, a quick overview of what’s required to set this up. We’ve got this detailed in our plugin documentation, so no need for too much detail.
You firstly need the plugin deployed to the OMS and agent in OEM13c.
The agent can be remote to REDIS, which is great – we can monitor lots of REDIS targets on different hosts, all through the one OEM agent.
We also need REDIS installed. For a sandpit environment, download from https://redis.io/download , extract the binaries and run a ‘make’.
At AIDEV we’ve published a deployment guide which details the steps required to configure password controlled connectivity so we’ll not go into detail here – just read the doc. This is required to allow OEM to communicate with REDIS.
Once REDIS is started we can look to add targets into OEM. Again, AIDEV’s doc covers this.
Configuring the target is pretty simple, with only a few parameters required to get things moving:
Once the target is added, metric data starts flowing in…
So, in Summary…
REDIS environments can be managed pretty easily using OEM13c + the AIDEV REDIS plugin. Setting things up is also pretty simple.
The plugin itself is very lightweight and can be deployed to any remote OEM agent with network connectivity to the REDIS endpoint being monitored. SSL comms are also supported.
Multiple REDIS targets can be managed by a single OEM agent, so it’s pretty flexible in it’s deployment options.
Once the monitoring data starts to flow in to OEM13c, adminstrators can make full use of OEM13c’s monitoring, alerting and reporting features.
The plugin datasheet can be found at https://bit.ly/3hsmtlH
If you’re interested in trialing it for your site, let us know.
For more info on the REDIS plugin, jump over to https://bit.ly/2FWtopC or drop us a comment here and we’ll get back to you.
AIDEV have the following plugins available and listed on the Oracle Extensibility Exchange:
- SSL certificate
- REDIS data store
For more information on our OEM plugins or how we can create plugins for your applications, reach out to us.
Subscribe to receive notification of updates to our blog posts…