Site Search

Splunk

Splunk

Splunk Technology Blog No. 5 - Introducing the Splunk Upgrade Monitoring Package -

Introduction

Hello, this is Macnica Splunk support.
In this fifth installment of the Splunk technical blog, we will introduce the Splunk Upgrade Monitoring Package, a support service for upgrade work, which is essential for operating Splunk.

Do you have any problems?

Do you have any of the following concerns when upgrading Splunk?

  • I'm worried that there might be problems with the upgrade.
  • I don't know if the upgrade procedure is correct.

Service contents

Our monitoring package offers the following services to ensure smooth upgrades.

Review the procedure manuals created by the customer

  • Check for excess or omission of steps
  • Guidance on additional check items
  • QA support regarding the creation of procedure manuals

If you would like to meet remotely, we will conduct up to two meetings during the service period.

  • Working Example

    1st: Kickoff
    • Confirmation of support details
    • Information on the system for version upgrade
    2nd time: Adjusting work procedures
    To complement the review of procedure manuals via email, we will hold meetings to fine-tune the procedure manuals upon request.

If any problems occur on the day of the upgrade, our engineers will promptly provide you with a solution by referring to our upgrade knowledge.

  • Response flow

    Occurrence of a fault

    Contact us by phone or email

    We will guide you through the solution and procedures by phone or email.

What are your benefits?

By using this package, we can carry out the upgrade work by following a procedure manual that has been reviewed with detailed consideration of the customer's situation and with reference to our upgrade knowledge, thereby minimizing troubles on the day.

In addition, any problems that arise during the upgrade process can be resolved quickly, ensuring that the Splunk upgrade can be completed without delay to schedule.

Illustration

Let me introduce some real examples.

Procedure manual review
When reviewing procedure manuals, we check the procedures for the following points to prevent problems before they occur.

  • Incorrect command or directory
  • Add-on version upgrade procedure
  • Indexer and forwarder stop process missing

Same-day response example
After the upgrade, when checking the settings of each instance, we discovered that some of the universal forwarder settings had disappeared. After investigating the cause using the diag file, we discovered that there was a problem with communication between the deployment server (an instance for managing the settings of multiple universal forwarders) and each universal forwarder. We then added settings to the configuration file (outputs.conf) and restarted the system to resolve the issue.

Customer testimonials

We received thorough support even before the work began, which allowed us to work with peace of mind on the day.

contact address

If you are interested, please contact us at the following address.

in conclusion

Upgrading Splunk is an important step in operation, so please take advantage of our services to help reduce any problems that may occur during the process.
We look forward to hearing from you.

Inquiry/Document request

In charge of Macnica Splunk Co., Ltd.

Weekdays: 9:00-17:00