Clients Rely on Us for Their Success

These are completed projects from leading clients in Silicon Valley:

 Innovative IT, 2020

Kafka DevOps, AWS Cloud DevOps

• AWS Lambda Function, AWS S3, AWS EC2, AWS RDS, AWS SQS, AWS Serverless deployment
• Kafka Security, Kafka encryption = configure encryption on kafka topics
• Java Builds, gradle , maven = build/release engineering with maven and gradle
• Postgres, database administration, sql scripts
• Microservices = deploy microservices in OCP
• Apigee = configure apiproxies for microservices and apikeys, configure deployment of REST api proxies
• OCP deployment and administration, Ansible, Jenkinsfile, Groovy
• Test Automation : JMeter, Junit, Jacoco, Smoke Test, Performance Test automation

Instaclustr

Kafka And Monitoring

• Create kafka topics, perform replication – ensure replication of schema registry and topics
• Automate deployment of kafka
• Administer, monitor kafka with Elasticsearch and confluent control center for performance and kafka related stats
• AWS , Docker, Monitoring, Cloud Admin, Ansible, Terraform
• Bash and python scripts for monitoring, alerting, Nagios check_mk, Kafka, and OpenStack services
• Adding inventory and decommissioning C-Series and B-Series servers in OpenStack Service Cloud
• Installing service assurance client to management nodes, nova nodes, and puppet master for monitoring
• Environment: Python, OpenStack, Ceph Storage, SolidFire NetApp Storage API, RESTApi, Ansible, Nagios, check_mk, Elasticsearch, Kibana, Logstash, Grafana, collectd
• AWS Cloud deployment and monitoring, Ansible

Google Cloud Services, 2019

• gcloud docker, gcloud container kubectl api for deployment , GCP CLI (https://cloud.google.com/sdk/gcloud/reference/container/clusters/create)
• Cloud Services and Cloud Operations, Kuberneter, GCP, Google Cloud SDK
• Cloud Automation, Google Cloud Deployments and CI/CD
• Firebase CLI , ReST API, Node.js, javascript and python scripting to access production
• Firebase Database , gcloud API, compute engine, Google Cloud TPUs, kubernetes and docker

Xavient = https://www.xavient.com , 2017

client = MUFG UnionBank of Los Angeles

Vocera = http://www.vocera.com, 2014

• Test vocera Servers, SIP Telephony Gateways, Client Gateways, jetty server
• Test Automation for : Web Services, SOA, Jetty Server
• SAN Certification Test Plan, API Tests for Call Processing with CUCM
• Test Devices for connectivity : Android Devices, iPhone, Cisco IP Phone, Motorola

            phone, smartphones, Samsung Galaxy

• Test Vocera Collaboration Suite, Vocera Connect apps downloaded from Google

            PlayStore and iOS App Store

• Installer testing , SSL Testing , Upgrade with Windows 2003, 2008, 2012
• Nuance Vocalizer Text-to-speech

Environment:

CUCM, IP Call Routing, SIP Telephony Gateway, Nuance Vocalizer, Mobile Devices, Android devices, iOS devices, VOIP Features, Voice-Over-IP Protocols and Stack, java, Jetty, WebServices

Cisco Systems   - http://www.cisco.com , 2015-16, 2018-19

APPLE (www. apple.com) , 2016

General Electric = http://www.ge.com, 2016

Install TeamCity Server = https://confluence.jetbrains.com/display/TCD9/Installing+and+Configuring+the+TeamCity+Server

Instaclustr

KAFKA MONITORING NOTES 

Q: What is HTTP Event Collector?

The Splunk HTTP Event collector is really pretty straight forward and you can find a lot of documentation online that would explain how it works much better than I can.  It’s just an alternate way of getting data into Splunk rather than the usual means (forwarder).  It’s basically just a listener that accepts raw or JSON data and sends it along to an index.

BACKGROUND

1. What is kafka-splunk-connect?

Splunk Connect for Kafka is a Kafka Connect Sink for Splunk with the following features:

• Data ingestion from Kafka topics into Splunk via Splunk HTTP Event Collector(HEC).
• In-flight data transformation and enrichment.

2. How do we install it ?

  https://github.com/splunk/kafka-connect-splunk

For Installation, we Need access to :

• Kafka hosts that need to be monitored
• SPLUNK DEV-STL instance access
• connect-distributed.properties file
• bootstrap.servers and plugin.path
• which is available for download

INFRASTRUCTURE

Q: Which SPLUNK instance is used for monitoring ?

access to any data for this POC will be through the MSE dev instance:

Q: What do we set values for “bootstrap.servers” and “plugin.path” in connect-distributed.properties file?

bootstrap.servers = kafka broker

plugin.path =  install directory of your Kafka Connect Sink and Source Connectors = place the jar file here for installation

Q: Where do we install the connector jar ?

the jar needs to be installed and configured on the Kafka host(s) per the instructions on Splunk/Github

Place the jar under “plugin.path” directory

Q: How do we start the connector?

.$KAFKA_HOME/bin/connect-distributed.sh $KAFKA_HOME/config/connect-distributed.properties

Q: How do we create connector task?

Run the following curl command for host = nc3-001b-ixb-sp and port = 8088 and below token

curl localhost:8083/connectors -X POST -H "Content-Type: application/json" -d '{

    "name": "kafka-connect-splunk",

    "config": {

      "connector.class": "com.splunk.kafka.connect.SplunkSinkConnector",

      "tasks.max": "3",

      "splunk.indexes": "kafka",

      "topics":"Kafka Control Metrics Reporter",

      "splunk.hec.uri": "xxxxxx:8088",

      "splunk.hec.token": "ff7810ff-7cd2-4756-876b-58bc119b3286"

    }

  }'   

Intuitive Surgical, 2017

AWS Helpful Links, FYI: