<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rubina Shaik on Medium]]></title>
        <description><![CDATA[Stories by Rubina Shaik on Medium]]></description>
        <link>https://medium.com/@shaikrubina094?source=rss-b4911ab1767d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*0K47xyXf8JTL-SCg04e-Vw.jpeg</url>
            <title>Stories by Rubina Shaik on Medium</title>
            <link>https://medium.com/@shaikrubina094?source=rss-b4911ab1767d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 20:09:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@shaikrubina094/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How to pass custom OIDC Claims from WSO2 Identity Server to WSO2 API Manager in OIDC Federated…]]></title>
            <link>https://medium.com/@shaikrubina094/how-to-pass-custom-oidc-claims-from-wso2-identity-server-to-wso2-api-manager-in-oidc-federated-07806a923f83?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/07806a923f83</guid>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[wso2-identity-server]]></category>
            <category><![CDATA[oidc]]></category>
            <category><![CDATA[sso]]></category>
            <category><![CDATA[wso2]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Thu, 05 Mar 2026 18:37:42 GMT</pubDate>
            <atom:updated>2026-03-05T18:37:42.252Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>How to pass custom OIDC Claims from WSO2 Identity Server to WSO2 API Manager in OIDC Federated Authentication</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Dbn3mzGXEnUkg5BgvlK8jw.png" /></figure><p>If you’ve found your way here, you are someone who has configured WSO2 Identity Server As External IDP with WSO2 API Manager using OIDC. Or if you’re someone who is still working on the configuration, I recommend you go through the blogs [1] and [2], which provide all required steps in detail.</p><p>In OIDC Federation flow, all the roles from the Identity Server are sent under the claim “group” to the API Manager. We map IDP claim “groups” to the local claim “role”. These groups will then appear in the ID token and can be mapped to the corresponding APIM roles. This is the only claim you need to pass under the OIDC scopes for provisioning of users and roles in API Manager.</p><p>Now, consider a scenario where you want to pass other user attributes like name, organization, mobile number, etc in the OIDC Federated flow. Or, maybe you want to enable application sharing among the users, for which the default implementation picks the organization’s claim as the group ID[3]. Users that belong to a single group can view each others’ subscriptions and applications (provided you have enabled group sharing). All these require you to pass certain extra attributes from the Identity Provider.</p><p>In this article, we will see how to pass custom OIDC claims from Identity Server to WSO2 API Manager.</p><p>For this use case, I’m using WSO2 API Manager-4.5.0 and IS-7.2.0.</p><p>Kindly note that, this article assumes that you have a running setup of OIDC Federated Identity Server with WSO2 API Manager.</p><p>Configurations on Identity Server.</p><p>1. By default, the “organization” claim is not available in the OIDC claims for both IS and APIM, hence we will first create a new attribute for the claim “organization.</p><p>Expand the <strong>User Attributes and Stores</strong> section on the left navigation menu and click on the <strong>Attributes</strong> option.</p><p>2. Next, select<strong> OpenID Connect</strong> under the <strong>Manage Attribute Mappings</strong> section.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KywACqsFSST7D5u-tKqlGg.png" /></figure><p>3. You will see a page listing all the OIDC attributes. Among the listed attributes, you will see that the “organization” attribute is not available by default. Therefore, let’s add it.</p><p>Click <strong>Add New Attribute</strong> button, you will see a page asking you to enter a name for OIDC attribute and its use attribute mapping. You need to add an attribute name and a mapping like below:</p><p><strong>OIDC Attribute</strong>: org_name<br><strong>User Attribute to map to</strong>: <a href="http://wso2.org/claims/organization">http://wso2.org/claims/organization</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*13vSJtKAsRNkYqXtu1G1Rg.png" /></figure><p>4. Once the attribute mapping is added, it looks like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3GM-HoU8jGJFe9zi1d6O_w.png" /></figure><p>5. In APIM/IS the user claims are bonded with scopes. So to include the requested claims in the response, the corresponding claim should be associated with the requested scope</p><p>So click on <strong>Scope</strong>. Under the listed scopes, select <strong>Open ID</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d8_Osz5m9ESmdhoIwKDvkQ.png" /></figure><p>6. Under <strong>Manage Attributes</strong>, click on Add <strong>New attribute</strong>. This will allow you to select all the user attributes you wish to add under the Open ID scope. You can select the <strong>“organization” </strong>attribute here. You can also select other attributes like <strong>Full name, Last Name, address,</strong> etc.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RidYpm64ePToU7ykFBVidQ.png" /></figure><p>You will see all the selected attributes will be shown under the OIDC scope like below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KwRRgY7vVKJgeCX0psErGQ.png" /></figure><p>7. Now that the attribute has been added to the scope, we need to select the user attributes that are allowed to be shared with this application. Navgate to Applications from the left navigation and select your service provider.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SmrcUd0K9Z_BOZqlfNSCXg.png" /></figure><p>8. Under the <strong>User Attributes</strong> tab of the application and select the required user attributes to be shared. Here I’ve selected <strong>First Name, Last Name, address and email</strong>, you can select other user attributes as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZD1sAIzkeagb9GyWr077ug.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DWnzStxulaIlF5tIOi-asQ.png" /></figure><p>9. Under the <strong>Attributes without a scope</strong>, select the “<strong>org_name</strong>” attribute.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s7jJ1ba7W2xcwobrvZ4pjg.png" /></figure><p>Now we have completed the configuration on the Identity Server. Let’s move to the API Manager.</p><p><strong>Configurations on API Manager</strong></p><p>1. By default, the claim ‘organization’ is not available in APIM-4.5.0 OIDC claim dialect(‘http://wso2.org/oidc/claim&#39;). So the ‘organization’ claim needs to be added to the OIDC claim dialect.</p><p>Log into the carbon management console. (https://localhost:9443/carbon).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kSQYsgOCOT-wzAYrrifFg.png" /></figure><p>2. Navigate to <strong>Main </strong>&gt; <strong>Claims</strong> &gt; <strong>Add</strong> &gt; <strong>Add External Claim</strong>. Click <strong>Add External Claim</strong> to add the organization claim to <strong>oidc</strong> claim dialect as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eH-YbzpDb3MNYF2NmhwwuA.png" /></figure><p>3. From the above step, you will see that this claim is added under the OIDC claims as below:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DSJw8W0xXyQwB1E7mWRPpg.png" /></figure><p>4. OOTB, there are no claims associated with the scope ‘openid’ in APIM-4.5.0, so this association also needs to be done. Under the OIDC Scopes, select <strong>List -&gt; openid</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ncehe-ZS0Kc00oIQQT9vhw.png" /></figure><p>5. Under the <strong>openid </strong>scope, select organization claim from the drop-down menu. Click <strong>Add</strong> and <strong>Finish</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8ldbiyvYS6BvbSXaAyUE6g.png" /></figure><p>6. Next, add a mapping for the <strong>organization </strong>claim under the <strong>Claim configuration</strong> under the <strong>Identity Provider</strong> configurations as below. As I’m also passing claims like name, address, email, I’ve added those mappings as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zkVDpPJX2i1yiCIbtdPi9A.png" /></figure><p>7. Once the above steps are done, you need to add the below configuration in the deployment.toml file of API Manager, to enable using the custom claim mappings, and restart your API Manager Server.</p><pre>[authentication.endpoint]<br>enable_custom_claim_mappings = true</pre><p><em>The next time when you login using the user provisioned from IS, you will observe that the user profile in the API Manager has been updated with the user attributes passed from IS.</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hEcV6sOLgvw6TdLXJedrpw.png" /></figure><p>Similarly, you can pass any required OIDC claim through the federated authentication flow using this approach.</p><p>If you run into any issues while following this configuration, feel free to leave a comment below. I’d be happy to assist.</p><p>[1] <a href="https://sumudusahanweerasuriya.medium.com/wso2-api-manager-portal-oidc-sso-with-wso2-identity-server-7-0-0-c2c786c588f1">https://sumudusahanweerasuriya.medium.com/wso2-api-manager-portal-oidc-sso-with-wso2-identity-server-7-0-0-c2c786c588f1</a></p><p>[2] <a href="https://medium.com/@chethanbs21/configure-wso2-identity-server-7-1-0-as-an-external-idp-for-wso2-api-manager-4-5-0-using-oidc-sso-8952dd7bda3d">https://medium.com/@chethanbs21/configure-wso2-identity-server-7-1-0-as-an-external-idp-for-wso2-api-manager-4-5-0-using-oidc-sso-8952dd7bda3d</a></p><p>[3] <a href="https://apim.docs.wso2.com/en/4.5.0/consume/manage-application/sharing-applications/sharing-applications/">https://apim.docs.wso2.com/en/4.5.0/consume/manage-application/sharing-applications/sharing-applications/</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=07806a923f83" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When Concentration Slips Away: A Personal Story]]></title>
            <link>https://medium.com/women-write/when-concentration-slips-away-a-personal-story-dab4f563b23b?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/dab4f563b23b</guid>
            <category><![CDATA[work-life-balance]]></category>
            <category><![CDATA[women]]></category>
            <category><![CDATA[screentime]]></category>
            <category><![CDATA[careers]]></category>
            <category><![CDATA[worklife]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Mon, 22 Sep 2025 08:57:42 GMT</pubDate>
            <atom:updated>2025-09-23T12:06:16.133Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i0vl6DmZ7jw7IPBlcPxKBg.png" /></figure><p>In my college days, I had an incredible level of concentration. All I used to do during a session was simply <em>be in the moment</em>. Those 45 minutes in class were enough for me to absorb everything being taught. I didn’t even need to revise my concepts later — just listening carefully was enough to appear for tests with confidence. Back then, I never questioned or even noticed this ability; it just felt natural.</p><p>But a few days ago, reality hit me. I was attending a technical session, something I was genuinely enthusiastic about. In the beginning, I was eager, keen to learn something new, and fully attentive. Yet slowly, I found myself zoning out. My mind drifted away, and before I knew it, I had completely lost track of what was happening in the session.</p><p>For a moment, I thought maybe the topic was just not intresting enough to keep me engaged, and that’s why I zoned out. But no — that wasn’t the case. I realized it was happening even when I was doing the things I love.</p><p>Take last weekend, for example. I convinced my husband to watch <em>Emily in Paris</em> with me. (It’s not his genre at all, but he agreed because I like it.) The show has everything I enjoy — fashion, drama, women navigating their careers — literally all the elements that usually keep me hooked.</p><p>But you won’t believe what happened. Just ten minutes into the episode, I had already grabbed my phone — without even realizing it — and started scrolling. It hit me later: this wasn’t supposed to happen. This is my favorite series, something I look forward to, and yet I couldn’t give it my full attention.</p><p>That scared me. If I can’t even stay present for the things I genuinely enjoy, what does that say about my everyday life? It’s not just unproductive — it feels like I’m robbing myself of experiences that once brought me joy. And it made me pause and think, <em>what am I even doing?</em></p><p>It’s not just that. Many a times I also find myself endlessly checking my phone for online shopping or making impulsive purchases I probably don’t even need. These little things were eating away my time, and it’s not like I’m free — I have so many important action items related to work, hobbies, and home. Yet somehow, I allowed myself to be pulled into endless scrolling.</p><p>I even set timers on apps to limit my daily usage, but I somehow extended those limits without guilt, thinking it wasn’t a big deal, that “everyone does it.” But that’s not who I am. I’m more than this. I can’t let an appliance control me; I should be the one controlling it.</p><p>To tackle this, I started a simple yet effective challenge: before starting any task, I tell myself I won’t touch my phone until it’s done. I convince my brain that it’s not yet “phone time.” This small mental challenge has helped me stay focused, at least over the past 3–4 days, and I hope to continue it.</p><p>Along with this, I’ve added some practical changes to my routine:</p><p>Phone-free zones: Like at the gym, where I focus only on myself.</p><p>Mindful mornings: Avoiding my phone first thing in the morning to start the day calmly.</p><p>Walks with my husband: Engaging in meaningful conversations instead of being glued to screens.</p><p>Turning off notifications: Reducing the constant pull of apps that interrupt my focus.</p><p>They might seem like small steps, but collectively, they’ve started to make a real difference. I feel like I’m slowly reclaiming my control.</p><p>Concentration isn’t something that disappears overnight; it slips away quietly, one notification, one distraction, one “just five minutes” at a time. And the same way, I believe it can be rebuilt — through small, consistent efforts, self-awareness, and honest reflection.</p><p>If there’s one message I want to leave with anyone reading this, it’s this: check in with yourself. Notice where your attention goes. Ask whether it’s adding value to your life or just stealing your time. And most importantly, don’t let guilt over being distracted hold you back — let it motivate you to do better.</p><p>This is me, taking the first steps to win back my focus. And if you’re struggling with the same, maybe today could be your first step too. Feel free to share your thoughts in the comments, or tell me about something that has actually helped you stay focused — I’d love to hear your experience.</p><p>Thank you for reading.😊</p><p>This article is published in Women Write Publication. A growing, strong community built by women for women. All thoughts are welcome.</p><p>To join this community, read these submission guidelines.</p><p><a href="https://medium.com/women-write/submission-guidelines-for-women-write-publication-864c067b4d2d">Submission Guidelines for Women Write Publication</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=dab4f563b23b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/women-write/when-concentration-slips-away-a-personal-story-dab4f563b23b">When Concentration Slips Away: A Personal Story</a> was originally published in <a href="https://medium.com/women-write">Women Write</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Logs on the move: Streaming WSO2 API Manager Logs to ELK Stack]]></title>
            <link>https://medium.com/@shaikrubina094/logs-on-the-move-streaming-wso2-api-manager-logs-to-elk-stack-834c8019ac9c?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/834c8019ac9c</guid>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[elk]]></category>
            <category><![CDATA[logstash]]></category>
            <category><![CDATA[kibana]]></category>
            <category><![CDATA[wso2]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Tue, 29 Jul 2025 16:41:29 GMT</pubDate>
            <atom:updated>2025-07-29T16:47:51.305Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Logs on the Move — Streaming WSO2 API Manager Logs to ELK Stack</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uVukTrDt6X6PFIeSj1l9gQ.jpeg" /></figure><p>On our journey to make WSO2 API Manager more observable, we’ve already explored the cloud-native tool Datadog and unpacked the power of modern monitoring stacks. In this post, I’ll walk you through how I shipped WSO2 logs to Elasticsearch using Filebeat and Logstash, the challenges I faced (hello, file permissions and index invisibility 🙃), and how I got everything wired up and searchable in Kibana. If you’ve ever stared at a blank index screen wondering “Why isn’t my data showing up?”, this one’s for you.</p><h3>Understanding the ELK Architecture</h3><p>Before we get into the nuts and bolts, let’s break down what ELK really is:</p><ul><li><strong>Elasticsearch</strong> is the heart of the stack — a powerful search and analytics engine that stores and indexes your data.</li><li><strong>Logstash</strong> is the data processor. It ingests logs, transforms them using filters (like parsing JSON or extracting fields), and sends them to Elasticsearch.</li><li><strong>Kibana</strong> is the visualizer. It reads from Elasticsearch and lets you explore your data with dashboards, charts, and search queries.</li><li><strong>Filebeat</strong> (often added to the stack, making it “ELK + Beats”) is a lightweight shipper that tails your log files and forwards them to Logstash or Elasticsearch.</li></ul><p>In simple terms:</p><p>[ WSO2 Log File ] → Filebeat → Logstash → Elasticsearch → Kibana</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ZkulDo-2tIzPj1SoQHBwsQ.png" /></figure><p>This modular design makes ELK incredibly flexible. You can parse and shape data in Logstash, ship it from multiple sources via Filebeat, and analyze everything in one place with Kibana.</p><p>Enough talk — let’s dive into the setup and get this ELK party started!</p><h3><strong>Configure WSO2 API Manager:</strong></h3><p><strong>1. Update deployment.toml</strong></p><ul><li>Go to wso2am-4.x.x/repository/conf/ and enable ELK analytics by adding:</li></ul><pre>[apim.analytics]<br>enable = true<br>type = &quot;elk&quot;</pre><p><strong>2. Enable Logging in log4j2.properties</strong></p><p>2.1. Add to appenders list:</p><pre>appenders = APIM_METRICS_APPENDER, …</pre><p>2.2 Define APIM_METRICS_APPENDER:</p><pre>appender.APIM_METRICS_APPENDER.type = RollingFile<br>appender.APIM_METRICS_APPENDER.name = APIM_METRICS_APPENDER<br>appender.APIM_METRICS_APPENDER.fileName = ${sys:carbon.home}/repository/logs/apim_metrics.log<br>appender.APIM_METRICS_APPENDER.filePattern = ${sys:carbon.home}/repository/logs/apim_metrics-%d{MM-dd-yyyy}-%i.log<br>appender.APIM_METRICS_APPENDER.layout.type = PatternLayout<br>appender.APIM_METRICS_APPENDER.layout.pattern = %d{HH:mm:ss,SSS} [%X{ip}-%X{host}] [%t] %5p %c{1} %m%n<br>appender.APIM_METRICS_APPENDER.policies.type = Policies<br>appender.APIM_METRICS_APPENDER.policies.time.type = TimeBasedTriggeringPolicy<br>appender.APIM_METRICS_APPENDER.policies.time.interval = 1<br>appender.APIM_METRICS_APPENDER.policies.time.modulate = true<br>appender.APIM_METRICS_APPENDER.policies.size.type = SizeBasedTriggeringPolicy<br>appender.APIM_METRICS_APPENDER.policies.size.size=1000MB<br>appender.APIM_METRICS_APPENDER.strategy.type = DefaultRolloverStrategy<br>appender.APIM_METRICS_APPENDER.strategy.max = 10</pre><p>2.3 Add to loggers list:</p><pre>loggers = reporter, …</pre><p>2.4 Configure reporter logger:</p><pre>logger.reporter.name = org.wso2.am.analytics.publisher.reporter.elk<br>logger.reporter.level = INFO<br>logger.reporter.additivity = false<br>logger.reporter.appenderRef.APIM_METRICS_APPENDER.ref = APIM_METRICS_APPENDER</pre><h3><strong>Configure ELK Stack</strong></h3><p>Instead of downloading and configuring Elasticsearch, Logstash, Kibana, and Filebeat individually — which can be tedious and error-prone — I opted for a much cleaner approach: <strong>Docker Compose</strong>. With just one YAML file, I can spin up all the necessary components as isolated containers, define dependencies between them, and ensure everything talks to each other out of the box. It’s a huge time-saver and makes managing and tearing down the entire ELK stack effortless.</p><h4>1. Folder Structure (Recommended)</h4><p>Organize your files like this:</p><p>ELKsetup/</p><pre>├── docker-compose.yaml<br>├── logstash/<br> └── logstash.conf<br>├── filebeat/<br> └── filebeat.yml</pre><p>2. Create a docker-compose file with the below content:</p><pre>version: &quot;3.8&quot;<br><br>services:<br>  elasticsearch:<br>    image: docker.elastic.co/elasticsearch/elasticsearch:7.17.9<br>    container_name: elasticsearch<br>    environment:<br>      - discovery.type=single-node<br>      - xpack.ml.enabled=false   # disables machine learning<br>      - bootstrap.memory_lock=true<br>      - &quot;ES_JAVA_OPTS=-Xms512m -Xmx512m&quot;<br>    ulimits:<br>      memlock:<br>        soft: -1<br>        hard: -1<br>    ports:<br>      - &quot;9200:9200&quot;<br>    healthcheck:<br>      test: [&quot;CMD-SHELL&quot;, &quot;curl -s http://localhost:9200/_cluster/health | grep -vq &#39;\&quot;status\&quot;:\&quot;red\&quot;&#39;&quot;]<br>      interval: 30s<br>      timeout: 10s<br>      retries: 5<br>    networks:<br>      - elk<br><br>  kibana:<br>    image: docker.elastic.co/kibana/kibana:7.17.9<br>    container_name: kibana<br>    ports:<br>      - &quot;5601:5601&quot;<br>    depends_on:<br>      elasticsearch:<br>        condition: service_healthy<br>    environment:<br>      - ELASTICSEARCH_HOSTS=http://elasticsearch:9200<br>    healthcheck:<br>      test: [&quot;CMD&quot;, &quot;curl&quot;, &quot;-f&quot;, &quot;http://localhost:5601&quot;]<br>      interval: 30s<br>      timeout: 10s<br>      retries: 5<br>    networks:<br>      - elk<br><br>  logstash:<br>    image: docker.elastic.co/logstash/logstash:7.17.9<br>    container_name: logstash<br>    ports:<br>      - &quot;5000:5000&quot;       # Beats input<br>      - &quot;9600:9600&quot;       # Monitoring API<br>    volumes:<br>      - ./logstash/:/usr/share/logstash/pipeline<br>    depends_on:<br>      elasticsearch:<br>        condition: service_healthy<br>    environment:<br>      - LS_JAVA_OPTS=-Xms512m -Xmx512m<br>    networks:<br>      - elk<br><br>  filebeat:<br>    image: docker.elastic.co/beats/filebeat:7.17.9<br>    container_name: filebeat<br>    user: root<br>    depends_on:<br>      logstash:<br>        condition: service_started<br>    volumes:<br>      - ./filebeats/filebeat.yml:/usr/share/filebeat/filebeat.yml:ro<br>      - /var/lib/docker/containers:/var/lib/docker/containers:ro<br>      - /var/log:/var/log:ro<br>      - /Users/shaikrubina/ELKsetup/wso2am-4.5.0/repository/logs/apim_metrics.log:/mnt/logs/apim_metrics.log:ro<br><br>    networks:<br>      - elk<br><br>networks:<br>  elk:<br>    driver: bridge</pre><h3>Configuring Logstash</h3><p>Logstash acts as the data pipeline that reads logs from Filebeat, parses them, and sends them to Elasticsearch.</p><p>Create a file named logstash.conf under the logstash/ folder with the following content:</p><pre>input {<br>beats {<br>port =&gt; 5044<br>}<br>}<br>filter {<br>grok {<br>match =&gt; [&quot;message&quot;, &quot;%{GREEDYDATA:UNWANTED}\ apimMetrics:%{GREEDYDATA:apimMetrics}\, %{GREEDYDATA:UNWANTED} \:%{GREEDYDATA:properties}&quot;]<br>}<br>json {<br>source =&gt; &quot;properties&quot;<br>}<br>}<br>output {<br>if [apimMetrics] == &quot; apim:response&quot; {<br>elasticsearch {<br>hosts =&gt; [&quot;http://elasticsearch:9200&quot;]<br>index =&gt; &quot;apim_event_response&quot;<br>user =&gt; &quot;elastic&quot;<br>password =&gt; &quot;Admin1234&quot;<br>}<br>} else if [apimMetrics] == &quot; apim:faulty&quot; {<br>elasticsearch {<br>hosts =&gt; [&quot;http://elasticsearch:9200&quot;]<br>index =&gt; &quot;apim_event_faulty&quot;<br>user =&gt; &quot;elastic&quot;<br>password =&gt; &quot;Admin1234&quot;<br>}<br>}<br>}</pre><h3>Configuring Filebeat</h3><p>Filebeat monitors your WSO2 log file and ships the data to Logstash.<br>Create a file named filebeat.yml under the filebeat/ folder:</p><pre>filebeat.inputs:<br>- type: log<br>enabled: true<br>paths:<br>- /mnt/logs/apim_metrics.log<br>include_lines: [&#39;(apimMetrics):&#39;]<br>output.logstash:<br># The Logstash hosts<br>hosts: [&quot;logstash:5044&quot;]</pre><blockquote><strong>NOTE:</strong></blockquote><blockquote>Make sure filebeat.yml is owned by root or uid=0, or the container will fail, use the below command to grant appropriate permissions.</blockquote><blockquote>sudo chown root filebeat/filebeat.yml<br>sudo xattr -c filebeat/filebeat.yml</blockquote><p>Once everything’s set up, go ahead and start your WSO2 API Manager server and fire a few API calls. Now, the ELK is ready. See the dashboard on http://&lt;hostname&gt;:5601/. If everything is wired correctly, you’ll see your logs dancing their way into Kibana’s Discover tab — just like this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*U3MyUTv4nFFyntFg" /></figure><h3>Uh-oh… Logs Not Showing Up? Here’s What to Check</h3><ol><li><strong>Is the Log File Being Updated?</strong></li></ol><p>Make sure WSO2 is actively writing to the <strong>apim_metrics.log</strong> file:</p><pre>tail -f wso2am-4.5.0/repository/logs/apim_metrics.log</pre><p>If it’s empty, try making some API calls. Still if you don’t see logs in this file, you need to verify your APIM configurations from above.</p><p><strong>2. Filebeat Running and Reading?</strong></p><p>If apim_metrics.log is properly populated, yet you do not see logs Kibana, check for the filebeat container logs using the below command:</p><pre>docker logs -f filebeat</pre><p>If you see nothing — check:</p><ul><li>File path in filebeat.yml (/var/log/apim_metrics.log)</li><li>Docker volume mount</li><li>File permissions (filebeat.yml must be owned by root)</li></ul><p><strong>3. Logstash Receiving and Parsing?</strong></p><p>Peek into Logstash logs using :</p><pre>docker logs -f logstash</pre><p>Look out for:</p><ul><li>JSON parsing errors</li><li>Pipeline startup issues</li><li>Messages being sent to Elasticsearch</li></ul><p><strong>4. Elasticsearch Got the Data?</strong></p><p>Verify if any index has been created:</p><pre>curl &quot;http://localhost:9200/_cat/indices?v&quot;</pre><p>If no index shows up with apim_event*, it means Logstash didn’t send anything or it failed parsing the logs.</p><p>Hopefully, the tips above help you get things flowing smoothly! But if the logs still play hide and seek, feel free to drop a comment — I’d be happy to help you troubleshoot. 😊</p><p>With logs now streaming into Elasticsearch and showing up in Kibana, you’re just getting started! 🎯 The real magic begins when you start <strong>building dashboards and visualizing API behavior</strong> with charts, filters, and custom widgets. Don’t hesitate to explore — Kibana is more powerful (and fun!) than it looks at first glance. 🚀</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=834c8019ac9c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Watchdog for Your APIs — Monitoring WSO2 API Manager with Datadog]]></title>
            <link>https://medium.com/@shaikrubina094/watchdog-for-your-apis-monitoring-wso2-api-manager-with-datadog-1ffbb4e205be?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ffbb4e205be</guid>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[datadog-agent]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-analytics]]></category>
            <category><![CDATA[datadog]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Wed, 02 Jul 2025 15:03:09 GMT</pubDate>
            <atom:updated>2025-07-02T15:05:54.114Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Watchdog for Your APIs — Monitoring WSO2 API Manager with Datadog</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I651NMr61AEJZDDDsd7DnQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@cookiethepom">cookiethepom</a> on <a href="https://unsplash.com/photos/brown-and-white-long-coated-small-dog-wearing-eyeglasses-on-black-laptop-computer-gySMaocSdqs">Unsplash</a></figcaption></figure><p>In today’s API-driven world, performance isn’t just a feature — it’s a necessity. While WSO2 API Manager does a great job of managing, securing, and exposing your APIs, how do you ensure they’re running smoothly, all the time? That’s where observability comes in.</p><p>Meet <strong>Datadog</strong> — your API watchdog. With real-time metrics, log monitoring, and intuitive dashboards, Datadog helps you keep an eye on what matters most: uptime, latency, and bottlenecks before they bite.</p><p>In this blog, we’ll walk through how to integrate Datadog with <strong>WSO2 API Manager</strong>, what insights you can unlock, and how to set it all up — step by step. Whether you’re a DevOps engineer, API architect, or just someone tired of flying blind, this guide will help you bring visibility into your API ecosystem.</p><p><strong>Deployment:</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/852/0*F3zZ2vRznyuoq6BK" /><figcaption>Source: <a href="https://apim.docs.wso2.com/en/latest/monitoring/api-analytics/on-prem/datadog-installation-guide/">WSO2 Datadog Installation Guide</a></figcaption></figure><p>As illustrated in the deployment diagram above, WSO2 API Manager analytics are logged asynchronously to the <strong>apim_metrics.log</strong> file. This log file is then monitored by the Datadog agent, which reads and publishes the data to the Datadog analytics platform.</p><p>On the Datadog side, a log processing pipeline is configured to pre-process the incoming data. This pipeline tokenizes the log content into structured attributes, which are then promoted to facets. These facets enable powerful filtering, aggregation, and the creation of insightful dashboards.</p><h3><strong>Configuring WSO2 API Manager</strong></h3><p>In this guide, I’ll be using WSO2 API Manager 4.5. The steps outlined here are applicable to all versions that support ELK-based analytics integration.</p><h4>1. Enable Log-Based Analytics in deployment.toml</h4><p>By default, Choreo-based analytics is enabled in WSO2 API Manager. To switch to log-based analytics (suitable for Datadog), update the following configuration in your deployment.toml file located at <strong>&lt;APIM_HOME&gt;/repository/conf/deployment.toml</strong></p><pre>[apim.analytics]<br>enable = true<br>type = &quot;log&quot;</pre><h4>2. Configure Log Appender in log4j2.properties</h4><p>To stream API analytics into a log file that Datadog can read, you’ll need to update the logging configuration. Locate the file at <strong>&lt;APIM_HOME&gt;/repository/conf/log4j2.properties</strong></p><p>➤ Add the custom appender to the list:</p><pre>appenders = APIM_METRICS_APPENDER, …(other appenders)</pre><p>➤ Add the following appender configuration:</p><pre>appender.APIM_METRICS_APPENDER.type = RollingFile<br>appender.APIM_METRICS_APPENDER.name = APIM_METRICS_APPENDER<br>appender.APIM_METRICS_APPENDER.fileName = ${sys:carbon.home}/repository/logs/apim_metrics.log<br>appender.APIM_METRICS_APPENDER.filePattern = ${sys:carbon.home}/repository/logs/apim_metrics-%d{MM-dd-yyyy}-%i.log<br>appender.APIM_METRICS_APPENDER.layout.type = PatternLayout<br>appender.APIM_METRICS_APPENDER.layout.pattern = %d{HH:mm:ss,SSS} [%X{ip}-%X{host}] [%t] %5p %c{1} %m%n<br>appender.APIM_METRICS_APPENDER.policies.type = Policies<br>appender.APIM_METRICS_APPENDER.policies.time.type = TimeBasedTriggeringPolicy<br>appender.APIM_METRICS_APPENDER.policies.time.interval = 1<br>appender.APIM_METRICS_APPENDER.policies.time.modulate = true<br>appender.APIM_METRICS_APPENDER.policies.size.type = SizeBasedTriggeringPolicy<br>appender.APIM_METRICS_APPENDER.policies.size.size = 1000MB<br>appender.APIM_METRICS_APPENDER.strategy.type = DefaultRolloverStrategy<br>appender.APIM_METRICS_APPENDER.strategy.max = 10</pre><p><strong>➤</strong> Add the reporter to the loggers list:</p><pre>loggers = reporter, …(other loggers)</pre><p><strong>➤ </strong>Define the logger configuration for the reporter:</p><pre>logger.reporter.name = org.wso2.am.analytics.publisher.reporter.elk<br>logger.reporter.level = INFO<br>logger.reporter.additivity = false<br>logger.reporter.appenderRef.APIM_METRICS_APPENDER.ref = APIM_METRICS_APPENDER</pre><h3><strong>Configuring Datadog</strong></h3><p>To get started, sign up for a new account in <a href="https://www.datadoghq.com/">https://www.datadoghq.com/</a> if not already. An application Key should be generated following the steps in this <a href="https://docs.datadoghq.com/account_management/api-app-keys/#add-application-keys">documentation</a>(Do not assign any scopes while creating the key).</p><p><strong>VM Deployment:</strong></p><p>For VM-based deployments, you’ll need to install the Datadog Agent, which is responsible for collecting and sending data to the Datadog cloud platform. Once the agent is installed and running, log in to the Datadog dashboard and open the <strong>Metrics Explorer</strong>. If you can see metrics like CPU usage, it confirms that the initial integration is successful.</p><p>By default, the Datadog Agent does not collect logs. To enable log collection, you’ll need to modify the agent’s configuration file.</p><ul><li><strong>For macOS</strong>, the configuration file is located at:<br> ~/.datadog-agent/datadog.yaml</li><li>For other operating systems, refer to the official documentation:<br><a href="https://docs.datadoghq.com/agent/configuration/agent-configuration-files/?tab=agentv6v7"> Datadog Agent Configuration Files</a></li></ul><p>Open datadog.yaml and set:</p><pre>logs_enabled: true</pre><h4>Setting Up Log Collection for WSO2 API Manager</h4><p>Next, configure a log collector to tail the WSO2 API Manager logs:</p><ol><li>Navigate to the ~/.datadog-agent/conf.d/ directory.</li><li>Create a new folder named wso2apim.d.</li><li>Inside this folder, create a file named conf.yaml.</li><li>Add the following configuration to the conf.yaml file, updating the path accordingly:</li></ol><pre>logs:<br>- type: file<br>path: &quot;&lt;APIM_HOME&gt;/repository/logs/apim_metrics.log&quot;<br>service: &quot;apim&quot;<br>source: &quot;apim_node&quot;</pre><p>For more information on custom log collection, refer to:<br><a href="https://docs.datadoghq.com/agent/logs/?tab=tailfiles#custom-log-collection"> Custom Log Collection — Datadog Docs</a></p><p>Finally, <strong>restart the Datadog Agent</strong> to apply the changes.</p><p>Once complete, invoke a few APIs via WSO2 API Manager, then check your Datadog dashboard. If everything is configured correctly, you should start seeing logs from APIM appear in the platform.</p><p><strong>Docker Deployment:</strong></p><p>If you prefer not to go with a VM-based setup, using Docker is a simpler and more portable alternative. In fact, I’ve used Docker for my own setup in this guide.</p><p>To get started, you just need to run the Datadog agent using the following Docker command. (Note: This command might vary slightly depending on your operating system. You can customize it as needed using the official Datadog Docker <a href="https://docs.datadoghq.com/containers/docker/log/?tab=containerinstallation">setup guide</a>.)</p><pre>docker run -d - name datadog-agent \<br> - cgroupns host \<br> - pid host \<br>-l com.datadoghq.ad.logs=&#39;[{&quot;type&quot;:&quot;file&quot;, &quot;source&quot;: &quot;apim_node&quot;, &quot;service&quot;: &quot;apim&quot;, &quot;path&quot;: &quot;/opt/am-logs/apim_metrics.log&quot;}]&#39; \<br>-e DD_API_KEY=&lt;API_KEY&gt; \<br>-e DD_LOGS_ENABLED=true \<br>-e DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL=true \<br>-e DD_LOGS_CONFIG_DOCKER_CONTAINER_USE_FILE=true \<br>-e DD_SITE=&quot;us5.datadoghq.com&quot; \<br>-v /var/run/docker.sock:/var/run/docker.sock:ro \<br>-v /var/lib/docker/containers:/var/lib/docker/containers:ro \<br>-v /opt/datadog-agent/run:/opt/datadog-agent/run:rw \<br>-v /&lt;APIM_HOME&gt;/repository/logs:/opt/am-logs:ro \<br>gcr.io/datadoghq/agent:latest</pre><p>Here’s a breakdown of the command:</p><p>-l com.datadoghq.ad.logs=’[&lt;LOGS_CONFIG&gt;]’ : This allows Datadog to identify the log source for each container and automatically install the corresponding integration. There are different ways you can configure this, which you can find <a href="https://docs.datadoghq.com/containers/docker/log/?tab=runcommand#log-integrations">here</a>.</p><p>DD_API_KEY: Specifies the Datadog API key for authentication.</p><p>DD_LOGS_ENABLED=true: Enables log collection.</p><p>DD_LOGS_CONFIG_CONTAINER_COLLECT_ALL: Configures the agent to collect logs from all containers (useful for Docker environments).</p><p>DD_LOGS_CONFIG_DOCKER_CONTAINER_USE_FILE: Enables log collection from container log files (e.g., /var/lib/docker/containers/*/*.log).</p><p>DD_SITE: Specifies the Datadog US5 site for log ingestion. Your site name can change based on the location where your Datadog is hosted, you can check your site from <a href="https://docs.datadoghq.com/getting_started/site/#access-the-datadog-site">here</a>.</p><p><strong>Volume mounts:</strong></p><p>-v /var/run/docker.sock:/var/run/docker.sock:ro<br>To connect to the Docker daemon to discover containers and collect stdout/stderr from the Docker socket.</p><p>-v /var/lib/docker/containers:/var/lib/docker/containers:ro<br>To collect container logs from files.</p><p>-v /opt/datadog-agent/run:/opt/datadog-agent/run:rw<br>To prevent loss of container logs during restarts or network issues, the last log line collected for each container in this directory is stored on the host.</p><p>-v /&lt;APIM_HOME&gt;/repository/logs:/opt/am-logs:ro <br>This specifies the mount path for api_metrics.log file</p><p><strong>Create a pipeline</strong></p><p>The published logs have to be pre-processed and extracted the attributes so that facets and measures can be created to generate dashboards and widgets. <br>To create the log pipeline, execute the following curl command providing the API Key and the Application Key to invoke the Log Pipeline Rest API.</p><pre>curl - location - request POST &#39;https://api.us5.datadoghq.com/api/v1/logs/config/pipelines&#39; \<br> - header &#39;Content-Type: application/json&#39; \<br> - header &#39;Accept: application/json&#39; \<br> - header &#39;DD_API_KEY: &lt;API_KEY&gt;&#39; \<br> - header &#39;DD_APPLICATION_KEY: &lt;APPLICATION_KEY&gt;&#39; \<br> - data-raw &#39;{<br>&quot;filter&quot;: {<br>&quot;query&quot;: &quot;source:apim_node&quot;<br>},<br>&quot;is_enabled&quot;: true,<br>&quot;name&quot;: &quot;PreProcessing&quot;,<br>&quot;processors&quot;: [<br>{<br>&quot;is_enabled&quot;: true,<br>&quot;grok&quot;: {<br>&quot;support_rules&quot;: &quot;&quot;,<br>&quot;match_rules&quot;: &quot;rules_1 %{date(\&quot;HH:mm:ss,SSS\&quot;)}%{regex(\&quot;[^a-zA-Z0–9]*\\\\w+[^a-zA-Z0–9]*\\\\w+[^a-zA-Z0–9]*\\\\w+ \\\\w+ [a-zA-Z0–9]*[^a-zA-Z0–9]*\\\\w+[^a-zA-Z0–9]\&quot;)}%{regex(\&quot;\\\\w+\&quot;):eventType}%{regex(\&quot;[^a-zA-Z0–9]* \\\\w+ [^a-zA-Z0–9]\&quot;)}%{data::json}\n&quot;<br>},<br>&quot;name&quot;: &quot;Grok Parser&quot;,<br>&quot;source&quot;: &quot;message&quot;,<br>&quot;samples&quot;: [&quot;08:23:34,898 [-] [PassThroughMessageProcessor-188] INFO ELKCounterMetric apimMetrics: apim:response, properties :{\&quot;apiName\&quot;:\&quot;PizzaShackAPI\&quot;,\&quot;proxyResponseCode\&quot;:200,\&quot;destination\&quot;:\&quot;https://localhost:9443/am/sample/pizzashack/v1/api/\&quot;,\&quot;apiCreatorTenantDomain\&quot;:\&quot;carbon.super\&quot;,\&quot;platform\&quot;:\&quot;Other\&quot;,\&quot;apiMethod\&quot;:\&quot;GET\&quot;,\&quot;apiVersion\&quot;:\&quot;1.0.0\&quot;,\&quot;gatewayType\&quot;:\&quot;SYNAPSE\&quot;,\&quot;apiCreator\&quot;:\&quot;admin\&quot;,\&quot;responseCacheHit\&quot;:false,\&quot;backendLatency\&quot;:3,\&quot;correlationId\&quot;:\&quot;02951f10-5934-456d-b608-7cd85b3f7c9d\&quot;,\&quot;requestMediationLatency\&quot;:1,\&quot;keyType\&quot;:\&quot;SANDBOX\&quot;,\&quot;apiId\&quot;:\&quot;af88b5f8-594a-4f57-a729-7eb86b6a63ab\&quot;,\&quot;applicationName\&quot;:\&quot;DefaultApplication\&quot;,\&quot;targetResponseCode\&quot;:200,\&quot;requestTimestamp\&quot;:\&quot;2022-12-15T02:53:34.894Z\&quot;,\&quot;applicationOwner\&quot;:\&quot;admin\&quot;,\&quot;userAgent\&quot;:\&quot;curl\&quot;,\&quot;userName\&quot;:\&quot;admin@carbon.super\&quot;,\&quot;apiResourceTemplate\&quot;:\&quot;/menu\&quot;,\&quot;responseLatency\&quot;:4,\&quot;regionId\&quot;:\&quot;default\&quot;,\&quot;responseMediationLatency\&quot;:0,\&quot;userIp\&quot;:\&quot;127.0.0.1\&quot;,\&quot;apiContext\&quot;:\&quot;/pizzashack/1.0.0\&quot;,\&quot;applicationId\&quot;:\&quot;87c8da4c-aa3f-43d3-89ac-dc3dc3b19d3e\&quot;,\&quot;apiType\&quot;:\&quot;HTTP\&quot;,\&quot;properties\&quot;:{}}&quot;],<br>&quot;type&quot;: &quot;grok-parser&quot;<br>}<br>]<br>}&#39;</pre><p>Now, invoke the integrations a few times, log in to DataDog and see if we can see the logs getting published. This is how it should look under the Logs Explorer view.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*p2bq59jPVKe-KKOK" /><figcaption>Logs appearing on Datadog log</figcaption></figure><p><strong>Creating Facets, measures and Dashboards.</strong></p><p>Now we have the pipeline working, we can create facets and measures on the extracted JSON fields. Click on a single log entry, and in the popup that appears we can create a facet or a measure for the extracted fields. Find more about facets and measures <a href="https://docs.datadoghq.com/logs/explorer/facets/#create-facets">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ILbE3SkyKjp_Mmzg" /></figure><p>Add the below fields as facets.</p><pre>apiContext<br>apiCreator<br>apiName<br>apiType<br>apiVersion<br>apiResourceTemplate<br>apiMethod<br>applicationName<br>applicationOwner<br>errorType<br>eventType<br>Destination<br>Platform<br>responseCacheHit<br>userAgent<br>userName<br>userIp</pre><p>Create measures for the following attributes</p><pre>backendLatency - Type Integer - Unit Milliseconds<br>responseLatency - Type Integer - Unit Milliseconds<br>responseMediationLatency - Type Integer - Unit Milliseconds<br>requestMediationLatency - Type Integer - Unit Milliseconds<br>targetResponseCode - Type Integer - Unit None<br>proxyResponseCode - Type Integer - Unit None<br>errorCode - Type Integer - Unit None</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ZL2bqGKTRePP5gx8" /></figure><p>You can also create dashboards in Datadog and add some graphs by applying filters on the facets and measures we created above. Find more about dashboards <a href="https://docs.datadoghq.com/dashboards/#copy-import-or-export-dashboard-json">here</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*pWH12x9aeuKTl0xE" /></figure><p>In this article, we explored how to integrate Datadog with WSO2 API Manager to gain powerful insights into API performance. Stay tuned for the next blog in this series, where we’ll dive into integrating the ELK stack with WSO2 APIM for advanced log analysis and visualisation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ffbb4e205be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Beyond the Logs: Monitoring WSO2 API Manager with Modern Tools]]></title>
            <link>https://medium.com/@shaikrubina094/beyond-the-logs-monitoring-wso2-api-manager-with-modern-tools-e82eea41dad3?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e82eea41dad3</guid>
            <category><![CDATA[wso2-analytics]]></category>
            <category><![CDATA[datadog]]></category>
            <category><![CDATA[grafana]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-api-manager]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Wed, 02 Jul 2025 14:30:27 GMT</pubDate>
            <atom:updated>2025-07-29T16:45:05.867Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/640/1*9hxbGkXI6mspmkg3Hj6jsQ.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jaredd">jareddc</a> on <a href="https://unsplash.com/photos/telescope-pointed-at-helicopter-on-mid-air-WYkl8rqaVUQ">Unsplash</a></figcaption></figure><p>Managing APIs effectively isn’t just about building and securing them — it’s about consistently monitoring, analyzing, and refining them for optimal performance. WSO2 API Manager integrates seamlessly with multiple monitoring platforms, helping organizations track API traffic and achieve operational excellence.</p><p>WSO2 API Manager offers a powerful suite of analytics tools that deliver deep insights into API usage, performance, and user behavior. These insights empower both API publishers and consumers to make informed, data-driven decisions. The analytics dashboards offer a unified view of API traffic patterns, user interactions, and key performance indicators.</p><p>Monitoring is a critical pillar of effective API management. Through this blog series, we’ll dive into the various tools and techniques available for monitoring WSO2 API Manager — from built-in dashboards to integrations with industry-leading platforms. Some of the key options we’ll cover include:</p><p><a href="https://medium.com/@shaikrubina094/logs-on-the-move-streaming-wso2-api-manager-logs-to-elk-stack-834c8019ac9c"><strong>ELK Stack (Elasticsearch, Logstash, Kibana)</strong> </a>— Native integration for log aggregation, processing, and visualization of API data.</p><p><a href="https://medium.com/@shaikrubina094/watchdog-for-your-apis-monitoring-wso2-api-manager-with-datadog-1ffbb4e205be"><strong>Datadog </strong></a>— Cloud-based observability platform that enables real-time API monitoring, alerting, and analysis.</p><p><strong>Choreo Analytics</strong> — A SaaS-based solution offering real-time visibility into API traffic, performance metrics, and user engagement.</p><p><strong>OpenSearch </strong>— Open-source alternative for searching, analyzing, and visualizing API traffic data.</p><p>Let’s kick off the first installment of our series: <a href="https://medium.com/@shaikrubina094/watchdog-for-your-apis-monitoring-wso2-api-manager-with-datadog-1ffbb4e205be"><em>Watchdog for Your APIs — Monitoring WSO2 API Manager with Datadog.</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e82eea41dad3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Setting Up ForgeRock as OAuth2 Key Manager in WSO2 API Manager-4.x.x]]></title>
            <link>https://medium.com/@shaikrubina094/setting-up-forgerock-as-oauth2-key-manager-in-wso2-api-manager-4-x-x-e0c7ba2f6a38?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/e0c7ba2f6a38</guid>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[wso2-api-manager]]></category>
            <category><![CDATA[forgerock]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Mon, 16 Dec 2024 10:22:12 GMT</pubDate>
            <atom:updated>2024-12-16T10:22:12.409Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*43EOWbyYsHkjH3YJ3FlJ0A.jpeg" /></figure><p>In this article, we’ll walk through the process of configuring <strong>ForgeRock</strong> as an external <strong>OAuth2 Key Manager</strong> for <strong>WSO2 API Manager 4.x.x</strong>. This setup allows you to securely manage OAuth2 tokens, making ForgeRock the central authority for issuing, validating, and managing API keys. We will also address common setup errors and provide solutions to troubleshoot any issues that may arise during the process.</p><p>Prerequisites</p><p>1. Prepare a JAVA Environment: Make sure that the Java version you’re using is supported by both ForgeRock and WSO2 API Manager. Set the JAVA_HOME environment variable to point to the latest supported Java version.</p><p>2. Install Apache Tomcat : Download version 9 <a href="http://tomcat.apache.org/">Apache Tomcat</a>. For information about supported versions, see <a href="https://backstage.forgerock.com/docs/am/6.5/release-notes/index.html#web-container-requirements">Web Application Container Requirements</a>. You will use Tomcat to run ForgeRock Access Management (AM).</p><h3>Step 1: Setup Tomcat</h3><ul><li>After downloading the preferred version of Apache Tomcat, unzip it and place it in a directory of your choice.</li><li>By default, all the users and roles are commented in the &lt;TOMCAT_HOME&gt;/conf/users.xml file. You need to configure the necessary roles and users:</li></ul><pre>&lt;role rolename=&quot;manager&quot;/&gt; <br>&lt;role rolename=&quot;manager-gui&quot;/&gt; <br>&lt;role rolename=&quot;admin&quot;/&gt; <br>&lt;role rolename=&quot;admin-gui&quot;/&gt; <br>&lt;user username=&quot;admin&quot; password=&quot;admin&quot; roles=&quot;admin,admin-gui,manager,manager-gui&quot;/&gt;</pre><ul><li>Download the latest <strong>ForgeRock AM WAR file</strong> from the official site and place it in the &lt;TOMCAT_HOME&gt;/webapps directory.</li><li>Start the Tomcat server, you will find the startup scripts in &lt;TOMCAT_HOME&gt;/bin directory</li></ul><blockquote>If you’re using Linux or macOS, make sure the Tomcat startup scripts have execute permissions by running:<br>chmod +x catalina.sh startup.sh shutdown.sh</blockquote><ul><li>Once the server has started you will observe the below screen. Make sure the ForgeRock AM war file status is Running. In my case it is /am.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Fpx4yTXyZoeU_lRL" /></figure><blockquote>If the Running status is false, you are probably not using the compatible JAVA version. Tomcat 9 is compatible with Java 11, try to change the JAVA version to 11.</blockquote><ul><li>Once the ForgeRock AM instance is up and running, you can set the password for the amAdmin user. Choose to either use the default or create a new configuration. It will take some time to complete the configuration.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Oy-C-y8N25On5Htv" /></figure><h3>Step 2: Configure the OAuth2 Service Provider in ForgeRock</h3><ul><li>After logging into ForgeRock, navigate to the <strong>Root Realm</strong> and select <strong>Dashboard → Service Management</strong>.</li><li>Click <strong>Add a Service</strong> and choose <strong>OAuth2 Provider</strong>.</li><li><strong>Set Core Settings</strong>:<br>Refresh Token Lifetime (seconds) — 60<br>Authorization Code Lifetime (seconds) — 120<br>Access Token Lifetime (seconds) — 3600<br>Issue Refresh Tokens — Enabled<br>Issue Refresh Tokens on Refreshing Access Tokens — Disabled</li><li><strong>Advanced Settings</strong>:<br>Scope Implementation Class — org.forgerock.openam.oauth2.OpenAMScopeValidator<br>Client Registration Scope Whitelist — default<br>Subject Types supported — public<br>Default Client Scopes — default<br>OAuth2 Token Signing Algorithm — RS256</li><li><strong>Client Dynamic Registration</strong>:<br>Require Software Statement for Dynamic Client Registration — Disabled<br>Required Software Statement Attested Attributes — redirect_uris<br>Allow Open Dynamic Client Registration — Disabled<br>Generate Registration Access Tokens — Enabled<br>Scope to give access to dynamic client registration — dynamic_client_registration</li><li>All other values shall be default.</li></ul><h3>Step 3. Configure the OAuth2 Client</h3><ul><li>Navigate to <strong>Realm → Dashboard → OAuth2 Clients</strong> and click <strong>Add Client</strong>.</li><li><strong>Enter Client Details</strong>:<br>Client ID — Enter a value of your choice<br>Client secret — Enter a value of your choice<br>Scope(s) — am-introspect-all-tokens, dynamic_client_registration<br>If you want to add scopes, you need to assign the relevant scopes to the OAuth clients.</li><li><strong>Core Section:<br></strong>Set a large value (e.g., 999999 seconds) to ensure that registration access tokens do not expire too quickly.</li><li><strong>Advanced Settings:<br></strong>Grant Type: Set as Client Credentials.</li></ul><h3>Step 4: Configure the Key Manager in WSO2 API Manager</h3><ul><li>Start WSO2 API Manager.</li><li>Navigate to the Admin portal. (https://&lt;hostname&gt;:9443/admin and log in).</li><li>In the <strong>Admin Portal</strong>, go to the <strong>Key Managers</strong> section in the left panel and click <strong>Add Key Manager</strong>.</li><li>Configure details as below. Under <strong>Key manager Type</strong>, select <strong>Forgerock</strong>.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*B31ayWSzhE8X6_yL" /></figure><ul><li>For the endpoint details you can just navigate to the below well known url and get all the details.</li></ul><p><a href="http://localhost:8080/am/oauth2/.well-known/openid-configuration">http://localhost:8080/am/oauth2/.well-known/openid-configuration</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9K1_-B9WWddWim9R" /></figure><ul><li>After entering the well-known url, you can simply hit the Import button. This will populate all other endpoint fields.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*oSJE2KB5EEFOEQAf" /></figure><ul><li>In the Connector Configurations, you need to provide the client and client Secret you provided for the OAuth2 client which you created in Forgerock.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ydUitQNM_0l6V-eg" /></figure><p>For more details on these configurations, you can check the documentation[1].</p><h3>Step 5: Generate keys using Forgerock</h3><p>Now that you are done with all the configurations, you can finally generate the keys using ForgeRock.</p><ul><li>Sign in to the Developer Portal.(https://&lt;hostname&gt;:9443/devportal)</li><li>Under the Applications tab, you can create an application or use the default application to generate keys.</li><li>Click Production Keys. You can select Forgerock and generate the keys</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*tDT6C-D6bXTSqv33" /></figure><blockquote>If you encounter issues when loading applications, such as seeing only a loading page, you may need to disable the validation for provisioned applications. To do this, add the following configuration under the apim.key_manager section in the &lt;API-M_HOME&gt;/repository/conf/deployment.toml file:</blockquote><blockquote>[apim.key_manager]<br>enable_provisioned_app_validation = false</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*she2JQpC-pCWU27Z" /></figure><p>Hope this article helps and guides effectively on how you can setup the ForgeRock as a Key Manager with WSO2 API Manager.</p><blockquote>Feel free to share your thoughts and experiences in the comments section.</blockquote><p>[1]https://apim.docs.wso2.com/en/4.3.0/administer/key-managers/configure-forgerock-connector/#step-2-configure-wso2-api-manager</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e0c7ba2f6a38" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reviving APIs: Customizing API Lifecycle in WSO2 API Manager 4.x.x]]></title>
            <link>https://medium.com/@shaikrubina094/reviving-apis-customizing-api-lifecycle-in-wso2-api-manager-4-x-x-f77f431380be?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f77f431380be</guid>
            <category><![CDATA[api]]></category>
            <category><![CDATA[api-manager]]></category>
            <category><![CDATA[wso2]]></category>
            <category><![CDATA[api-lifecycle-management]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Sat, 23 Nov 2024 16:51:59 GMT</pubDate>
            <atom:updated>2024-11-23T16:51:59.653Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IZEE4aQoej50DHB1JLgrSQ.png" /></figure><p>If you’ve found your way here, chances are you’ve accidentally moved a published API to a deprecated state and are now searching for a way to restore it. Or perhaps you’re looking to introduce a new state between the existing API states. Or maybe you’re simply keen to customize the API lifecycle rules to better fit your organization’s needs.</p><p>Whatever the case, this guide is here to help. Let’s explore how you can customize the default API lifecycle in <strong>WSO2 API Manager 4.x.x</strong> and adapt it to suit your requirements.</p><h3><strong>Understanding the API Lifecycle in WSO2 API Manager</strong></h3><p>The API lifecycle is one of the key factors in API management. APIs created in WSO2 API Manager have their own life cycle consisting of predefined states. These states represent the stages that an API has in the process of starting to develop an API until its retirement. The APIs created from WSO2 API Manager have a lifecycle that contains six stages which allows you to identify in which state that the API is currently in.</p><p>The following API lifecycle states are available in the default API lifecycle.</p><p><strong>CREATED</strong>: The API has been created, but is not available for use.</p><p><strong>PROTOTYPED</strong>: API prototype is created for early promotion and testing. The API can be tried without any subscription.</p><p><strong>PUBLISHED</strong>: The API is ready to be used in the Developer portal</p><p><strong>BLOCKED</strong>: The API is temporarily and blocked from use. An API can be moved to PUBLISHED state from the BLOCKED state.</p><p><strong>DEPRECATED</strong>: When a newer version of the API is PUBLISHED, the older version of that API is DEPRECATED.</p><p><strong>RETIRED</strong>: When the API is no longer used it can be moved to RETIRED state.</p><h3><strong>Creating a customized Lifecycle</strong></h3><p>This section demonstrates how you can edit the default API lifecycle and customize it according to your requirements.</p><p>1. Sign in to the API Publisher Portal and click on the API that you have already created.</p><p>2. In the Left panel, you will find a tab for Lifecycle. If you click on this you will see the default lifecycle for the API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Y3lwAq0zPMEQujMX" /></figure><p>3. Go to the Management console (<a href="https://localhost:9443/console%29">https://localhost:9443/carbon</a>).</p><p>4. Navigate to <strong>Extensions &gt; Configure &gt; Lifecycles</strong></p><p>5. Click the <strong>View/Edit</strong> link corresponding to the default API LifeCycle. You will find the default configuration appear.</p><p>6. This is the configuration file to customize the APILifecycle.</p><h3><strong>Adding a new state REJECT</strong></h3><ol><li>Say you want to add a new state REJECT for a published API.</li><li>Navigate to the APILifecycle configuration file in the Management console.</li><li>Add the below code block to the existing content.</li></ol><pre>&lt;state id=&quot;Rejected&quot;&gt;<br>    &lt;datamodel&gt;<br>        &lt;data name=&quot;checkItems&quot;&gt;<br>            &lt;item name=&quot;Deprecate old versions after rejecting the API&quot; forEvent=&quot;&quot;&gt;<br>            &lt;/item&gt;<br>            &lt;item name=&quot;Remove subscriptions after rejection&quot; forEvent=&quot;&quot;&gt;<br>            &lt;/item&gt;<br>        &lt;/data&gt;<br>        &lt;data name=&quot;transitionExecution&quot;&gt;<br>            &lt;execution forEvent=&quot;Re-Submit&quot; class=&quot;org.wso2.carbon.apimgt.impl.executors.APIExecutor&quot;&gt;<br>            &lt;/execution&gt;<br>            &lt;execution forEvent=&quot;Retire&quot; class=&quot;org.wso2.carbon.apimgt.impl.executors.APIExecutor&quot;&gt;<br>            &lt;/execution&gt;<br>        &lt;/data&gt;<br>    &lt;/datamodel&gt;<br>    &lt;transition event=&quot;Re-Submit&quot; target=&quot;Published&quot;/&gt;<br>    &lt;transition event=&quot;Retire&quot; target=&quot;Retired&quot;/&gt;<br>&lt;/state&gt;</pre><p>4. Add a new transition event under the PUBLISHED state, to show the state change to REJECTED.</p><pre>…<br>&lt;transition event=&quot;Reject&quot; target=&quot;Rejected&quot;/&gt;<br>…</pre><p>5. Go back to the Publisher portal. You will find that an extra state named. REJECT is added to an already published API.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HSNVelnuTN44CsV1" /></figure><h3><strong>Reverting an API from DEPRECATED to PUBLISHED</strong></h3><ol><li>When you move an API to DEPRECATED state, the only state you can move it to is RETIRED state as per the default API Lifecycle.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*OuLe2PcwjPluzqLz" /></figure><p>2. Say you mistakenly moved your API to a <strong>DEPRECATED</strong> state and now need to revert it to <strong>PUBLISHED</strong>. Creating a new API isn’t an option, as it’s tightly integrated with multiple applications. What do you do?</p><p>Don’t worry — I’ve got you covered :)</p><p>3. All you have to do is edit the APILifecycle to enable PUBLISHED state in the transition events section of DEPRECATED state. Below is an example of how you can modify your code.</p><pre>&lt;state id=&quot;Deprecated&quot;&gt;<br>  &lt;datamodel&gt;<br>    &lt;data name=&quot;transitionExecution&quot;&gt;<br>      &lt;execution forEvent=&quot;Publish&quot;<br>         class=&quot;org.wso2.carbon.apimgt.impl.executors.APIExecutor&quot;&gt;    <br>      &lt;/execution&gt;<br>      &lt;execution forEvent=&quot;Retire&quot;<br>         class=&quot;org.wso2.carbon.apimgt.impl.executors.APIExecutor&quot;&gt;<br>      &lt;/execution&gt;<br>    &lt;/data&gt;<br>  &lt;/datamodel&gt;<br>    &lt;transition event=&quot;Publish&quot; target=&quot;Published&quot;/&gt;<br>     &lt;transition event=&quot;Retire&quot; target=&quot;Retired&quot;/&gt;<br> &lt;/state&gt;</pre><p>4. When you navigate back to the Publisher portal, you will see a button to Publish the API though it is in the DEPRECATED state.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*HNElQNvLM3SE0g5J" /></figure><h3>Important Notes</h3><p>1. After making the necessary changes, revert to the default lifecycle configuration to maintain standard API lifecycle practices.</p><p>2. Always back up the original configuration file before making any modifications.</p><h3><strong>Conclusion</strong></h3><p>These were some of the basic scenarios where you might want to modify the default APILifecycle. By leveraging the power to modify the API lifecycles, you can add significant flexibility and control to your API flows.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f77f431380be" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Sun, Sand and Serenity: An Andaman Escape]]></title>
            <link>https://medium.com/@shaikrubina094/sun-sand-and-serenity-an-andaman-escape-f424449196af?source=rss-b4911ab1767d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f424449196af</guid>
            <category><![CDATA[beach-vacation]]></category>
            <category><![CDATA[honeymoon]]></category>
            <category><![CDATA[scuba-diving-in-andaman]]></category>
            <category><![CDATA[andaman]]></category>
            <category><![CDATA[marine-life]]></category>
            <dc:creator><![CDATA[Rubina Shaik]]></dc:creator>
            <pubDate>Tue, 13 Aug 2024 17:33:05 GMT</pubDate>
            <atom:updated>2024-08-14T16:47:06.116Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*czw1msRLrWrB-kxVB4SM3Q.jpeg" /><figcaption>Author’s click</figcaption></figure><p>A few weeks before our wedding, my husband turned to me and asked, “Where should we go for our honeymoon?” His question sparked a wave of excitement, and I eagerly grabbed my laptop to start searching for vlogs on YouTube. Although there were plenty of options available, we were looking for something truly unique. After an extensive search, we stumbled upon a vlog about the Andaman Islands, and in that moment, we knew it had to be the place.</p><p>Two weeks into our marriage, we flew from Hubli (a small city in Karnataka) to Port Blair, with a brief layover in Bangalore. Since it was my husband’s first flight, he was incredibly excited and stayed awake the entire time, determined to snag the window seat 😏. As for me, I spent much of the journey napping.</p><p>However, my husband, in a generous gesture, offered me the window seat as we flew over the waters. I was mesmerized by the breathtaking aerial view of endless turquoise waters and lush green islands. It was astonishing to see how the tiny specks of land on the map appeared so vast and magnificent from above.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vEOSoixe8zegL1ogzOz2SQ.jpeg" /><figcaption>Author’s click</figcaption></figure><p>The Veer Savarkar Airport in Port Blair is the gateway to the Andaman Islands. As it is a defense airport, photography inside is strictly prohibited, and the security is exceptionally tight. Flights primarily come in from Bangalore or Chennai.</p><p>One amusing quirk is that my luggage always seems to be the last one to arrive on the belt, which makes me anxious and convinced that it’s lost. This happens every time —even on the ferry, my luggage was the last to show up, making me worry if it had fallen into the ocean.</p><p>When we finally stepped outside the airport, we were greeted by our travel agent and the intense Andaman sun. The humidity is palpable, with a sticky feeling in the air that is constant throughout the day.</p><p><strong>Day 1 — A step into History</strong></p><p><strong>Cellular Jail<br></strong>No trip to Andaman is complete without a visit to the Cellular Jail, aka Kala Pani(Black Water). The jail was built by the British to imprison our freedom fighters. The building consists of a central tower and seven arms stretching out. A single guard in the central tower could keep an eye on the entire jail. Such an architectural marvel was not really needed to house the Indian prisoners for their struggle. But it is there serving as a huge memory of their sacrifices. The light and sound show is a story telling of the struggles endured by our freedom fighters who were imprisoned in its walls through a combination of illuminating lights and haunting sound effects. Visitors are transported back in time to witness the atrocities faced by our freedom fighters. Photography is strictly prohibited in the light and sound show. You will literally be in tears watching this. You might be tempted to skip this for other destinations, but trust me, it will be absolutely worth it.</p><p><strong>Corbyn Cove’s Beach<br></strong>It’s a highly populated beach, having small scale water sports. However, it’s a great spot for shopping, picking up souvenirs, and enjoying sunsets with a nice cup of chai.</p><p><strong>Day 2 — Dining under the stars</strong></p><p>We took a ferry from Port Blair to Havelock. This is where our real Andaman adventure begun. The island boasts some of the most stunning beaches I’ve ever encountered.</p><p><strong>Radhanagar Beach<br></strong>This beach is something out of a wonderland with its stunning sunrises and sunsets and crystal clear water. It’s an ideal stop for those seeking to spend some quality time in nature. If you’re looking to click some adorable pictures, don’t miss this place.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ge80Ig4eE6F5Z4aw7QpkYw.jpeg" /><figcaption>Author’s click</figcaption></figure><p>We ended our day with a nice candlelight dinner by the beach. It was one of the most memorable moments we shared. Picture this: dining by the shore, under a starlit sky, with the sand beneath your feet, the soothing sound of waves, and your loved one by your side. What more could you ask for?</p><p><strong>Day 3 — Exploring the Depths</strong></p><p>Did you know? You don’t need to know how to swim to go scuba diving? Well, I did not.</p><p>Early in the morning, our driver took us to the scuba diving spot. TBH, I did not want to do it. But seeing my husband being so excited, I couldn’t think of anything but to join him. After changing into our diving suits and signing the necessary consents, we stepped into the water.</p><p>I could already feel my heart skipping its beat every minute. The instructor noticed the nervousness on my face, he reassuringly held my hand and said, “Dariye mat, maza aa jayega”( Don’t be afraid, you will enjoy it). He taught us the underwater signals, to which I barely paid any attention, still wondering will I come back alive😬?</p><p>The moment we were under the water, I entered a completely new world, one I’ve never seen before. The ocean seemed to welcome us into its depths. The richness of marine life was astounding, and the beauty was heavenly, almost magical. Even now, the memory makes me feel the ocean on my skin.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UBrIf2doHIZf38Ixm3zf0g.jpeg" /><figcaption>Author’s click</figcaption></figure><p>Here’s a fact no one warns you about with scuba diving: you get insanely tanned. No sunscreen in the world can fully protect you from it. We had snorkeling planned at Elephant Beach as well, but the intense tan I got from scuba diving was enough to keep me from trying any other water activity.</p><p><strong>Kala Patthar Beach<br></strong>The beach has excellent aesthetics, making it ideal for photoshoots and seashell collecting — one of my favorite beach activities — and allows you to unwind in the lap of nature.</p><p><strong>Day 4 — Marine marvels at your feet</strong></p><p><strong>Laxmanpur Beach-2<br></strong>We took a ferry from Havelock to our next destination — Neil Island. It’s a small island stretching over 13.7 kms. Our first spot was Laxmanpur Beach-2, which is known for its Natural Coral Bridge — called as Howrah bridge by the locals. Nature has truly blessed the island with its breathtaking rock creation. It’s made of two living natural Corals only visible during low tide. The low tide also reveals a fascinating glimpse of marine life right under your feet, with corals and other aquatic creatures stranded in little puddles. We hired a guide who educated us about every single coral and sea-animal we came across. And also clicked some cute couple pictures for us.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svKlXxd-ilVN4IXjZanDSw.jpeg" /><figcaption>Author’s click</figcaption></figure><p><strong>Laxmanpur Beach-1<br></strong>A few kilometers away, we arrived at Laxmanpur Beach-1, which was comparatively less crowded, allowing us to relax and enjoy the sunset in peace.</p><p><strong>Day 5 — Unwind by the waves</strong></p><p><strong>Bharatpur Beach<br></strong>As we were approaching the end of our trip, we spent more time relaxing. Our final stop was Bharatpur Beach, where a wide range of water sports are available. We chose a glass boat ride, which lets you view aquatic life through a glass bottom beneath your feet. Rest of the time we spent watching others enjoying their Banana rides.</p><p>We then took a ferry from Neil Island back to Port Blair concluding our trip.</p><p><strong>Day 6 — Farewell to paradise</strong></p><p>Cherishing the unforgettable memories of our Andaman adventure we flew back to Bangalore from Port Blair.</p><p>Whether you’re an adventurer at heart or simply a lover of nature, Andaman promises an exciting blend of history, nature, adventure and relaxation. We carried not just memories of scenic beauty, but the special moments we got to spend with each other. So when are you planning your Andaman escape?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f424449196af" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>